TEAM8BuildGamingBasicCompare editions
8 TEAM8 Gaming Buy a key $80
Features

Everything inside
TEAM8 Gaming

A desktop app and a Claude Code plugin that share one record of your team. Here's what each part does.

Claude & roles

A chat for
every role

  • Seat a role in one click. The chat reads the team rules and its brief, checks its tools and posts READY on the board.
  • Model, effort and permissions per chat. Every reply shows its tool calls, time and cost as it happens.
  • Nine game roles to start: lead, combat, animator, netcode, fx, creatures, audio, qa and toolsmith. Add, rename and reorder your own.
  • File ownership. Each role owns part of the project, and chats claim a file before editing someone else's.
  • Works outside the app too. The bundled plugin brings the /team8 commands and team tools to any Claude Code chat.
A combat chat in TEAM8 measuring and fixing a boss ticket, with tool calls and a results table
Planning

One board.
One plan.

  • Team board. One record of every START, DONE, BLOCKED, QUESTION and ticket, from chats and people, newest first.
  • Tracker. Bugs in the tester's own words, with repro steps, priority, owner and the proof that shows a fix works.
  • Roadmap. Milestones with goals, target dates, owners, priorities and progress, edited by you and by Claude.
  • Research and handoffs. Reference notes every role can find, and handoffs so tomorrow's session starts where today's stopped.
  • Plain files. All of it is Markdown and JSON in your project's team/ folder.
Roadmap with three milestones and items owned by different roles
Build & ship

From checks
to a live build

  • Definition of done. Checks set for your engine (tests, builds) run from Runs & Outputs, with logs and a clear pass or fail.
  • Deploy with one button. Build, upload and get the live link. Updates go out the same way, or after every push.
  • Build presets for Godot web exports, Unity WebGL and npm builds, or your own command.
  • Access tokens stay on your computer, encrypted, and are hidden in logs.
  • Terminal and files built in, with previews for code, images and text.
  • itch.io
  • Netlify
  • Vercel
  • Cloudflare Pages
  • GitHub Pages
  • Your server (SSH)
  • Any deploy command
Deploy page with a choice of hosts
Costs & limits

Know what
every role costs

  • Token usage. Estimated cost by day, model, role and session, read from Claude Code's own records, including chats started outside TEAM8.
  • Prompt logs. Every prompt your team sent, searchable, with what each one cost.
  • Plan & limits. Your Claude plan, the 5-hour and weekly limits with reset countdowns, and how full each chat's context window is.
  • Token Saver. Command output trimmed by RTK before Claude reads it, with the tokens saved per session, per project and all time.
  • Estimates, not bills. Costs use API list prices. On a Claude subscription you aren't billed per token.
Token usage with cost per day, tokens per day, cost by role and by model
Co-op

Made for a team
of humans

  • Git, set up for you. Create the repository or clone a teammate's, put it on GitHub, GitLab, Bitbucket or any git server, and invite people with a ready-made message.
  • Pull and push from the title bar. The board, statuses and roadmap merge on their own; art files can be locked so one person edits them at a time.
  • Who's working on what. After a pull, say what you're on. Everyone sees it live, gets a warning before pushing into someone's files, and Claude stops before editing them.
  • Patch notes. Your trigger phrase has Claude write two notes per push: one for your teammate's Claude, one in plain words. Make notes required and pushes without them are refused.
  • Patch log. Every round back and forth, one click from its post on the board.
Who's working on what, with a warning that two people are editing the same file

Who's working on whatBoth people see the overlap before either pushes.

Patch log with two rounds of notes

Patch logNotes back and forth, linked to the board.

Token Saver · in every edition

Same work.
Fewer tokens.

Every command a chat runs (a test run, a build, a git diff, a search) comes back as text Claude has to read, and most of it is noise. Token Saver runs those commands through RTK, which keeps the lines that matter and trims the rest before Claude reads a word.

60–90%less output on common
dev commands*
1switch in
Settings
0changes to how
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.

TEAM8 Token Usage: tokens saved by RTK for the latest session, today, the project and all projects, saved per day and the commands that save the most
The window

An app with
an edge

A hexagon window

TEAM8 opens in its own shape: black, bone and blood red. Prefer a normal window? Switch to the standard Windows shape in Settings.

Dark and light

A dark theme made for long nights, and a light one for daytime, one click apart in the title bar.

Install or carry it

A Windows installer with its own theme music, or a single portable exe that runs from anywhere, even a USB stick.

Engines

66 engines
recognised

TEAM8 detects the engine when you open a project and sets the folders, checks and rules Claude follows. Anything else works as a Custom project.

  • Unity
  • Unreal Engine
  • Godot 4
  • Godot 3
  • O3DE (Open 3D Engine)
  • CRYENGINE
  • Flax Engine
  • Stride
  • s&box (Source 2)
  • GameMaker
  • Defold
  • Cocos Creator
  • Cocos2d-x
  • Solar2D (Corona)
  • LÖVE (Love2D)
  • GDevelop
  • Construct 3
  • RPG Maker MZ / MV
  • GB Studio
  • Adventure Game Studio
  • Ren'Py
  • Twine (Tweego)
  • Ink (inkle)
  • Bevy
  • Fyrox
  • Macroquad
  • MonoGame
  • FNA
  • raylib
  • SDL
  • SFML
  • libGDX
  • jMonkeyEngine
  • KorGE
  • Ebitengine
  • HaxeFlixel / OpenFL
  • Heaps
  • Kha
  • Flame (Flutter)
  • Pygame
  • Panda3D
  • Ursina
  • Python Arcade
  • DragonRuby Game Toolkit
  • Phaser
  • PixiJS
  • Three.js
  • Babylon.js
  • PlayCanvas (engine)
  • Excalibur.js
  • KAPLAY / Kaboom
  • Web (TypeScript / Vite / custom)
  • Roblox (Rojo)
  • PICO-8
  • TIC-80
  • Playdate SDK
  • Apple SpriteKit / SceneKit / RealityKit
  • Android (native)
  • C / C++ (CMake)
  • Visual Studio solution (C++ / C#)
  • Rust (Cargo)
  • .NET (C# / F#)
  • Java / Kotlin (Gradle)
  • Go
  • Python
  • Custom / other engine
Requirements

What you need

01

Windows 10 or 11

64-bit. macOS and Linux versions are in testing.

02

Claude Code

Signed in with a Claude plan that includes Claude Code, or with API billing. TEAM8 doesn't include Claude usage.

03

Node.js

The free LTS version, for the team tools that run inside Claude chats. TEAM8 tells you if it's missing.

04

git

Only for co-op with human teammates. Git LFS is recommended for art and audio.

TEAM8 Gaming

Seat your team
today.

Buy a Gaming key $80
One-time paymentYours forever13-day refunds