Use Claude or Codex directly to push a weeks-long project and you soon become the messenger. Putting several models in a group chat is no different: they all read the same ever-longer transcript, and nobody keeps the books.
The models are strong enough. The problem is structure: they are organized as project → conversations; Vermilion is project → goals → tasks. In Claude or Codex, a project is a string of ever-longer chats. In Vermilion it is a tree of goals and tasks, and every card has someone doing it, someone checking it, and a state.
Claude / Codexproject → conversations
- My project
- 💬 Help me plan a login feature
- 💬 Write the code for this plan (copied from the last chat)
- 💬 Let's pick up from yesterday… (background retold)
- 💬 Can you check it for problems again?
- 💬 …
Conclusions are scattered across chat logs. Who did what, how far it got, and what's waiting on you: only you remember.
vs
Vermilionproject → goals → tasks
- My project
- G001 Ship login
Approved
- T1 Plan Claude does · Codex reviews
Passed
- T2 Code Codex does · Claude checks
In progress
- T3 End-to-end check DeepSeek checks
Not started
- G002 Redesign home page
Awaiting approval
Every card says what's wanted, who does it, who checks it and how far it got. Switch models or sessions and work picks up from "▶ Next".
Claude / Codex directlyWith Vermilion
Unit of workA conversationA goal, split into task cards
Planning and staffingHow to split it and who gets what is all on youThe Lead builds the plan and picks members by capability; you approve once and work starts
WorkspaceOutput scattered in chats, drafts mixed with finished workcollab/ is the ledger, work/ holds results: one delivery per task, one desk per member
ContextStuck in chat history, retold every session; in a group chat everyone reads everythingKept in the project's collab/; each member gets their own slice for their seat, and work picks up from "▶ Next"
Several models togetherYou copy and paste between windowsThe Lead dispatches; members work in their own CLIs; results are logged automatically
Who comes to youEvery model, after every stepThe Lead handles members and solves what the plan covers; only real blockers reach you, with options and a recommendation
Multi-model discussionYou ask each in turn and relay their answersMeetings: each speaks independently and reviews the plan, you rule, and the transcript is kept
Who says it's doneThe model that did itAnother model checks it against the success criteria and sends it back if it falls short
What you manageEvery stepThree things: approve the plan, decide "Needs your decision", confirm completion
Progress and costScroll through chatsThe board shows it at a glance: who's working, what's stuck, how many tokens