The index

Everything TEAM8 does,
and when you'd use it.

35 things, grouped, with one example each in the words of the edition it belongs to. This is the same list the app shows under Editions › What it can do, so it cannot drift from the product.

The team and its record

	TEAM8Build	TEAM8Gaming	TEAM8Basic
Roles, briefs and ownershipEight preset roles per edition or your own, each with a mission, a brief and the files and folders it owns. Basic: Give the writer content/ and the finance role invoices/, so neither ever edits the other's files by accident. Build: Give backend src/api/ and frontend src/app/, so two chats can work the same afternoon without a merge fight. Gaming: Give combat Assets/Scripts/Combat/ and the animator Assets/Animations/, so a balance pass never touches a rig.
The boardAn append-only record in your project: START, DONE, BLOCKED, QUESTION, REVIEW, APPROVED, DECISION. Chats write it; so do you. Come back on Monday, read the last ten entries, and know exactly what happened without opening a single chat.
Catch me upOne press: everything that happened since you last had TEAM8 open, read straight from the record. No tokens, no waiting. After two days away: four board posts, one ticket claimed, a decision that ran past its date, and what each role spent.
Decisions with defaultsA choice a chat should not make alone, with what happens if you never answer. It carries on under that default instead of guessing or stalling. Basic: "Do we pay for the photo licence?" defaults to no, so nothing is bought while you are thinking about it. Build: "Do we ship without the migration?" defaults to holding the release, and the team keeps working meanwhile. Gaming: "Cut the third boss from the slice?" defaults to keeping it and slipping a week, and combat carries on.
TicketsA tracker in plain files: symptom in the reporter's words, how to repeat it, an owner, and what would prove it fixed. One claimed ticket per role. Basic: Turn "the invoice email reads oddly" into a ticket the writer owns, with the sentence that has to change. Build: Turn a failing test into a ticket with the repro command and the owner, claimed by backend. Gaming: Turn a tester's "the boss teleports too much" into a ticket with the build, the seed and the level.
Roadmap and milestonesMilestones with items and owners, and the share of each that is done. It is what the team reads when it asks what to do next. Set one milestone for the month, put five items under it, and let Home tell you how far along it is.
Research studiesA role's findings written to a file instead of buried in a chat, so the next chat reads the study rather than repeating it. Have a role study the three options before a decision, then link the study from the decision itself.
Check the recordWhat stalled: two tickets on one role, claims nobody released, a block with no follow-up, decisions past their date, roles with no brief. Every finding names its fix. Friday afternoon, press it once and clear whatever the week left hanging.
Handover and rotationA chat that has been compacted writes a forty-line handover, is closed for good, and a fresh chat takes the role and reads it first. When a role's chat gets slow and forgetful, press Rotate instead of fighting it, and the new one starts knowing where things stand.
File claimsA chat claims a file before touching anything outside its own area, and a chat that reaches for a claimed file is stopped by a hook, not a rule in a prompt. Two roles need the same config file: the second one is told who holds it and asks on the board instead of overwriting it.

Doing the work

	TEAM8Gaming	TEAM8Basic
Claude chats in rolesSeat a role in one click: it runs on your own Claude Code, reads its brief and the board, and streams its replies, tool calls and cost into the window. Seat the lead, ask for a plan for the week, and watch it post the plan on the board for everyone else to read.
Model and effort per roleAdvice on which model and effort each role should run, from how important the role is, what your plan allows, or both. Applied in one click. Put the lead on the strongest model and the docs role on the cheapest, and stop paying Opus prices for a changelog.
Compaction between tasksWhen a role finishes a task, its chat is compacted down to its brief, claimed files, open tickets and recent board posts before the next one starts. A role that has worked all day starts its next task on a small context instead of dragging the whole day behind it.
Checks before doneThe commands that have to pass before anyone says a job is finished, run from the app with their logs and a clear pass or fail. Basic: A link checker and a spell pass over what is about to go out. Build: Lint, typecheck, tests and build: the same four your CI runs. Gaming: The engine's own build and test commands, on the build the tester will play.
Rig BuilderOne sentence, one tool made for this project: TEAM8 works out what shape a tool takes in your engine or stack and a role writes it. Build: "Seed the dev database with ten realistic orders" becomes a Node command in tools/ with an npm script. Gaming: "List every prefab with a missing script" becomes a Unity Editor menu item under TEAM8.		Not included
Site BuilderBuild and edit a website in your repository while it runs: click anything to change it, live theme, accessibility and layout checks, design reviews from screenshots, undo. Change a headline by clicking it (no tokens), then ask for a pricing section and watch it appear in the preview.	Not included	Not included
DeployPut the thing live from one button, with the token kept in your system keychain and an option to deploy after every push. Basic: Publish the site you built to Netlify without leaving the app. Build: Ship to Vercel, Netlify, Cloudflare, GitHub Pages or your own server over SSH. Gaming: Push a web build to itch.io with butler, every update in one press.
Terminal and filesA real terminal and a file browser with previews, in the same window as the team. Run one command, see it fail, and send the output straight to the role that owns that file.
The Claude Code pluginThe same team commands in any Claude Code chat — a terminal, your editor, the Claude desktop app — through the team8 skills and MCP tools. In a terminal chat, /team8:board read and /team8:ticket work exactly as they do in the app.
8, the guide, and the tutorialA first-run walk-through that builds a throwaway project and does a working day's moves in it, then one hint per page whenever you meet it. New teammate on their first morning: press Show me, and a minute later they have seen a ticket, a claim and a check run.

What it costs

	TEAM8Build	TEAM8Gaming	TEAM8Basic
Token usageWhat every chat, role, model, project and day cost, read from Claude Code's own records. Find the role that quietly costs three times the others, and move it down a model.
Plan and limitsYour Claude plan, each usage limit with when it resets, and how full every chat's context window is. See the weekly limit at 80% on a Thursday and put the heavy work on the strongest role only.
Token SaverCommand output trimmed by RTK before Claude reads it, with the tokens saved counted per session, project and all time. A failing test run reaches the chat as the failure and the changed lines, not four hundred lines of log.
Prompt logsEvery prompt sent from this computer, searchable, with what it cost and which role sent it. Find the wording that got a good answer last month and use it again.
BudgetA daily and monthly figure you set, shown against what has been spent. Set ten dollars a day, and see the day's bar turn as it fills.

Working with other people

	TEAM8Build	TEAM8Gaming	TEAM8Basic
People approveReviews, approvals and decisions are posts on the board, so what ships, sends or merges is a person's call and stays on the record. Basic: Nothing is emailed, posted, paid or signed without an APPROVED post from you or your approver. Build: Nothing merges to main or reaches production without an APPROVED post from the release approver. Gaming: Nothing goes to the tester without the lead's sign-off on the board.
Co-op with a human teamShare the project through git: pull and push from the title bar, the board merged rather than fought over, and patch notes on every push. Two people, four chats, one repository: everyone pulls in the morning and reads what the others' roles did overnight.			Not included
Who is working on whatLive records of what each teammate and each chat is on, shared through the remote, with a warning before two people touch one file. You open a file a teammate's chat is holding, and TEAM8 tells you before you start typing.			Not included
Patch notesA short note written on every push and posted on the board when others pull, so a teammate reads what changed rather than a diff. Your artist pulls and reads "dash cooldown is 0.4s now", instead of finding out in play.			Not included
CommunicationsEmail, calendar, files and chat through the connectors in your own Claude account: TEAM8 sorts what came in and drafts replies that wait for you. Press Check now, read Needs you, edit the draft reply, approve it, and send it yourself.	Not included	Not included
Social, and ScoutA researcher that reads the web and cites what it found, drafts posts with hashtags, plans the week, and learns from what actually did well. Nothing is posted without you. Scout finds what is being said about your kind of business this week; you approve three posts and put them on Tuesday, Thursday and Friday.	Not included	Not included

Made for what you build

	TEAM8Build	TEAM8Gaming	TEAM8Basic
What TEAM8 recognisesTEAM8 looks at the folder and sets the team up for what is actually in it, with the checks and the rules for Claude that go with it. Basic: Seven project types, and the apps your files come from: Word, Excel, PowerPoint, Google, Apple, PDF, design files, cloud folders. Build: Twenty stacks with their lint, typecheck, test and build commands, and thirty-plus tools and services from GitHub to Sentry. Gaming: Sixty-six engines from Unity and Unreal to Ren'Py and Roblox, each with its checks, generated folders and pitfalls.
All-rounder roleOne role that covers every job at once, for a project too small to split up — with a plain warning about what it costs in tokens. A one-week project run by one chat that still keeps the board, the tickets and the record.
Editions and keysOne download holds all three editions. Basic is free; a key bought on team8.dev unlocks Build or Gaming on up to three of your computers, and you switch whenever you like. Run Basic for the business side in the morning and switch to Build for the codebase after lunch.
The windowA shape per edition — a capsule, a tall box, a hexagon — that changes as you switch, with a standard window one switch away. Keep the tall box beside your editor, or turn the shapes off entirely and use a normal window.

Basic is free with the download. A key for Build or Gaming unlocks the rest on up to 3 of your computers, and you switch between the editions you own inside the app.

TEAM8

Start free.
Unlock what you need.

Download TEAM8 free

One-time paymentYours forever13-day refunds

Everything TEAM8 does,and when you'd use it.