Mesh Architecture for AI Agents: Client Isolation and Cross-Project Coordination
Mesh vs. Hub-and-Spoke Architecture
The author contrasts their mesh approach with the hub-and-spoke model popularized by setups like Daniel Miessler's PAI. In hub-and-spoke, one central assistant with shared memory handles all workflows, which trades depth for breadth. The mesh architecture creates domain-specialist agents for each client's project, with each agent carrying deep project context without competing for memory space.
System Implementation Details
The system uses plain markdown files and naming conventions for coordination:
STATE.mdfor working memoryCLAUDE.mdandAGENTS.mdfor agent instructions- Structured memos for cross-project communication
- Git for version control underneath everything
There's no database, no platform, and no dependencies beyond CLI tools. Each project is its own node with its own state and instruction files, ensuring Client A's context is isolated from Client B's session.
Cross-Agent Communication
Agents coordinate by dropping structured memos (plain markdown files) into each other's incoming directories, similar to emails passing between team members. Examples include:
- A content agent finishing a draft that the developer agent picks up next session
- A sysadmin agent finding a bug and sending it to the web dev agent
- Infrastructure changes affecting websites
- Content decisions depending on project management input
- Requirements specs triggering development work
For projects needing true isolation where SSH access would defeat the purpose, the memo system extends to email so there's no direct access between environments.
Tool Agnostic Approach
The author uses Claude Code, Codex, Gemini CLI, and DeepAgent across different projects. Because the conventions are just files, there isn't a noticeable vendor boundary—a Claude agent can send a memo that a Codex agent picks up. Swapping vendors to meet project needs is a standard part of the workflow.
Practical Results
This system has been running on real client work for about a year, handling 44 projects across 14 organizations. The author previously carried all coordination between agents but now just reviews work instead of passing it along.
📖 Read the full source: r/ClaudeAI
👀 See Also
Reducing AI Agent Costs by 30% Through Behavior Monitoring and Configuration Changes
A developer cut their OpenClaw bot's token usage by 30% after discovering 70 cron jobs were dumping results into the main chat session, causing context bloat and repeated compaction. The fix involved redirecting cron outputs directly to Telegram and building a monitoring skill to identify inefficiencies like redundant searches and oversized file reads.
Solo Founder Builds News Analysis Platform with Claude Code: Lessons on Scaling and Debugging
A solo founder without a CS degree built The Daily Martian, a news analysis platform analyzing 40+ outlets using Python/FastAPI, PostgreSQL, Redis, and React/TypeScript, primarily through Claude Code. The developer shares specific challenges including context loss, database connection issues, and debugging strategies.
How Claude Code Agents Coordinate in Production: Orchestrator Insights
A team running six specialized Claude Code agents (coder, designer, marketing, QA, security, operations) that autonomously ship features, designs, and social content daily details their orchestrator system. They cover task dispatch, agent handoffs, failure scenarios, and why state machines beat message queues for coordination.
Using Claude Code for Go-to-Market Operations: Context Engineering Patterns
A developer shares practical patterns for using Claude Code beyond coding, specifically for running go-to-market operations including scraping, enrichment, databases, email infrastructure, and multi-platform content. Key techniques include CLAUDE.md files, session scoping, CLI tools over MCP servers, and subagents for heavy lifting.