Home / Articles / Replicating the agentic inbox / Versions / v1.2.0
Replicating the agentic inbox: what changed in v1.2.0
From v1.1.0 (2026-10-03, a93621273) to v1.2.0 (2026-10-03, 1576cdd8c), paragraph by paragraph.
2 paragraphs added, 0 removed, 0 changed in place, 75 unchanged. About 230 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
← v1.1.0 · all versions · v1.3.0 →
63 unchanged paragraphs, under In short, Why this is on a separate page, The core idea: Claude as a state machine…
The second contribution is a picture rather than a paragraph: the briefs role drew the whole team from the README and the conductor's roster file, as it stood on 2 October. It is worth having here because it shows what this walkthrough leaves out. The roster is twelve agents, not the five of phase 2: alongside the roles above there are @linkedin (LinkedIn conversations, in its own vault), @zapier (WhatsApp relay through Zapier and Twilio, with its policy written and the channel not yet live), @newsroom (the newsroom site), and @abp (the policy vocabulary and each agent's policy). It also shows how an email actually leaves: the briefs or CRM role writes the text as a file, the CRM role registers it, the drafts role puts it in Gmail Drafts, and the person sends. And it corrects a detail in the schedule paragraph above: the conductor runs four times a day on weekdays and twice at weekends, in the order security, drafts, inbox, briefs, CRM, webSummit, abp, dev, security.
[figure inbox-team-roster.webp] The team as the briefs role drew it on 2 October 2026: twelve agents, one owner, grouped by what they touch, with the path an email takes to leave and the order of a run along the bottom. Infographic from the team's README and roster file; no contact named beyond the agent's published address. | narrow
12 unchanged paragraphs, under Threads woven here