The Company Selling You AI Product Managers Doesn't Give Its Own Agents Job Titles: Roles, Isolation, and Code in Multi-Agent Systems
Grok Bot markets agents as named coworkers like sales or finance, but its engineering core Grok Build uses only functional names such as researcher-0 and verifier—zero personas. The article breaks multi-agent design into three layers: the mechanism layer relies on context-window isolation for output quality; the orchestration layer decides who controls the next step (teammate persona, main agent, or script); the interface layer uses job hats to lower the human adoption barrier. Hats solve three human problems—delegation intuition, approval anchors, and memory partitioning—but do nothing for model reasoning. All coworkers under one account share the same cloud computer and credentials; security boundaries depend solely on manual approval gates. When building your own system, nail window isolation first, then pick an orchestration style based on task reliability needs, and save persona packaging for last.
Why it matters: Grok Bot presents agents externally as named colleagues while the engineering core uses only functional IDs like researcher-0, and the article uses that gap to examine context isolation and role design in multi-agent systems.