Frequently asked questions
30 questions people actually ask, with the short answer and a link to the page that has the long one.
About TeamFlow
What is TeamFlow?
TeamFlow manages your AI software factory. It gives leads one live view of every agent workstream across the organisation. Each Jira, Linear and GitHub issue shows at the stage it really reached. A self-learning model fixes stalled, orphaned and crashed agents, and sends serious problems to a person. Your code never leaves your organisation. See how it works.
Which issue trackers does TeamFlow work with?
Jira, Linear and GitHub Issues. TeamFlow reads the ticket key from the work you already do, and puts that ticket on the delivery flow. The tracker stays the record, and TeamFlow shows the progress. See connect a tracker.
How does Claude Code report progress to TeamFlow?
The Claude Code plugin finds the stage from the work itself. Edits, test runs, audits, merges and deploys each become one report. Background CI reports through the same route with its own credential, so a build that finishes at 3am still moves the ticket. See the delivery flow.
How much does TeamFlow cost?
Solo is USD 25 a month, or USD 240 a year, for one developer. Team is USD 99 a month, or USD 1,140 a year, for five seats. Growth is USD 249 a month, or USD 2,388 a year, for ten. You pay per seat, and a seat is one person. A developer's agents report on their seat, and every agent, subagent and worktree they run is included. A viewer reads the board and takes a seat. CI and tracker connections need no seat. Use is fair use, never priced per report. See pricing.
Privacy
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. So a report cannot reach somebody else’s board, even on purpose. See security.
Does my code or my prompts leave my machine?
No. A report carries derived state only: an issue key, a stage, a status, a short summary, counts and timestamps. Prompts, diffs, source, shell commands, logs and issue bodies never leave the machine, and the service drops any field it does not recognise rather than storing it. What a report carries is the full list.
What exactly does a report contain?
The issue key and link, the stage and status, who did the work, the repository and branch, where the branch stands as counts, how many pull request checks are passing or failing, a summary of up to 180 characters, and timestamps. What a report carries has all of it.
Can TeamFlow read my issue descriptions and comments?
No. Descriptions, comments, attachments and custom fields are dropped where the webhook arrives, and an import does not ask for them at all. What is kept is the key, the title, the status, the assignee, the labels and the structure around the issue. See connect a tracker.
Does TeamFlow write anything back to my tracker?
Only if an owner turns it on, per connection, and only two things: a comment when a ticket is verified or ready for production, and a move to a status you choose from those two stages. It never reopens or closes an issue. See what a report carries.
Setting up
Which editors and agent tools are supported?
Claude Code, Cursor, VS Code with GitHub Copilot, Windsurf, Cline, OpenAI Codex CLI, Gemini CLI, JetBrains AI Assistant and Kiro report through their own hooks. Zed and Aider report through git hooks, and Claude Desktop through its rules file. Other tools has the one line for each. Cursor, Codex, Copilot and Kiro get more than reports, as far as their hooks allow: what each tool can do.
Do I need a tracker to use TeamFlow?
No, but without one the board starts empty and stays that way until something reports. A tracker is what puts an issue on the board before anybody opens an editor. Connecting one is three steps.
Do I have to report from my editor for a ticket to appear?
No. Your tracker’s webhook puts each issue on the board as it is created and keeps its title, assignee, status and labels current. The plugin then moves that ticket through delivery as the work happens. See connect a tracker.
How does a machine or a CI job report?
A person authorises the plugin once, on a consent page that names the tool and the machine, and it stays authorised until revoked. Each report carries a one-hour access token the plugin refreshes in the background; the long-lived refresh token is bound to that one machine, is sent only to TeamFlow’s token endpoint, and is revoked from the Organisation page or by /teamflow:logout. A GitHub Actions run authorises itself, exchanging its own OIDC identity for a short-lived credential, and it costs no seat. Nothing long-lived is pasted in anywhere. See get started.
Why does authorising the plugin show me a code?
So you can tell that the page in front of you is the one your terminal started. The consent page shows the same short code the terminal printed, and names the tool and the computer asking; if they do not match, press Deny and nothing is issued. When the browser is on the same machine the page opens with the code already in it, so approving is one press. See get started.
Projects
What is a project?
One or more repositories, with the Linear projects and Jira projects linked to them. It is how the board is divided up, and a project’s sources decide what its trackers import. See projects.
Why is my work showing as outside any project?
Because the repository you are working in belongs to no project yet. Nothing is lost: the reports land as usual and show under Outside any project, with an option to add the repository to one. See work outside a project.
Can one repository be in two projects?
No. A repository belongs to at most one project per organisation, and adding it to a second is refused with the name of the project that already owns it. Remove it there first. See projects.
Does choosing a project in the header change what gets reported?
No. The project in the header is a view. It never changes what a plugin reports or where a report is written, so you cannot file work in the wrong project by having the wrong one selected. See projects.
What happens to a repository I remove from a project?
Nothing is deleted. Its cards stay in the project’s history, and new reports land outside any project until the repository is added to one again. See projects.
Do git worktrees confuse it?
No. A worktree belongs to the same project as the repository it was made from. See projects.
The board
Where do failed tickets go?
Back to the gate that failed, with a loop drawn to it. Rework is never a column of its own, which is what lets the board say which gate is sending work back. See the delivery flow.
Can I move a card by hand?
No. Every position on the board was reported by the work itself, so a card you dragged would be the one thing on the board that was not true. Change the ticket in your tracker, or do the work. See the delivery flow.
My board is empty after connecting a tracker. Why?
A webhook only reports what happens from now on, so the issues that already existed come from the import. It runs in the background and issues appear as they arrive; press Import history under Integrations rather than waiting. See connect a tracker.
Your account
How do I invite someone?
Send them the invite link from the members page. Joining is invite-only, and each person takes one of the seats the owner pays for; nobody invited is asked for a card. If every seat is taken, the owner adds one from the members page. See your team.
Can I sign in with my fingerprint or face?
Yes, on any device that has a sensor for it, however you signed in — Google, GitHub or an emailed link all lead to the same offer, because one person is one account here and the three are doors into it rather than separate accounts. Setting up offers you a passkey on its first step, and the account menu — your name at the top right, then Add a passkey — has it afterwards. A passkey lives on the one device, so add one on each device you use, and the other ways in all keep working. That last part cuts both ways and is worth knowing: one account with four doors is only as protected as the least protected one, and for most people that is the mailbox, because anyone who can read your email can ask for a sign-in link. Two-factor authentication on your Google or GitHub account does not cover the other doors, so put the same protection on the mailbox. A passkey is the one door that cannot be phished or emailed to anybody. See get started.
How do I remove a machine that is reporting?
Run /teamflow:logout on the machine, which revokes its credential at the service. Every authorized machine can also be revoked from the members page, which is what to use when you no longer have a shell on it; that ends its refresh token and its access tokens on the next report. See your team.
Can one person belong to more than one organisation?
Yes. Each machine reports to one organisation at a time, and /teamflow:org switches it. Reports published after the switch belong to the new organisation and nothing already published moves. See your team.
Can I pay for TeamFlow now?
Not yet. Paid plans open soon. Every new organisation gets the Growth plan free for 30 days, and the trial keeps going until paid plans open. See pricing. Questions: macleod@macleodlabs.ai.
Do you give refunds?
No. All fees are non-refundable, including for a part-used period, unused reports, a downgrade or a cancellation part-way through a period. The exceptions are a charge we made in error and any refund right the law gives you. See section 5 of the terms of service.
How do I delete my data, or ask a question about it?
Ask your organisation’s owner first if you are a member, because they decide what the organisation reports. You can also come to us directly: the privacy policy has the contact address and what we will do within a month of being asked.