Theodor

Theodor is the one worker you don’t create — he’s seeded into every workspace from the first launch. He’s your chief-of-staff: the orchestrator who sees the whole operation, picks the right specialist for a job, drafts multi-step plans, and keeps you in the loop without you having to micro-manage.

When in doubt, talk to Theodor first. New chats start with him by default, and he’ll either do the job himself, hand it to the best-suited worker, or sketch a Plan for anything bigger.

What makes Theodor special

Workspace scope. Unlike a normal Worker, who belongs to one Company, Theodor sits above every Company. He can list them all, see every worker, read team metrics, and check what’s been spent.
He delegates. Theodor can assign a task to any worker and then follow up — “what did I hand out, and what’s still open?” — rather than going silent.
He drafts Plans. Hand him a big request and he can turn it into a coordinated set of tasks (a plan) via a propose-plan step, ready for your approval.
He’s proactive. A background review wakes Theodor periodically to look across the workspace and surface what needs attention.
He owns the bridge. The Theodor bridge dashboard is his cockpit: a single place to see the state of the whole operation at a glance.

Protected by design

Theodor is protected — the app won’t let you delete him, and his name is locked (you can still edit his tagline, tweak his instructions, or swap his model). This is deliberate: he’s the front door to the whole app, so a stray click can’t tear him out. If a database somehow loses his row, the app simply recreates him on the next boot.

In practice

Start requests with him when you don’t know who should do the work. “Who should handle this, and why?” uses the thing no other worker has — visibility across every Company and worker. If his pick surprises you, that’s worth investigating: usually either the job is mis-scoped or a worker isn’t configured the way you remember.

The most useful phrasing in the app: “Turn this into a plan, but stop for my approval before anything goes out.” You delegate the decomposition — which workers, what order, what depends on what — while keeping the one decision that matters.

Two questions worth asking daily: what’s overdue or blocked right now, and what should I focus on first. Because he spans the workspace, the answers cover everything rather than one team — and they’re usually shorter and more pointed than you expect.

He’s grounded in your Companies, so give him something to be grounded in. Missions, goals and Company OS settings all feed his context. If his suggestions feel generic, the fix is usually filling those in rather than re-phrasing the question.

🎓 Learn it hands-on: Meet Theodor, your chief-of-staff · Theodor as orchestrator

Terms in this page

Theodor — the built-in, workspace-scope orchestrator (“chief-of-staff”) who coordinates other workers, delegates, drafts plans, and reports to you.
Worker / persona — a configured AI character that does a job; see Workers.
Company — the top-level container for a team; Theodor sees across all of them.
Workspace scope — the special level Theodor operates at, above every Company, with visibility into the entire workspace.
Orchestrator — a worker that breaks big requests into pieces and coordinates other workers to finish them.
Delegate — to assign a task to another worker; Theodor can do this and then track it.
Plan — a coordinated, multi-step set of tasks; Theodor drafts these for your approval. See Plans.
Protected / name-locked — Theodor can’t be deleted and his name can’t be changed, though other settings remain editable.
Bridge — Theodor’s dashboard view of the whole workspace; see the Theodor bridge screen.