One Grok bot per project: a simple trick to keep agent context scoped
jonathan_wilke · x · 2026-10-28
- Developer jonathanwilke shares his Grok Bot setup: one bot per project (the screenshot shows parallel conversations for sedecon solutions, SetSale, supastarter, supatools, Outbid and more), keeping each project's context scoped.
- He asks others how they split their work; the one-bot-per-project approach prevents cross-project context pollution and makes it easy to track each project's progress separately.
More from coding & agent
- Garry Tan: 10-20 subagents running at all times have 'renormalized' my GitHub contribution graph — garrytan · 2026-10-28
- GBrain teases feature where AI loops boot their own Linux machines to get work done — garrytan · 2026-10-28
- SEP-3415: MCP Events extension PR would let agents react to pushes without user polling — braelyn_ai · 2026-10-28
- AMD details warp-pipelining: Triton GEMMs hit 1,437 TFLOP/s on MI355X, matching hand-tuned assembly — xiaosun86 · 2026-10-28
- Are agent harnesses dying? Distillation experiments move scaffolding into the model — rseroter · 2026-10-28
- Running agents on Berkeley's Agents' Last Exam: one task took 400+ checked actions — Fun-Government-8007 · 2026-10-28