THIS GUY RECREATED THE OFFICE BUT EVERY CHARACTER IS A CLAUDE CODE AGENT RUNNING LOCALLY michael scott is an agent. dwight is an agent. jim is an agent every single character is a separate claude code instance with its own personality and role they're all running locally on his... machine interacting with each other in real time and it's actually a full multi-agent orchestration system here's how it works: > michael is the "god" agent. he orchestrates everything, never implements. he fans out tasks to the other agents, handles conflict resolution, QA, and all github changes > each agent gets assigned real tasks like writing blog posts, handling context engineering, scheduling missions > there's a kanban board with TODO, DOING, BLOCKED, and DONE columns tracking every agent's work > each agent has its own memory file and semantic search via something called MemPalace > there's a live graph showing how all the agents communicate with each other in real time > michael runs an hourly standup mission where he collects work from all agents, dedupes it, runs QA, builds, and publishes you can spawn new agents from a panel where you pick the character (michael, jim, pam, dwight, kevin, angela, oscar, stanley, andy, kelly, ryan, toby, creed, meredith), choose the model (opus 4.8, sonnet 4.6, haiku 4.5), set a goal, and hit spawn kevin walks around saying "why waste time say lot word" michael's QA gate actually caught real issues before publishing. trimmed meta descriptions, caught duplicate flags, found a dedup trap where jim's commit was built from HTML only with no source the agents commit source-only on their own branches michael dedupes, builds once, and publishes this is the most over-engineered and simultaneously most beautiful multi-agent system anyone has builtshow more

Om Patel

24,889 subscribers

Paylaş İndir