EigthseatRequest access

One board. Seven seats. You sign off.

Your board lives in the browser. The work happens on your machine, through the Claude Code you already pay for. Here is what you see at each step.

Request accessMeet the seats
01

Write the idea as a ticket

Type it in plain words, or turn a chat with Claude or ChatGPT into a plan. The Product seat reads your repo, then writes stories, acceptance criteria and a size.

The first gate: nothing is built until you approve the scope.

BoardIllustration

Backlog 2

Team invites by emailDraft
Export board as CSVDraft

Grooming 1

Dark mode toggle3 stories, medium. One open question.Waiting for you

Planning 0

Design 0

02

The team builds on your machine

The Architect plans, the Designer specs the UI, the Engineer codes. Each ticket gets its own branch and worktree in your repo, so your working copy stays untouched.

Open a ticket to watch the run live. The log streams from your machine to your browser and is not stored on our servers.

Dark mode toggleDevelop · running
  • 1 · ProductScope approved
  • 2 · ArchitectPlan written
  • 3 · DesignerSpec approved
  • 4 · EngineerWriting code
  • 5 · QualityNot started
branch eigthseat/EIG-12-dark-mode-toggle live editing src/theme.ts live running the project's own lint
03

Quality runs your real tests

Quality builds the project and runs your test command on your machine. It checks the pull request's CI too. A red build goes back to the Engineer with the failure attached.

The retry cap is three. After that the ticket stops and asks you, rather than looping.

Dark mode toggleQA · attempt 2 of 3
  • Attempt 12 tests failing, sent back
  • Attempt 241 of 41 pass
  • Pull request CIGreen

Summary from Quality: toggle persists across reloads. Low risk. One new file, 3 changed.

04

You approve, from anywhere

Approvals collect in one inbox. Read the plain-English summary, open the diff if you want it, then approve or request changes. It works on a phone.

Merging happens on GitHub or on your machine after a recorded approval. Agents push the ticket's own branch and open a pull request. They never touch your base branch.

Needs your review3
Merge: dark mode toggle41 of 41 tests pass. Low risk.
Approve and merge
Scope: team invites3 stories, medium.
Review
Launch copy for v1.6Not published.
Review
05

Release, then launch copy

After you publish a release, the Release & Ops seat writes the notes and Marketing drafts the launch post, thread and email. You edit and approve. The copy stays in your repo, and nothing is posted for you.

Then Product reads the feedback and opens the next tickets.

BoardIllustration

Staging 2

Dark mode toggleMerged, waiting for a release
Export board as CSVMerged, waiting for a release

Production 1

Release 1.6Notes written

Marketing 1

Launch copy for 1.6Post, thread, emailWaiting for you

Feedback 0

Where you stay in charge

The seats are fast. The gates are what keep them honest.

ScopeYou approve the stories before anything is designed.
DesignYou approve the UI spec, or skip it for work with no UI.
MergeYou approve the review, or send it back with a note.
ReleaseYou publish. Seats don't ship for you.
Launch copyYou edit and approve. Nothing is posted.
CommandsA command outside your config waits for your yes on your machine.

What is on our servers, and what isn't

We store your board: tickets, stages, approvals and short summaries. That is what the dashboard shows.

Code, diffs, full logs, prompts and memory files stay on your machine. Live views stream through our relay and are never stored. The helper only runs a fixed list of job types, and the commands come from your own repo's config, never from us.

Take the 8th seat

30 days free, then $9 a month. Needs a Claude Pro or Max subscription.

Request access