01 · 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.
Product
Named teammates. Every model you already pay for. A computer each. Four moves, then the night shift.
01 · Hire
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.
02 · Connect
Gmail, Calendar, Drive, Slack, GitHub, Notion. Claude, Codex, Grok, or Cursor — signed in as the vendor built them. Logins stay here. The 8code app is not required.
03 · Work
Live computer: observe, click, type, terminal, browser. You see work chips in the thread, not a CLI dump. Allow or deny in place.
04 · Learn
A local notebook of what actually worked. Briefed vs control, measured on your machine. Consent-gated. Stored here, not a cloud brain.
Instead of a chat window
What the staff is 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
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
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
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
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
Gmail, Calendar, Drive, Slack, GitHub, Notion. Connected on this machine. MCP is Advanced, not the front door. Logins stay here.
Allow
Mail, posts, and anything you would want to see stop at Allow or Deny in the thread. You keep the send button.
The job
Research, build, outreach — then whoever you hire. The job stays on the roster. Next shift starts briefed, not re-explained.
This machine
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.
Then the night shift
01
macOS, Windows, Linux. Its own app.
02
Claude, Codex, Grok, or Cursor — in this app. Logins stay on this machine.
03
Scout, Maker, and Closer are already on the roster.
04
Schedules while 8staff is open. Open at login, so the night actually happens.