WORLD 1-1

Tickets are cattle, not pets.

TCC Factory runs your tickets down a workflow you draw, each in its own git worktree with its own Claude Code or Copilot CLI agent. When one needs you, its pane glows and your watch can answer it.

Opens your own mail app with the link filled in. No sign-up; nothing is sent to us. No mail app?

Windows 10 and 11, x64. Version 0.3.1. No account, no API keys.

The Factory workflow canvas: tickets wait on a Tickets node, flow to an AI action that fixes the bug, then a decision that checks the tests and sends each ticket to Done or back for another try.
1Tickets wait here until you press Go2A decision sends each ticket on, or back Real screenshot of the Factory in TCC 0.3.0. The workflow and tickets are made up.
  • 1P Claude Code
  • 2P GitHub Copilot CLI
  • Android phone
  • Wear OS watch

WORLD 1-2

Draw the line once. Tickets run it.

Factory is a new way to build software with AI. Draw a workflow, drop tickets in and press Start. Every ticket gets its own git worktree and its own Claude Code or Copilot CLI session, and moves down the line by itself. You stop nursing one agent at a time and start delivering tickets.

  1. Tickets bugs/ TKT-12TKT-13TKT-14 next
  2. Categorise Which area does this ticket touch? uidata
  3. Action Fix this bug: {title} Acting complete
  4. Decision Did the tests pass? yesno: back to Action
  5. End Ready for review TKT-9TKT-10
Illustration of a Factory workflow. Tickets are plain .tkt text files in a folder.
  • Draw the line

    Tickets, Decision, Categorise, Action, Wait, Delay and End nodes on a canvas. Wire an output to the next node; an unwired output finishes the ticket.

  • One worktree, one agent

    Each ticket gets a factory/<ticket-id> branch in its own worktree (on by default), and keeps the same AI session for the whole line. Action nodes type the prompt for you and move on when the turn ends.

  • A model routes the work

    Decision and categorise nodes ask a decision model where each ticket goes next, from the ticket and its files or the tail of its console. laya runs on your PC; jev is hosted.

  • You handle the exceptions

    "N at a time" caps how many tickets a node works on. A ticket whose agent waits on you shows Needs your input, and Open session takes you straight to its pane.

WORLD 1-3

PICK A GAME

Four ways to lose an afternoon.

Each one is a familiar moment from running coding agents. Watch it go wrong, then watch TCC replay it.

TCC ARCADE

Ticket Stampede

Game over

Eight tickets in. One shipped.

STORY TIME. NOT A BENCHMARK.

TICKETS ARE CATTLE, NOT PETS

NOW PLAYING Ticket Stampede

Draw a workflow once. Every ticket gets its own worktree and agent, and moves on by itself.

Save the link

Game over times are story time, not a benchmark. Session names in the games are made up.

CARTRIDGE SHELF 4 GAMES

  1. Ticket Stampede

    Eight tickets, one agent at a time, and you are the bottleneck.

    Game over Eight tickets in. One shipped.

    Unlocks Factory: a workflow that runs every ticket

    See Factory for Ticket Stampede
  2. Coffee Run

    You stepped away. Your agent finished with a question and stopped.

    Game over You came back. It stopped 40 min ago.

    Unlocks Reply from your watch or phone

  3. Out of Range

    You left home. Your agent asked a question nobody could see.

    Game over You left the Wi-Fi. It waited all day.

    Unlocks Cloud connections from your phone or another TCC desktop, end-to-end encrypted

  4. The Lost Session

    Can't find yesterday's agent chat? Start again from scratch.

    Game over You explained the whole bug again.

    Unlocks Every session in one panel. Click to resume

    Real screen for The Lost Session

WORLD 1-4

Power-ups.

6 items to find

Every screen on this level is a real screenshot of TCC 0.1.0. ScrollSwipe to collect all six.

  1. ITEM 1 · SPLIT SCREEN

    Tile every agent

    Split any pane to any depth, then flip between the grid and one pane in focus.

    KeysCtrlAlt→split rightCtrlShiftFgrid / focus

    Terminal Command Center with four terminal panes: tests passing, a git history graph, a dev server request log and git worktree status.
    1Split lineReal screenshot · four panes tiled in a 2x2 grid, one window
  2. ITEM 2 · WARP ZONE

    Jump by letter

    A letter lands on every pane. Press it and you are there. No mouse, no hunting.

    KeysCtrlShiftJthen a letter

    Pane hints: a large letter on every pane so you can jump to it with one key press.
    1Press A to land hereReal screenshot · every pane gets its own letter: A, D, S, F
  3. ITEM 3 · SESSION RADAR

    Every AI session, one panel

    Every Claude Code and Copilot CLI session on this PC, grouped by repo, each with its live state. Click a row to resume it in a new pane.

    KeysCtrlShiftCAI Sessions

    The AI Sessions panel listing Claude Code sessions grouped by project folder, each with a live status such as Waiting for input, Thinking or Running a tool.
    1Grouped by repo2Waiting for inputReal screenshot · the AI Sessions panel docked beside your panes (dimmed here). Session names and prompts are made up.
  4. ITEM 4 · CODE REVIEW

    Review the diff, send the notes

    Comment on any line of the diff, then send every note to Claude in one go.

    OpenCtrlShiftPthen Diff Review

    The diff review screen with a review comment left on a changed line of code.
    1Line commentReal screenshot · diff review. Zoom shows the Send 1 to Claude button.
  5. ITEM 5 · BRANCH SPLITTER

    A worktree per agent

    Create, open and review git worktrees from one panel, so every agent gets its own branch and nobody trips over anybody.

    OpenWorktreesin the status bar

    The Git Worktrees panel showing three worktrees of one repository with buttons to open, review or delete each.
    13 worktrees2One per branchReal screenshot · the Git Worktrees panel docked beside your panes (dimmed here), from a made-up demo repo.
  6. ITEM 6 · CHEAT CODES

    Every command, one search

    The palette lists every command with its shortcut. Then pick a skin: 12 themes, 8 dark and 4 light.

    KeysCtrlShiftPpaletteCtrlShift?all shortcuts

    The command palette listing commands such as New Terminal and Jump to Terminal by Hint, each with its keyboard shortcut.
    1Type to search2Shortcut chipsReal screenshot · command palette

Stage clear!

Six power-ups in the box. TCC is not released yet, so email yourself the link and check back.

Your own mail app opens with the link filled in. No sign-up, and nothing is sent to us.

WORLD 1-5

Player 2 has joined.

Your Android phone and Wear OS watch connect straight to your PC on your own network. When Claude needs you, answer from your wrist.

Out of the house? When you add a host, pick Local or Cloud. Cloud reaches the same PC from anywhere, end-to-end encrypted. And on another TCC desktop, Connect to host… opens your PC’s tabs.

TCC is free. Cloud connect is an optional paid add-on with a 3-month free trial.

Android 8.0 or later. Wear OS (API 30) or later. Not on app stores yet.

How pairing stays safe

P2 · Android phone

Animation

The Android app pairing screen asking you to approve the phone on your desktop, showing the desktop's certificate fingerprint.
Real screenshot · phone pairing

Your PC's terminals, in your pocket

  • A full remote terminal for every session on your PC.
  • Extra keys: esc tab ctrl alt ← ↑ ↓ →
  • The same quick replies when Claude is waiting for you.
  • Open on desktop focuses that pane on your PC.

Phone and watch each connect to your PC on their own, never through each other.

P3 · Wear OS watch

Animation

A Wear OS watch screen that found your desktop and offers to pair with no code to type.
Real screenshot
A watch waiting for you to approve it on the desktop.
Real screenshot

Answer from your wrist

  • One page per session. Swipe between them.
  • The chip ● Claude needs you shows the agent's actual question.
  • Tap Reply, then Yes, go ahead, No or Continue. TCC types it into the session on your PC.

Replies type text plus Enter into the session. They are not a permission button.

The big screens are real screenshots from the Android emulator. The small pixel devices are drawn animations, not recordings.

WORLD 1-6

PLAYER 1: TCC 0.1.0

High scores

Measured, not promised: five records and a bonus round, each with the conditions it was set under.

  1. 01 430ms Cold start to a promptMedian of 30 launches, PowerShell
  2. 02 29.9MiB On diskThe whole app, 5 files
  3. 03 60.7MiB Idle with one terminalWhole process tree, PowerShell included
  4. 04 40.6MiB The app itself with eight terminals openApp process only, shells excluded
  5. 05 20ms Typing latency, p95Key press to pixels on screen, 100 samples
BONUS 2,889 Automated desktop tests, 0 failingOur own run of the build measured here, 2026-10-08

Measured on one Windows 11 PC (Ryzen AI 9 HX 370), 2026-10-08.

The PC was in normal use, not idle. Cold start means the app was not running, with a warm OS file cache. Some launches take longer: 27 of 30 were under 500 ms.

Email myself the link

Your own mail app opens with the link filled in. No sign-up, and nothing is sent to us.

World 1-7 · Save point

Game saved

Paired to your PC. Cloud is optional.

Save point: Your sessions stay yours.

At home, phone and watch talk straight to your PC over an encrypted connection on your own network. Away from it, Cloud connect goes through a relay that can’t read your sessions: it only forwards ciphertext.

The Remote devices settings with a single-use six-digit code for pairing a phone, which expires in under five minutes.
Real screenshot · Settings › Remote devices, from a throwaway test instance. The QR and code are not reusable.

Save file 1 Account: only for Cloud Relay: ciphertext only Network: yours

Inventory

  • Item 01

    Encrypted

    Phone and watch connect over WebSocket with TLS 1.2 or 1.3.

  • Item 02

    Pinned certificate

    At pairing, the phone pins your PC’s certificate. A different one is refused.

  • Item 03

    Single-use code

    6 digits. Expires in 5 minutes. Burned after 5 wrong guesses.

  • Item 04

    You approve devices

    A watch, and every first cloud connection, asks on your desktop first: Allow or Deny. Cloud shows the key fingerprint.

  • Item 05

    Revoke any time

    Settings › Remote devices › Revoke disconnects a device at once.

  • Item 06

    End to end over Cloud

    The relay forwards only ciphertext. Choose Standard, Strict or Paranoid. Remote resize is off by default.

What the relay keeps: your account email, a password hash, your plan and trial dates, your devices’ names and public keys, which devices you approved and when each was last seen, hashed sign-in and reset tokens, a hashed machine identifier (used only to allow one Cloud trial per machine) and how much cloud data you used each month. Never what you type or what your terminals show: it only ever carries ciphertext.

WORLD 1-8

Insert coin. TCC is not released yet. Save the link and check back.

Send tickets down a Factory line, run every agent in one Windows window, and answer them from your PC, phone or watch.

Keep the link

There is nothing to sign up for yet, so take the link with you.

Email myself the link

Or bookmark it: Ctrl+D on a PC, Share on a phone.

TCC has no public download or waitlist yet. The email opens in your own mail app with the link filled in; nothing is sent to us.

Or play a game while you wait

System requirements1P

  • Windows 10 and 11, x64
  • About 30 MB on disk*
  • Installs without admin rights
  • No account (only Cloud connect needs one)
  • Companions: Android 8.0+ phone, Wear OS watch

29.9 MiB. Measured on one Windows 11 PC (Ryzen AI 9 HX 370), 2026-10-08.