Who it is forA developer who has more than one agent CLI installed and wants a developer, reviewer and QA agent to use different tools.
The problemForcing every role onto one agent CLI leaves some work done by a tool that is not the best fit for it.
The outcomeA board where the developer runs on Claude Code, the reviewer on the Cursor CLI and QA on OpenCode, each in its own session.
What you need first
- git installed on the machine
- At least one agent CLI (Claude Code, Cursor, Antigravity or OpenCode) or an API key for a model provider
- A GitHub account connected during first run
- macOS, Windows or Linux desktop
Steps
- Install TaskTrooper and connect Claude Code, the Cursor CLI and OpenCode during first run.
- Open the agent settings and set the runtime for backend-developer to Claude Code.
- Set the runtime for system-architect or security-agent to the Cursor CLI.
- Set the runtime for qa-agent to OpenCode, then move a test task into the QA column to confirm the handoff.
Prompt for your agent
In the makifbaysal/tasktrooper repo, open the agent settings and assign the runtime for backend-developer, security-agent and qa-agent to <runtime for each>. Report which runtime each agent used on its last run and confirm that each run has its own session.
Caveat. The runtime is set per agent, so a role runs on one CLI at a time and you must reassign it manually to change tools.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for makifbaysal/tasktrooper and "Split one board across Claude Code, Cursor and OpenCode"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer