Other tools
The board does not care which tool moved a ticket. It cares that something reported it. Every tool gets the same skills, the same stage vocabulary and the same command line; only the install path differs.
One command per tool
npx -y github:macleodlabs-ai/teamflow-plugin skills install --for cursor--for takes cursor, codex, gemini, copilot, windsurf, cline, zed, jetbrains, claude-desktop, aider, grok, codex-ide, opencode, openhands, pi, kiro, qwen and claude-code. Add --dry-run to list the files without touching any of them.
That writes the skills where your tool discovers them, or generates the rules file it reads instead, registers TeamFlow's MCP server in that tool's own format, and installs its hook configuration where it has one. Re-running replaces TeamFlow's block and leaves the rest of each file alone.
Then sign in once, exactly as in get started.
Tested, and coming shortly
We run TeamFlow in Claude Code every day, so it is the one tool marked tested. Every other tool is untested so far, and coming shortly. Its install steps follow that tool's own documentation and work today.
How much is automatic
- Through their own hooks: Claude Code, Cursor, VS Code with GitHub Copilot, Windsurf, Cline, OpenAI Codex CLI, Gemini CLI, JetBrains AI Assistant and Kiro. Nobody types a command and nobody instructs the model.
- Through git hooks: Zed, Aider and the OpenAI Codex IDE extension have no agent hooks. Grok Build, OpenCode, OpenHands, Pi and Qwen Code have hooks that TeamFlow does not read yet. For all of them, commits, merges and pushes report by themselves.
- Through its rules file: Claude Desktop has no hooks at all and reports because its rules tell it to. A git hook keeps the board complete when it forgets.
Installing the skills is not the same as them being used. Where the level is rules, reporting is still the model's decision — which usually happens and sometimes does not. A team that wants the board complete without depending on that puts a report into the places that already run on every change.
What each tool can do
Claude Code gets every feature of the TeamFlow plugin. The other tools get as much as their own hooks allow. This table comes from each vendor's documentation, checked 2026-10-04. We have not run these four tools with TeamFlow yet.
| Feature | Claude Code | Cursor | Codex | GitHub Copilot | Kiro |
|---|---|---|---|---|---|
| Ticket, project and lead notes at session start | Yes | Yes | Yes | Yes | Yes |
| Ticket, project and threads with each prompt | Yes | No | Yes | No | Yes |
| Allow or Deny from TeamFlow | Yes | No | Yes | Partly | No |
| Plan goes on when a turn ends | Yes | Yes | Yes | Partly | Yes |
| Helper agents and session end on the board | Yes | Yes | Yes | Partly | Partly |
| One-minute check-in on an idle session | Yes | No | No | No | No |
| TeamFlow skills | Yes | Yes | Yes | Yes | Yes |
| TeamFlow MCP server | Yes | Yes | Yes | Yes | Yes |
Why a tool does less
- Cursor: Ticket, project and threads with each prompt. Cursor takes no added text when you send a prompt.
- Cursor: Allow or Deny from TeamFlow. Cursor runs its hooks before every command, not only when it asks you. Waiting there would stop all work.
- Cursor: One-minute check-in on an idle session. Cursor cannot wake an idle session later.
- Codex: Allow or Deny from TeamFlow. Codex has no event for a question with options, so you answer those in Codex.
- Codex: One-minute check-in on an idle session. Codex cannot wake an idle session later.
- GitHub Copilot: Ticket, project and threads with each prompt. Copilot drops the text a hook adds to a prompt. The ticket comes at session start.
- GitHub Copilot: Allow or Deny from TeamFlow. Only Copilot CLI asks TeamFlow. The VS Code agent has no event for a permission.
- GitHub Copilot: Plan goes on when a turn ends. Only for helper agents. At a turn end, Copilot does not send its last answer.
- GitHub Copilot: Helper agents and session end on the board. VS Code reports helper agents but not session end. Copilot CLI reports agent stops and session end.
- GitHub Copilot: One-minute check-in on an idle session. Copilot cannot wake an idle session later.
- Kiro: Allow or Deny from TeamFlow. Kiro has no event for a permission. Holding every tool call would stop Kiro.
- Kiro: Helper agents and session end on the board. Kiro has no events for helper agents. Only Kiro CLI reports session end.
- Kiro: One-minute check-in on an idle session. Kiro cannot wake an idle session later.
Get the new features
Run the install for your tool again. It adds the hook events your install does not have yet.
npx -y github:macleodlabs-ai/teamflow-plugin hooks install --for cursor--for takes cursor, codex, copilot or kiro. teamflow doctor names each hook event that your install does not have.
Uninstalling
npx -y github:macleodlabs-ai/teamflow-plugin skills uninstall --for cursor
npx -y github:macleodlabs-ai/teamflow-plugin hooks uninstall --allThe first takes back exactly what the install of that tool wrote. The second takes back everything: every tool's hooks, the git hooks, and this repository's ticket binding. Both remove only what TeamFlow put there — another vendor's entry in the same config stays, a hook TeamFlow did not write is never touched, and your own instructions around a marked block are kept. --dry-run lists what would go without removing anything, and every run prints what it removed.
Reporting from anything with a shell
npx -y github:macleodlabs-ai/teamflow-plugin report --issue DAEMON-142 \
--stage LOCAL_TEST --status success --summary "42 tests, 0 failing"Same envelope, same transport, same credential, no model involved. It is the answer for a pre-push hook, an npm script, a CI step that is not GitHub Actions, or a JetBrains run configuration.
It never decides whether your push happens. It exits successfully on a refused, queued or unreachable service, so a TeamFlow outage cannot block a developer.
A guide for each tool
Every tool has its own page, with what the installer writes, where it writes it, and the configuration to paste if you would rather do it by hand.