TeamFlow in VS Code with GitHub Copilot
Copilot agent mode loads Agent Skills and reads MCP servers from a workspace file, handling the OAuth handoff itself. Note the top-level key: VS Code says servers where almost every other client says mcpServers.
Tool VS Code + Copilot Reporting Automatic, via hooks
1. Install
npx -y github:macleodlabs-ai/teamflow-plugin skills install --for copilot
That writes:
.agents/skills/<skill>/SKILL.md— the ten skills, in the shared skills directory this tool reads.github/copilot-instructions.md— a marked TeamFlow block; your own instructions are kept.vscode/mcp.json— the TeamFlow MCP server underservers.teamflow/hooks/copilot.sh— the hook itself; it callsteamflow hook --for copilot, prints nothing the tool could read as a denial, and exits 0 whatever happens.github/hooks/teamflow.json— the hook registration:PostToolUse,Stop,postToolUse,postToolUseFailureandagentStop
Add --scope user to install for every project on this machine, or --dry-run to see the file list without writing anything. Re-running it replaces TeamFlow's block and leaves the rest of each file alone.
2. The skills you get
The same ten the Claude Code plugin carries, generated from the same SKILL.md files. This tool loads them as skills, one directory each, with the name prefixed so they do not collide with anybody else’s in a shared directory.
| Skill | What it does |
|---|---|
teamflow-login / teamflow-logout | sign in once, or remove the session |
teamflow-status | who is signed in, what is bound, what was last sent |
teamflow-bind / teamflow-unbind | name the ticket by hand, or stop |
teamflow-sync | publish the current state now |
teamflow-doctor | transport, account, credits, tracker MCP |
teamflow-repos | register a repository so its CI can report |
teamflow-admin-code | email an invite code to an org admin; superadmins only |
macleodlabs-teamflow-client | call the paid service over MCP or REST |
Each one wraps a github:macleodlabs-ai/teamflow-plugin subcommand, so the skill and the shell command are the same thing. Inside Claude Code they are /teamflow:login, /teamflow:status and so on.
3. Sign in once
A browser window opens on the first connection to the server. After that, MCP: List Servers shows teamflow running with its three tools, and they appear in the agent-mode tool picker.
4. By hand
The installer writes this for you. If you would rather paste it: .vscode/mcp.json in the workspace, or the user profile file from MCP: Open User Configuration.
{
"servers": {
"teamflow": {
"type": "http",
"url": "https://codercat.io/mcp"
}
}
}
Leave the oauth block out. It exists for servers that need a pre-registered client id; TeamFlow publishes /.well-known/oauth-protected-resource and VS Code discovers what it needs. The command palette writes the same file: MCP: Add Server -> HTTP.
Agent mode is the only mode that can call MCP tools. Ask mode and inline chat read the instructions and have nothing to call them with.
VS Code also scans .github/skills and .claude/skills. The installer writes only the shared root, so a repository carries one copy.
5. The stages to report
| Stage | When |
|---|---|
LOCAL_DEV | code is being written on a workstation |
LOCAL_TEST | the local test suite or build passed |
LOCAL_AUDIT | a local review, lint or security audit passed |
LOCAL_REWORK | a local gate failed; pass --rework-from naming it |
MERGE | the pull request is merged, or ready to be |
CI_BUILD | CI is building the merged change |
DEPLOY_DEV | the change is deployed to the shared dev environment |
DEV_TEST | tests passed against dev |
DEV_AUDIT | an audit passed against dev |
DEV_REWORK | a dev gate failed; pass --rework-from naming it |
DEV_VERIFIED | verified in dev |
READY_PROD | waiting on the production decision |
JIRA is the thirteenth: the ticket exists and nothing has started. Statuses are running, success, waiting, blocked, failed and idle. This is the same vocabulary the Claude Code plugin derives, so a ticket moved from here sits in the same column as one moved by Claude.
6. Without the agent
Anything that runs in a shell posts the same report with no model involved. A git hook, an npm script, a run configuration, a CI step:
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. Prefer it wherever the board has to be right whether or not an agent remembered. npx -y github:macleodlabs-ai/teamflow-plugin report --help lists every flag.
7. What this is not
VS Code with GitHub Copilot reports automatically through its own hooks: PostToolUse, Stop, postToolUse, postToolUseFailure and agentStop. Nothing to remember. One hook file in .github/hooks covers both the VS Code agent and Copilot CLI, which read the same directory in two different dialects.
The hooks see this tool's own calls and nothing else. A test run in another terminal, a merge from the web UI, a deploy from a pipeline: put npx -y github:macleodlabs-ai/teamflow-plugin report in the git hook or the script that already runs on every change, and those land on the board too.
8. What leaves your machine
TeamFlow is a delivery map for Jira, Linear and GitHub issues, run by MacleodLabs. Reports carry derived state only: a ticket key, a stage, a status, a short summary and evidence links. Prompts, diffs, source code, commands and logs are never sent and are rejected before they are charged.