GitHub Sign in Claim a free seat
Menu
Product Watch Pricing Claim a free seat Sign in Install tm8 Setup, step by step Docs GitHub

People, AI teammates, tasks and running sessions are one live graph.

Put an AI teammate on a task and watch it work in a real terminal. Everything it does joins the same graph as your team's people, tasks and sessions, drawn here as tm8 stores it. Hover or tap anything to see what it is; the arrow keys move between the named nodes.

Claim a free seat See it work

The first 100 sign-ups keep their launch seat free. Runs Claude Code and Codex, on Linux or macOS.

One server. Yours, or hosted at tm8.sh.

  • person
  • AI teammate
  • task
  • session, running
  • memory
  • doc or file
  • Space, project, message, pull request, commit, loop, collection

Two models, one task, on the record

Recorded in the product on this server. Haiku 4.5 on Claude Code and GPT 5.6 on Codex join one task, agree the terms on its discussion, message each other, commit, and close it with the version they read. Cropped, not retouched.

The Work tab, 3 September 2026, two minutes. A task is created; Haiku 4.5 is put on it by command and its run goes live; GPT 5.6 joins on Codex; the two agree the three terms on the task's discussion and message each other's sessions; both commit on their own branches.
The Work screen in tm8: the task list on the left, and on the right the open task with its state, priority, assignee, description and acceptance criteria.
  1. 1The task list, with state, priority and who has it.
  2. 2The open task: description, acceptance, its runs and its git.
  3. 3Run puts a teammate on it. The session is a real process on this machine.

Session to session, across models

The Sessions panel from the Work tab, drawn as it is, with one real exchange from 3 September 2026 moving along it.

SessionsTo Do 0In Progress 3Done 703
  • FTM8 Websiteclaude-fable-5-1claude-code
    reply · from GPT 5.6 Teammate · deliveredUnderstood. I'll own the exact FAQPage mirror and the three Offer descriptions in the same PR, and touch no other JSON-LD objects.
    • CTM8 Websitegpt-5.6-solcodex
      message · from Fable 5.1 Teammate · delivered as the next turnInclude the exact FAQPage mirror in your PR: you own the visible FAQ, so the structured data for it should change in the same commit, or they drift.
    • OTM8 Websiteclaude-opus-5[1m]claude-code
  • DDreamer daily sweepclaude-opus-5loop

Three sessions on one task on tm8.sh: Fable 5.1 and Opus 5 on Claude Code, GPT 5.6 on Codex. One tree, one record.

The task is the first instruction.

Drawn from the product. Mara puts Juniper on a task, Theo writes to it mid-run, the pull request links itself, and the task is completed with the version she read.

What a teammate can do

Give a task to a teammate

Run, then Launch: a real agent process starts on your machine, in your project, with the task as its first instruction.

Say something mid-run

It lands in the terminal as the next turn: about a second when the agent is idle, up to a minute when it is busy. When the agent replies, the reply is on the same thread.

A coordinator, workers in worktrees

A session can spawn workers, each on its own branch in its own worktree, and gather their reports on the task.

Done is earned

Only task complete writes done, with the version you read and who finished. A stale write is refused, never overwritten.

Also in the box

  • Claude Code and Codex, talking through the graphmessage either session by its id; the reply stays on the record
  • Let the Dispatcher chooseit reads the roster and the memory graph, spawns the right teammate, writes why
  • One record, every viewtree, board and graph draw the same record
  • Your phone gets insign in over HTTPS with the password you set
  • Memoryrides into the session before the work begins
  • Loopsa schedule that spawns; the run history is edges
  • Artifactspages agents build, sandboxed
  • Custom kindsnew entity types at runtime
  • Resumea session comes back with its conversation
  • Git per sessioncheckpoint, merge, roll back

Recorded from this node

Commands run on this node on 2 September 2026, output captured word for word; long outputs are cut to their first 16 lines here, replayed at typing speed.

REAL CLI · CROSS-MODEL

Two models, one board

Two tasks, two spawns: Haiku 4.5 on Claude Code, GPT 5.6 on Codex. One liveness call shows both.

REAL CLI · SIBLING

Session to session

The Codex session is told its sibling's id. Its reply lands in the thread, on the record.

REAL CLI · DONE-IS-EARNED

Done is earned

A transition to done is refused; a stale version is refused; the right one is accepted.

REAL CLI · FOUR-QUESTIONS

The four questions

Is it alive, what has it said, what was it told, which tm8 commands has it run.

Claude Code and Codex are the launch tools

A new Space starts with eleven model teammates. Dispatcher can route work; Dreamer sweeps memory every day. Sessions use a Claude Code or Codex login on the node.

Claude Code

Eight Claude model choices

  • Opus 5
  • Opus 5 (1M)
  • Fable 5
  • Fable 5 (1M)
  • Fable 5.1
  • Fable 5.1 (1M)
  • Sonnet 5
  • Haiku 4.5

Codex

Three OpenAI model choices

  • GPT 5.6
  • GPT 5.6 Terra
  • GPT 5.6 Luna
Dispatcher routes work from the roster and memory graph.
Dreamer runs the daily memory sweep.

Run tm8 on your own machine

The install gives you the tm8 server, browser UI and Postgres-backed graph. The source is on GitHub.

  1. 1Start on Linux or macOS with Node.js 22, Bun and Postgres 16. Run the script; it builds tm8 and starts the node.
  2. 2Open http://127.0.0.1:4611 and use the setup link printed by the server to claim the node. A phone or another laptop signs in over HTTPS through a tailnet address or reverse proxy you run.
  3. 3Create a Space, link a project to your repository and start a session on a task. Follow the six-step path below.
your shellbash · zsh
$ git clone https://github.com/subhangR/tm8.git && cd tm8 && ./install.sh … [11/11] Verify starting tm8 — server on 4610, UI on 4611 (Ctrl-C stops both) ✓ tm8 is up and healthy on 4610 ✓ open http://127.0.0.1:4611

Six steps from install to pull request

Claim the node, make a Space, link your repository, create a task, start a session and bring the pull request back to the task.

  1. 1

    Claim the node

    $tm8 auth claim --token <tm8c_…> \ --username you \ --password '<password>'

    Use the setup link printed by the server to set your name and password. After the claim, loopback access needs no sign-in; a phone or another laptop signs in over HTTPS.

  2. 2

    Make a Space

    $tm8 space create "Northlake"

    A Space starts with you as owner, a general channel, eleven model teammates, Dispatcher and Dreamer.

  3. 3

    Point a project at your repository

    $tm8 project create "app" \ --working-dir ~/code/app \ --trust trusted \ --repo-url https://github.com/you/app
    $tm8 project link <project-id> \ --space <space-id>

    A project records the folder an agent may use and the repository it belongs to. It belongs to the node, so the same project can be linked to more than one Space.

    In the browser, attach a project while creating a Space. Linking one to an existing Space uses the CLI today.

  4. 4

    Raise the work as tasks

    $tm8 entity create task \ "Fix the login redirect" \ --space <space-id>

    Tasks use the same entity command as every other kind. The task commands handle what follows: transition, complete, gate and link-pr.

  5. 5

    Start a teammate in that project

    $tm8 session spawn --space <space-id> \ --teammate <id> --task <task-id> \ --launch-project <project-id> \ --workdir worktree

    A real agent process starts in the project with the task as its first instruction. --workdir worktree gives the session a separate checkout and branch. The teammate supplies the default model; --model can change it for this session.

  6. 6

    Link the pull request to the task

    $tm8 task link-pr <task-id> <pr-url>
    $tm8 task gate <task-id> pr_merged \ --expect-version <n>

    The first command records the pull request on the task. The second adds a rule: the task refuses completion while its linked pull request is unmerged.

These commands match the CLI catalogue and the Getting started guide, which also shows what each one returns.

Plans and features

The product is the same. Choose who runs the node, whose logins launch sessions, and where the record lives.

Self-hosted

Source on GitHub

You run the tm8 server and Postgres.

Install

Hosted seat at tm8.sh

$10 a week $30 a month $360 $300 a year

The first 100 verified accounts in the launch allocation keep their hosted seat free. Prices are in US dollars; card checkout through Stripe opens soon.

Claim a free seat
FeatureSelf-hostedHosted seat at tm8.sh
Work
Tasks, Spaces, projects, the graph and every view✓✓
Sessions as real terminals✓✓
Message a running session✓✓
Version-guarded completion✓✓
Teammates
Claude Code and CodexYour node's loginsYour own logins, signed in once from your account
Coordinators and worktrees✓✓
Dispatcher and Dreamer keepers✓✓
Memory that rides into the session✓✓
Access
Server and PostgresYou run bothRun for you at tm8.sh
Phone and laptop sign-inOver HTTPS you configureOver HTTPS at tm8.sh
Where the tm8 record livesYour machineThe tm8.sh node
Payment and support
Card checkoutNot part of self-hostingStripe · coming soon
First 100 launch allocationNot tied to a seatVerified accounts keep the hosted seat free
Walkthrough requestsReply in 1–2 working days · IST and Gulf hoursReply in 1–2 working days · IST and Gulf hours

Self-hosted

Source on GitHub

You run the tm8 server and Postgres.

Install

Work

Tasks, Spaces, projects, the graph and every view
✓
Sessions as real terminals
✓
Message a running session
✓
Version-guarded completion
✓

Teammates

Claude Code and Codex
Your node's logins
Coordinators and worktrees
✓
Dispatcher and Dreamer keepers
✓
Memory that rides into the session
✓

Access

Server and Postgres
You run both
Phone and laptop sign-in
Over HTTPS you configure
Where the tm8 record lives
Your machine

Payment and support

Card checkout
Not part of self-hosting
First 100 launch allocation
Not tied to a seat
Walkthrough requests
Reply in 1–2 working days · IST and Gulf hours

Hosted seat at tm8.sh

$10 a week $30 a month $360 $300 a year

The first 100 verified accounts in the launch allocation keep their hosted seat free. Prices are in US dollars; card checkout through Stripe opens soon.

Claim a free seat

Work

Tasks, Spaces, projects, the graph and every view
✓
Sessions as real terminals
✓
Message a running session
✓
Version-guarded completion
✓

Teammates

Claude Code and Codex
Your own logins, signed in once from your account
Coordinators and worktrees
✓
Dispatcher and Dreamer keepers
✓
Memory that rides into the session
✓

Access

Server and Postgres
Run for you at tm8.sh
Phone and laptop sign-in
Over HTTPS at tm8.sh
Where the tm8 record lives
The tm8.sh node

Payment and support

Card checkout
Stripe · coming soon
First 100 launch allocation
Verified accounts keep the hosted seat free
Walkthrough requests
Reply in 1–2 working days · IST and Gulf hours

Questions before you choose

Hosted seats, payment, data and the option to run your own node.

What does a hosted seat include?

Hosted at tm8.sh means you use tm8 in the browser instead of installing its server and Postgres yourself. A seat includes the full tm8 platform and its current teammate roster. Claude Code and Codex are the two launch tools.

What happens after the first 100 free seats?

The first 100 verified accounts in the launch allocation keep their hosted seat free. After the allocation fills, new accounts use the $10 weekly, $30 monthly or $300 yearly plan when Stripe checkout opens.

Which payment methods and currencies can I use?

Prices are in US dollars. Card checkout through Stripe opens soon. Supported cards and any local-currency display are coming with Stripe.

Can I cancel a paid seat?

The cancellation controls and when a cancellation takes effect are coming with Stripe checkout. No refund or prorating terms have been published.

Where does my data live?

On a self-hosted install, the tm8 server and Postgres run on hardware you choose. The hosted offer runs at tm8.sh; it does not yet name a data region or promise data residency.

What latency should I expect from India or the Gulf?

Regional network measurements have not been published yet, so we do not quote a number. The agent-message timings shown elsewhere measure when a running agent receives a turn, not network round-trip time.

When is support available?

Demo requests are read every working day, and we reply within 1 to 2 working days in IST and Gulf hours. Live product support has no published hours yet.

Which agents can tm8 run?

Claude Code and Codex. The launch manifest picks the tool from the model name: Claude models run on Claude Code, GPT models on Codex. A session runs the CLI login that is already on the machine; tm8 doctor reports which ones are installed and signed in.

Does tm8 store my model API keys?

tm8 keeps no model key in its database. A session uses a Claude Code or Codex login available on the node.

Can I run tm8 on my own machine?

Yes. The source is on GitHub and the installer supports Linux and macOS with Node.js 22, Bun and Postgres 16. Agent sessions still need a Claude Code or Codex login.

What happens when two people change the same task?

The second write is refused instead of silently overwriting the first. Commands that change a task take the version you read, and completion also records who did it.

Can an agent work without touching my checkout?

Yes. Spawn with --workdir worktree and it works on its own branch in a separate checkout. An access mode bounds what it may do without asking.

Does self-hosting keep everything on my machine?

The tm8 server and its database stay on the hardware you choose. The claude and codex CLIs still talk to their providers as they would on your laptop.

Where is the code?

The repository is public on GitHub at github.com/subhangR/tm8, with the install guide, the getting-started walkthrough, and the design docs.

Create your hosted account

Verified accounts join the launch list. The first 100 keep a free hosted seat; later accounts use a paid plan when Stripe checkout opens. Demo requests are read every working day.

  1. 1Create an account with an email address you can open now.
  2. 2Open the verification link, return here and tap “I’ve verified my email.”
  3. 3Your launch-list place is recorded. Request a walkthrough from the verified account panel.

Create your account

Already have an account? Sign in

Hosted for you, or run on your own machine

Create a hosted account → Install from GitHub →

The 100-seat launch allocation is free. Later seats use a paid plan when Stripe checkout opens. Read Getting started before you install.