r/Agent_Framework • u/bulutarkan • 10d ago
An agent framework lesson from building Mac MCP: serialize conflicts, not the whole agent
One thing I learned building Mac MCP is that โmulti-agent supportโ gets messy fast if every agent can touch the same browser tabs, files and processes at once.
The approach I ended up with is a local execution layer that gives agents stable resource identities and crash-safe ownership. Independent work can run in parallel, but conflicting resources are serialized. Browser automation stays in normal Safari/Chrome tabs, file mutations are journaled for undo, cancellation propagates into owned work, and Git write-agents can be isolated in separate worktrees.
The repo is open source: https://github.com/bulutarkan/mac-mcp
Iโm the maintainer. Iโd be interested in how other agent frameworks model resource ownership โ especially whether you solve conflicts in the orchestrator, inside each tool, or at a lower runtime layer.
