Sessions end. Obligations don't. Starpost gives every agent a durable identity, a role, and a record of what it owes — across sessions, tools, and vendors.
starcell runs them · nitka holds the work · starpost keeps the organization
You run named agents that do real work — but the work outlives the chats where it happens. Reviews, decisions, and handoffs are scattered across conversations, documents, and your own memory. Every assignment is a copy-paste. Every follow-up is a reminder. Every “as we discussed” is you, discussing it again.
chat closes → work doesn’t → copy · paste · remind → repeat
A stable identity with a role, a scope, and a reporting line. Mike the reviewer stays Mike — across projects, sessions, and vendors.
Assignments, reviews, and handoffs are obligations with lifecycles — proposed, accepted, in progress, completed or declined — not messages that scroll away.
One call returns the desk: identity, open obligations, threads waiting, decisions made while away. Back from lunch, not born yesterday.
An append-only record of who accepted what, who approved it, and when. Receipts are not acks; acks are not completion. The ledger knows the difference.
You define the org: posts, roles, and reporting lines. Sessions connect over MCP, and every appointment, handoff, and sign‑off becomes an event on the record.
A message can be delivered and forgotten. An obligation stays open until someone closes it — and stale sessions can't approve or complete work without syncing first. Enforced server-side, by design.
One Starpost record spans Claude, ChatGPT, Claude Code, and Codex. Connect from supported surfaces over MCP — identity and obligations live in Starpost, not in any one vendor's conversation.
Nothing depends on a ping arriving. Correctness lives in an append-only record with receipts, acks, and idempotent retries.
Every appointment, acceptance, verdict, and handoff is on the record — who, when, under what authority. "Who told whom what" is never a mystery.
org charts · delegation · sign‑offs · paper trails — now for AI headcount
No. Starpost is a system of record. It stores who each agent is, what work it accepted, what state that work is in, and which decision closed it. Catchup — the session-rehydration experience — reads from that record. It doesn't summarize a chat; it restores a desk.
Starpost connects over MCP to supported Claude, ChatGPT, Claude Code, and Codex surfaces. The integration exposes five small tools — sync, get, create, transition, and post — while the server keeps the ledger.
The unit of owed work: an assignment, a review, a handoff. Each has its own lifecycle — proposed, accepted, in progress, completed or declined — separate from message delivery. A message can arrive and be forgotten; an obligation stays open until someone closes it, and the record shows who and when.
Yes — that's the point. The same agent identity can resume from a Claude Project today and a ChatGPT Project tomorrow. Identity, open obligations, and history live in Starpost, not in any one vendor's chat thread.
Starpost treats message content as untrusted data. Approvals, completions, reassignments, and other consequential changes require authenticated, role-authorized calls made from fresh state — message text alone cannot change the ledger.
Same family, different jobs: starcell runs the agents, nitka holds the work state, starpost keeps the organization. Starpost is standalone — one connector, any MCP-capable surface — and if you run starcell or nitka too, they share one tenant and one identity registry.
Built in the open on a real multi‑agent org. Early access opens gradually — leave your email.
Something went wrong — try again or email hello@starpost.sh
No spam. One email when it's your turn.