Task Implementer
Pick a GitHub or Jira task, choose a developer persona, and run the Claude Code CLI on it with streamed output.
Task Implementer launches one claude process per task. The agent is the Claude Code CLI; other agents are not selectable in this app.
For how this app fits with the others when you build an app, see the Build apps guides: on your own or as a team.
The app runs claude -p <prompt> --output-format stream-json --verbose --dangerously-skip-permissions as your user, in the app’s working directory. The agent can read and write files and run commands without asking. The app does not create a sandbox, a temporary account or a virtual display. Use it only on repositories and machines where that is acceptable. The prompt asks the agent to create a feature branch, commit and push it, and not to open a pull request.
Requirements
- The
claudeCLI on the PATH, signed in. - A task server in
~/.config/robos/settings.json. For GitHub, theghCLI. For Jira, therobos-task-clientpackage, and the API token inpassat the server’stoken_pass_path. If none is configured, the window shows Open Task Servers; see Task Servers.
Use it
The window has three tabs: Tasks, Dependencies and Plan.
- In Tasks, choose Open, Closed or All. GitHub shows up to 50 issues (
gh issue list). Jira uses a JQL search for up to 50 issues. - Select a task. The header shows a persona (Frontend Web Developer is an example). Change it in the drop-down. The Directives panel holds the persona’s development guidance, editable for this run, with Reset to Role Default. Add hints in the extra-context box. Open opens the task in your browser.
- Click Start Agent. Output streams into Agent Output; Stop ends the process and Clear empties the pane.
- To review the result, click Review branch…. Choose the checkout of the implementation branch and the app opens PR Review on it.
Plan and Dependencies work on the loaded tasks. Generate Plan asks claude -p to order the loaded tasks (the prompt is written for Jira tasks), taking parent-child links, issue types, priority and blockers into account, plus your context text. The log appears under Generation Log, and the plan is saved to ~/.config/robos/plans/<server-id>.json.
Personas
Personas come from packages/robos-lib/agent-personas.js: Software Architect, Frontend Web Developer, Game Developer, Backend Systems Developer, Data & Storage Engineer, DevOps & Cloud Engineer, Non-Headless Developer and Human + Agent Desktop Co-Pilot. A persona is a system prompt plus development guidance, planning and implementation directives. When you do not pick one, the app guesses from the task’s persona or role fields, whether it is an epic, and its labels and text.
Use Agent Personas to edit them, add custom ones (saved in ~/.config/robos/agent-personas.json) or Restore Defaults.
The two GUI personas change two things only: the DISPLAY variable (:99, or ROBOS_XVFB_DISPLAY, for Non-Headless Developer; your current display for the co-pilot) and the prompt text, which tells the agent to use an isolated Xvfb display, tmpfs storage and IDE bridge tools. The app does not start Xvfb or mount storage itself, so those only work if your environment already provides them.