mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00

Files

T

Renn F f48106cbb6 docs: reflow hard-wrapped prose to one line per paragraph

Markdown and editors soft-wrap on their own, so the manual ~75-char line
breaks across the docs added nothing but noise. Join wrapped prose, list
items, and paragraphs into single lines across 67 docs — README, CLAUDE.md,
deployment, usage, the RAG knowledge base, and the agent role prompts.
Whitespace-only: code fences, tables, and blockquote alerts are byte-identical
and the change is token-verified (no content altered). Applied with a
deterministic reflow tool (committed separately).

Also lands two doc edits that were awaiting commit: the measured under-load
resource numbers in usage.md and the pr_reviewer additions to the
org-structure RAG doc.

2026-06-16 23:18:55 +02:00

2.3 KiB

Raw Blame History

Project & Workspace Tools

Overview

There is no roboco_project_* or roboco_workspace_* agent tool. Agents do not create projects, manage git tokens, or ensure workspaces. Those are handled for you:

Workspaces are auto-cloned by the orchestrator (WorkspaceService). Your per-agent clone of the project repo is created the first time you claim work on it — you never call a workspace tool. Branches are auto-created on i_will_work_on() / claim_review(); you don't run git checkout either.
Project registration and git-token management are operator actions done through the control panel / HTTP API, not from inside an agent container. Tokens are encrypted at rest; the agent container never sees the PAT (it is injected into git operations server-side and scrubbed from URLs).

What a task already tells you

A task carries its project linkage; you don't look it up with a tool. The task object you receive from give_me_work() / triage() includes the project_id (and the branch the flow verbs check out). Acceptance criteria and the project context come back inline on the Envelope.

Inspecting the repo

Read-only git inspection is available through the roboco-git-readonly MCP server (developers and QA):

roboco_git_status(project_slug="roboco")
roboco_git_log(project_slug="roboco")
roboco_git_diff(project_slug="roboco")
roboco_git_branch_list(project_slug="roboco")

There is no roboco_git_commit / _push / _checkout / _create_pr / _merge_pr tool. Commits go through the commit content tool (auto- prefixed with [task-id], auto-pushed by the choreographer); PRs open at open_pr time; merges are a PM complete operation.

Finding project knowledge

To learn how a project's codebase is laid out or how a subsystem works, query the knowledge base rather than a project tool:

roboco_kb_search(query="rate limiting redis", project="roboco",
                 index_types=["code", "documentation"])
roboco_ask_mentor(question="How is auth wired up in this project?")

PM note: creating work

PMs create work with the delegate flow verb (a subtask under the current parent task), not a project/task-create tool. delegate takes an optional project_id; the parent task's project is inherited when you omit it. There is no agent-facing standalone project- or task-create tool.

2.3 KiB Raw Blame History