TeamFlow MacleodLabs
Sign in Get started

Plan › Build › Audit › Ship

Agentic DevOps, from idea to shipped.

TeamFlow maps every Jira, Linear or GitHub issue as people and agents take it through tests, audits, CI and deploys, in one live delivery flow. Claude Code, Cursor, Copilot, Codex and any MCP client.

Get started

Set up in minutes• Works with your existing tools

The TeamFlow cat

Your AI-powered delivery OS

From idea
to shipped.

Active Tickets

24↑ 3

Jira issues in progress

Running Agents

5↑ 2

Claude Code agents

Audit Health

98%↑ 2%

Last 24 hours

Shipped This Week

12↑ 4

Issues verified in dev

Delivery Flow

Track every Jira, Linear and GitHub issue from development to deployment.
View all tickets
Backlog4
TF-101S

User onboarding flow

TF-102M

API rate limiting

In Progress3
TF-103L

Refactor auth service

TF-104S

Add analytics events

In Review2
TF-105J

Payment webhook handler

TF-106M

UI component library

Testing2
TF-107L

End-to-end tests

TF-108S

Performance optimizations

Deploy1
TF-109J

Production release v1.2

Recent Activity

View all

Security scan passed

TF-105 • No issues found

Claude agent completed task

TF-104 • Added analytics events

PR merged

TF-103 • Refactor auth service

Audit check passed

Dependency scan • 0 vulnerabilities

Deployed to production

TF-109 • v1.2.0

Built for modern teams

Engineers, reviewers and agents in sync

Works with your stack

Jira, Linear and GitHub Issues. Claude Code, Cursor, Copilot, Codex and any MCP client

Audit-ready by default

Security, compliance, and traceability

Move faster

Turn ideas into working software

TeamFlow is a delivery map for issues worked on with Claude Code.

Point it at Jira, Linear or GitHub Issues and the Claude Code plugin reports the stage each ticket reaches as people and agents work on it. Every issue sits at exactly one of eleven gates, from the tracker through local dev, test and audit to verified in dev, and the board shows all of them at once. Reports carry derived state only, so prompts, diffs and source code never leave your machine. It costs USD 25 per person per month, or USD 99 a month for a team of five.

Behind the board, eleven gates

The columns above are the summary. Underneath, every Jira, Linear or GitHub issue sits at exactly one of eleven stages that the Claude Code plugin and your CI report, from the tracker through local dev, test and audit to verified in dev.

Delivery Flow

Rework is drawn at the gate that failed, never as a column.

12 active 3 in review 1 blocked
Jira
DAEMON-151UI polish
Local Dev
DAEMON-142Hot-load Claude skills PROV-091Reporting UI
Local Test
CORE-220Alerts
Local Audit
PROV-083Billing API
Merge
CI / Build
CORE-217Cache layer
Deploy Dev
PROV-078Webhooks
Test Dev
PROV-085Notifications
Dev Audit
DAEMON-148Editor updates
Verified
DAEMON-131MCP support
Prod Review
DAEMON-171Search V2
Passed Running Waiting At an audit gate Not started

The plugin decides the stage from the work you were already doing. Edits, test runs, audits, merges and deploys each become one report, and background CI posts its own through the same route, so a build that finishes at 3am still moves the ticket.

Works with your tools

Every tool gets the same TeamFlow skills, the same stage vocabulary and the same command line. One line installs them where that tool looks: a skills directory, a rules file, an MCP server entry, whichever it reads. Eight of the eleven then report by themselves, through hooks that classify every tool call as it happens.

npx -y github:macleodlabs-ai/teamflow-plugin skills install --for cursor
Claude Code Automatic, via hooks /plugin install teamflow@macleodlabs Cursor Automatic, via hooks skills install --for cursor VS Code + Copilot Automatic, via hooks skills install --for copilot Windsurf Automatic, via hooks skills install --for windsurf Cline Automatic, via hooks skills install --for cline JetBrains AI Assistant Automatic, via hooks skills install --for jetbrains Zed Automatic, via git hooks skills install --for zed Claude Desktop Rules, then a git hook skills install --for claude-desktop OpenAI Codex CLI Automatic, via hooks skills install --for codex Gemini CLI Automatic, via hooks skills install --for gemini Aider Automatic, via git hooks skills install --for aider

Each guide carries what the installer writes for that tool, the sign-in step, and the config to paste if you would rather do it by hand. Installing the skills is not the same as them being used: where the level is rules, the agent reports because its rules file told it to, which usually happens and sometimes does not. A team that needs the board to be complete also puts teamflow report in the git hook or the test script that already runs on every change.

Derived state leaves your machine. Nothing else does.

Reporters post the stage a ticket reached and little else. The allowlist is a document you can read, and anything outside it is rejected before it is charged.

Sent with every report

  • The ticket key and the stage it reached
  • A status and a summary of up to 180 characters
  • Up to eight evidence links, such as a build or a pull request
  • Execution ids and timestamps

Never sent

  • Prompts and model output
  • Diffs and source code
  • Shell commands and their logs
  • Jira, Linear and GitHub issue bodies

The tenant a report lands in comes from the credential, never from the request, so one team's work cannot appear on another team's board. Read the whole allowlist in llms.txt.

One price, per person

No seat administration and no annual commitment. Pick monthly or annual, and start on your own or bring the team.

Individual

One engineer, one subscription.

$25 per member, per month

  • 2,000 reports a month, pooled across your organisation
  • One credit per accepted report. A rejected report costs nothing
  • REST and MCP on the same key, at /v1/report and /mcp
  • Cancel in Stripe whenever you like
Start as an individual
For teams

Team

Five members in one organisation.

$99 per month, five members

  • Five members included, each reporting under the same organisation
  • 10,000 reports a month, pooled across the organisation
  • Add members at individual rates once the five are used
  • Invite by link, so members join the organisation in one step
Start a team

Team organisations add members at individual rates. Invited members join through the link the owner sends them, and every paid member adds 2,000 reports a month to the organisation.

Questions people ask before signing up

What is TeamFlow?

TeamFlow is a delivery map for issues worked on with Claude Code. It shows every Jira, Linear and GitHub issue at the stage it has actually reached, from the tracker through local dev, test and audit to verified in dev, so a team can see the state of its work without asking anyone.

Which issue trackers does TeamFlow work with?

Jira, Linear and GitHub Issues. TeamFlow reads the ticket key from the work you are already doing and maps that ticket onto the delivery flow, so the tracker stays the system of record and TeamFlow stays the view of progress.

Does TeamFlow work with Cursor, Copilot and other IDEs?

Yes, and they get the same skills and the same hooks. One command, npx -y github:macleodlabs-ai/teamflow-plugin skills install --for cursor, writes the TeamFlow skills where that tool looks for them, registers the MCP server in its own format, and installs that tool’s hooks. Eight report automatically through their own hooks: Claude Code, Cursor, VS Code with GitHub Copilot, Windsurf, Cline, OpenAI Codex CLI, Gemini CLI and JetBrains Junie. Zed and Aider have no agent hooks, so TeamFlow installs git hooks and commits, merges and pushes report by themselves. Claude Desktop has no hooks at all, so the agent reports because its rules file tells it to, and a git hook keeps the board complete when it forgets.

How does Claude Code report progress to TeamFlow?

The Claude Code plugin derives the stage from the work itself. Edits, test runs, audits, merges and deploys each become one report, posted to the service over REST or MCP. Background CI posts through the same route with its own credential, so a build that finishes at 3am still moves the ticket.

What data leaves my machine?

Only derived state. Every report carries the ticket key and the stage it reached, a status, a summary of up to 180 characters, up to eight evidence links such as a build or a pull request, and execution ids and timestamps. Prompts, model output, diffs, source code, shell commands, their logs and the issue bodies themselves are never sent, and anything outside the allowlist is rejected before it is charged.

How much does TeamFlow cost?

An individual subscription is USD 25 a month, or USD 240 a year. A team of five members is USD 99 a month, or USD 1,140 a year. Each paid member adds 2,000 reports a month to a pool the whole organisation draws on, one credit per accepted report, and a rejected report costs nothing. Pilot teams can be invited instead: an invite code carries its own seats and its own complimentary period, and the organisation is created without a card.

How do teammates join my organisation?

By invite link. The owner copies a link and the person who opens it joins the organisation in one step, reporting under the same tenant. A team plan covers five members, and further members are added at the individual rate.

Can one team see another team’s tickets?

No. The tenant a report lands in comes from the credential that sent it, never from the request body, so a report cannot be addressed to somebody else’s board even deliberately.

Is audit a separate product?

No, audit is a stage. Local Audit and Dev Audit are two of the eleven gates every issue passes through, and when one fails the rework is drawn at the gate that failed rather than as a column of its own.

The full list of what a report may and may not carry is published for people in llms.txt, and for agents and IDEs on the capabilities route.