01
Who owns what?
Two chats edit the same script and you find out when it breaks. In TEAM8 every role has its own files, and a chat claims a file before touching someone else's.
TEAM8 Gaming · for Windows
Build your game
Build your game
with a team of Claude
chats.
TEAM8 Gaming puts Claude Code chats in roles (lead, combat, animator, netcode, fx, qa and more) and keeps them on one board. You get the roadmap, the bug tracker, token costs, git co-op with your human teammates and one-button deploys, in one window.
One-time paymentYours forever3 computersWindows 10 & 11
66game engines and toolchains recognised
9game roles ready to seat, plus your own
0API keys: it runs on your own Claude plan
1window for the chats and the humans
Why TEAM8
One Claude chat is a helper.
One Claude chat is a helper.
Five are a mess.
02
What's actually done?
Progress hides in five scrollbacks. TEAM8 keeps one team board, tickets, a roadmap and a definition of done, saved as plain files in your repository.
03
What did it cost?
Tokens disappear across sessions. TEAM8 reads Claude Code's own records and shows the cost per day, model, role and session.
How it works
From folder to studio
From folder to studio
in three steps
01
Open your game
Point TEAM8 at the project folder. It recognises the engine and adds the team: board, roles, tickets, roadmap and the checks that decide when work is done.
02
Seat the roles
One click seats a Claude chat as the lead, combat, animator or any role you add. It reads its brief, checks its tools and posts READY on the board.
03
Run the studio
Chats post START, DONE and BLOCKED as they work. You steer from the dashboard, run the checks, sync with your teammates and put the build online.
A look inside
Real screens.
Real screens.
Real build.
From the current TEAM8 Gaming build, running a demo Unity project.
What's inside
Everything a small studio needs.
Everything a small studio needs.
Nothing it doesn't.
01
Claude, inside the app
Uses your own Claude Code. Seat a role in one click; replies, tool calls and costs stream in live.
02
Roles & ownership
Nine game roles to start, or your own. Each owns its files, and claims keep chats out of each other's way.
03
Board, tickets, roadmap
A team board, a bug tracker and milestones, stored as Markdown and JSON inside your project.
04
Definition of done
Checks that know your engine (tests, builds) run from Runs & Outputs with logs and a clear pass or fail.
05
Token usage & prompts
Cost per day, model, role and session, plus every prompt your team sent, searchable.
06
Plan & limits
Your Claude plan, 5-hour and weekly limits with reset timers, and how full each chat's context is.
07
66 engines
Unity, Unreal, Godot, GameMaker and more, detected with the right folders, checks and rules for Claude.
08
Terminal & files
A real terminal and a file browser with previews, without leaving the window.
09
Token Saver
Test runs, build logs and diffs trimmed before Claude reads them, with every saved token counted.
10
Co-op with git
Create or clone the repository, one-click pull and push, team files that merge themselves, locks for art files.
11
Patch notes & who's on what
Every push carries notes for your teammate and their Claude. See who's editing which files before anyone pushes.
12
Deploy
itch.io, Netlify, Vercel, Cloudflare Pages, GitHub Pages or your own server, with one button.
Co-op
Humans and Claude,
Humans and Claude,
on one repo.
Every teammate runs TEAM8 and their own Claude chats on the same git repository. TEAM8 keeps the people in sync, not just the code.
- Who's working on what. After a pull, say what you're on. Everyone sees it live, and red faces warn you when two people touch the same file.
- Patch notes on every push. Say your trigger phrase and Claude writes two notes: one for your teammate's Claude, one in plain words for them.
- Guard rails for Claude. A chat stops and asks before it edits a file a teammate is working on.
- Your git host. GitHub, GitLab, Bitbucket or any git server. No TEAM8 server in the middle.
Who's working on whatTwo people in one file. Both see it before either pushes.
Patch logEvery round of notes, one click from its Board post.
Yours, not ours
No account. No cloud.
No account. No cloud.
No lock-in.
Your Claude plan
TEAM8 drives the Claude Code already on your computer. No API key to paste, and no markup on your AI usage.
Plain files
The board, tickets and roadmap are Markdown and JSON in your project. Stop using TEAM8 and you keep every word.
No TEAM8 servers
No sign-up with us and no tracking in the app. Your work goes only where you send it: Claude, your git host, your web host.
Pay once
One payment, no subscription, and your copy keeps working. Included: Free updates through version 1.x.
Token Saver · in every edition
Same work.
Same work.
Fewer tokens.
Unity test runs, Unreal build logs, git diffs of a scene file, a grep across Assets: every command a chat runs comes back as text it has to read. Token Saver runs those commands through RTK, which keeps the lines that matter and trims the rest before Claude reads them.
60–90%less output on common
dev commands*
dev commands*
1switch in
Settings
Settings
0changes to how
you work
you work
- Limits go further. Less noise in each chat's context means more work before the 5-hour and weekly limits, and emptier context windows.
- Every saved token, counted. Token Usage shows what was saved in each session, each project and all time, which commands save the most, and what it's worth.
- Local and open source. RTK runs on your computer and sends nothing anywhere. TEAM8 finds it, or installs it with one command.
*RTK's published figure for common commands such as git, test runners, builds and search. Savings depend on what your chats run. Token Saver is powered by RTK (Apache-2.0), an independent open-source project not made by TEAM8.
A test run, as Claude reads it
without npm test 412 lines ≈ 6,100 tokens
with rtk npm test 3 lines ≈ 70 tokens
FAIL src/api/orders.test.ts › rejects an empty cart
expected 400, received 500 (orders.ts:88)
1 failed · 127 passed · 4.2 s
Illustration of the kind of trimming RTK does on a test run.
$80once, for the key
3computers per copy
66engines recognised
13 daysto ask for a refund
Do I need a Claude subscription?
Yes. TEAM8 works through Claude Code on your computer, so you need Claude Code signed in with a Claude plan that includes it (such as Pro or Max) or with API billing. TEAM8 doesn't include or resell Claude usage.
Is it really a one-time payment?
Yes. Pay once and your copy keeps working, with no subscription. Included: Free updates through version 1.x.
Does each teammate need a copy?
Yes: one copy per person, installed on up to 3 of their computers. The files TEAM8 writes into your repository are plain text, so anyone can read them without a copy.
Which engines does it work with?
66 engines and toolchains are recognised, including Unity, Unreal, Godot, GameMaker, Defold, Bevy, MonoGame, Ren'Py, Roblox, Phaser and Three.js. Anything else works as a Custom project. See the full list.
Is there a Mac or Linux version?
TEAM8 Gaming runs on Windows 10 and 11 (64-bit) today. macOS and Linux versions are being tested and will be free for existing buyers when they ship.