8staff

A staff thatactually does the work.

Claude, Codex, Grok, Cursor — signed in as themselves. Named desks. A computer each.

Scout · Maker · Closer

What the staff is for

Every model you already pay for.

Not one chatbot. A floor of named teammates — each with a desk, a standing job, and the CLI you pick. They message like colleagues, work in parallel, and come back when they need Allow.

ClaudeCodexGrokCursorGeminiCopilotKimiSigned in as the vendor built them. Nothing proxied. No borrowed tokens.

All models

The CLIs you already pay for.

Claude, Codex, Grok, Cursor — Gemini, Copilot, or Kimi if they are on this machine. Pick a model per desk. Scout can research on Claude while Maker builds on Codex. 8staff does not resell them, proxy them, or mark them up.

Named desks

Message them like teammates.

A name, a standing brief, a thread that survives the night. First run seeds Scout, Maker, and Closer. “Make a bot named Riley who writes emails” creates Riley and starts the work.

In parallel

Work with many at once.

Drag a chat beside. Three windows, like a real floor. Each teammate has a computer of their own. You are not the router between tabs.

A computer

Each desk has its own machine.

Isolated home folder. Live computer: observe, click, type, terminal, browser. Files stay on the desk, not lost in a reply. Work chips in the thread — not a CLI dump.

Your tools

They sign into what you already use.

Gmail, Calendar, Drive, Slack, GitHub, Notion. Connected on this machine. MCP is Advanced, not the front door. Logins stay here.

Allow

They come back when they need you.

Mail, posts, and anything you would want to see stop at Allow or Deny in the thread. You keep the send button.

The job

Give each one a standing job.

Research, build, outreach — then whoever you hire. The job stays on the roster. Next shift starts briefed, not re-explained.

This machine

Local-first. Free on yours.

Schedules run while 8staff is open. Open at login keeps the night shift. Cloud desks are paid, for work that should survive a closed laptop. We do not markup Claude, Codex, Grok, or Cursor.

How it works

Hire

Name them. Give them a job.

One bot is a name, a standing brief, and a computer of their own. First run seeds Scout, Maker, and Closer. “Make a bot named Riley who writes emails” creates Riley and starts the work.

Two states of the same 8staff office, same camera. Before: 7am, three empty desks, dark screens, unread envelopes, silent threads. After: lights on, Scout’s brief on the front desk, Maker’s files stacked, Closer’s drafts sealed, one Allow chip waiting, the computer still warm.

You slept. They didn’t.

Scout’s brief is waiting. Maker left files on the desk. Closer queued drafts. One Allow sitting on the rail. Same room as last night. Different shift.

  • Scout
    Brief on the desk
  • Maker
    Files stacked
  • Closer
    Drafts queued
  • You
    One Allow
8staff desktop messenger with roster, thread, and computer pane on a laptop.

Open at login. Close the window, they stay.

Desktop for Mac, Windows, and Linux. Messenger plus a live computer pane. They run while 8staff is open on this machine. Open-at-login keeps the night shift actually happening.

Staff the night shift.

Open at login. Close the window, they stay.