What does Rundock cost?
Rundock is free. You'll need a Claude Pro ($20/mo) or Max ($100/mo) subscription for the AI processing, since Rundock runs on top of Claude Code. Add a ChatGPT plan if you want specialist agents on Codex too. That's the total cost.
What if I'm not technical?
If you can describe what you want, Rundock can build it. You'll spend more time naming your agents than writing code. Doc, the built-in platform agent, walks you through setup and builds your first agents with you.
Why not just use Claude Code?
Claude Code is one engine, and it ties your team to a single provider. Rundock runs the same team across Claude Code and Codex, and lets you move between them without rebuilding. You keep the org chart, the coordination, and the files you own. When a better engine comes along, your team is ready to run on it.
Is Rundock a harness or an orchestrator?
Neither: Rundock runs on harnesses. Claude Code and Codex are the harnesses; they own the agentic loop, tool execution and context management, and they improve without Rundock lifting a finger. Rundock is the layer above: the workspace where a team of harness-run agents is built, managed, observed and improved. If you want a word for it, it's an orchestration layer, but the orchestration primitive is delegation between named agents on an org chart, not a graph you program.
Do I have to design agent graphs or loops?
No. In Rundock the org chart is the graph: roles are the nodes, delegation is the edges, and the loop belongs to the harness. You get what multi-agent graphs exist for (specialisation, parallel work, handoffs, human approval gates) through a structure any manager already understands. Reorganising your team is dragging a reporting line, not a refactor.
How does Rundock relate to best practices for working with AI?
It makes them structural instead of disciplinary. Context engineering: every specialist has a small, role-scoped context, because that's what an agent file is. Reusable procedures: skills are files. Persistent memory: legible markdown you can read and correct, not an opaque store. Human in the loop: the permission model and the review flow. Observability: delegation happens in front of you. You don't follow the best practices. You get them by default.
Where does my data live?
On your machine. Rundock keeps your files, agents and history on your machine. Only the active conversation is sent for processing: to Anthropic via Claude Code, or to OpenAI via Codex if you run specialists on your ChatGPT plan.
Can I bring my context from ChatGPT, Notion, or Claude?
Your workspace is plain markdown files. If you have notes elsewhere, copy them into your workspace and your agents can read them straight away. No import tool, no migration step.
Can my agents work on a schedule?
Yes. Set up routines so your team runs on its own. The weekly research digest, the Monday content review, the overnight email triage. Pick the schedule, walk away, get the output when it's ready.
Does my computer need to be on?
Yes. Your team runs on your machine; when the machine is off, so is the team. Routines run while Rundock is running. A guide to giving your team an always-on home of its own is on the roadmap.
Is this another tool I have to babysit?
There's nothing to host and nothing to maintain beyond updating the app. The team runs when you ask it to, every action that matters asks permission, and the org chart shows you everything at a glance. Rundock is where you already work, not another service to keep alive.
What if Rundock stops being maintained?
Your workspace is yours. Agents and skills are markdown files you own. The code is source available. Worst case, you keep using whatever version works on your machine, or fork it, or take your agents to any tool that supports the Claude agent format.
How long until I'm up and running?
Around an evening. Install Claude Code (10 minutes). Download Rundock and pick a workspace folder (5 minutes). Talk to Doc and let him build your first three agents (30 to 60 minutes). You're running.