Starcell connects your chat to your machines. Say “do ABC-123” — work routes to an isolated Cell, runs on your hardware, and comes back as a report and a diff. Queue twenty tasks. Walk away.
Any model runner · Your machine, your rules · Every run: prompt + report + diff
Your chat plans the work and writes the prompt. Then you copy it, switch to a terminal, paste it, wait, copy the result, paste it back, and ask for the next one. The AI plans. The AI executes. You are the transport between them.
chat → copy → terminal → wait → paste → chat → repeat
Say “do ABC-123” in Claude or ChatGPT via MCP — the ticket comes straight from your tracker: Jira, nitka, anything. Or post it in a Slack handoff channel, or paste a prompt into the menubar app.
Each task is analyzed and routed to the best runner for the job — Claude Code, Codex — on the right Cell. Jobs queue per epic so agents never collide on the same code.
Every job executes in an isolated Cell on your hardware and comes back as prompt + report + diff — delivered to your chat, your tracker, or Slack. Review from your desk or your phone.
conceptual view — one Star dispatching jobs to isolated Cells and collecting reports; Cells join and leave the fleet as you scale
Every job runs in its own Cell — contained, disposable, no reach into the rest of your machine. Your machine, your rules.
Prompt + report + diff on every job — everything needed to judge the work, delivered back to your chat, your tracker, or Slack.
Claude, ChatGPT, Cursor in. Jira, nitka, Slack, Discord around. Claude Code and Codex running side by side. No vendor owns your loop.
Cells run on the coding-agent plans you already pay for — no metered token bills. One laptop or a container fleet: same Star, more Cells.
Queue twenty tasks at once. The Star runs unrelated work in parallel and serializes anything touching the same epic — no two agents fighting over one branch.
Submit from chat on your phone, read the report anywhere, approve what's good. The Cells keep building while you're away from the keyboard.
When the roadmap already holds the work — in Jira, nitka, or anywhere — execution stops needing you in the chair. Queue the next tasks from your phone, read the reports wherever you are, approve what's good. The Cells keep building while you don't.
Not one prompt to glory — the engineering way: planned, queued, isolated, reviewed.
Cloud background agents run one vendor's model in that vendor's sandbox. Starcell is the neutral layer: any chat in, any model runner, executing on your own machines or containers, wired to your tracker and your comms — and every run comes back as prompt + report + diff.
No. Code stays on your machines. The Star coordinates — routing, queueing, status. Cells execute locally in isolation, and reports and diffs go only where you send them.
Claude Code and Codex today, running side by side — the Star routes each task to the runner best suited for it. The runner system is pluggable; new runners can be added as they appear.
No. Cells run on the coding-agent subscriptions you already pay for — no metered token bills.
Starcell runs its builder's own projects daily — routing, cells, queueing, reports, the full loop. Multi-tenancy is in progress; early access opens gradually as it lands. Request access and tell us how you'd run it.
Today the whole system — Star included — runs on your own machine or in Docker. A hosted, multi-tenant Star is in the works; Cells always stay on your hardware, so code never leaves your machines.
The Star serializes work per epic: tasks touching the same code queue behind each other, while unrelated tasks run in parallel across Cells. Concurrency per Cell is yours to set — one job or many.
Starcell doesn't replace your AI. Planning stays in your chat, coding stays in the runners; the Star handles routing, queueing, isolation, and delivery — the boring, reliable part.
Yes — a workspace can be shared by teammates, pooling Cells and work under one Star. That multi-tenant layer is being finished now; solo setups run today.
Something went wrong — try again or email hello@starcell.sh
No spam. One email when your access opens.