AI Agent Coordination ★ GitHub

Your agents are stepping on each other. AgentPeek fixes that.

A native macOS daemon with an MCP server. AI agents lock files, serialize installs, and share state — without conflicts.

brew install adamorad/tap/agentpeek

Works with Claude · Cursor · Copilot · Cline · Windsurf · any MCP-compatible agent

Built by Adam Morad
How does it compare?
The Landscape

Other tools store memory.
AgentPeek prevents conflicts.

Whole categories of tools touch this space — session-scoped MCP servers, memory layers, DIY locks. They answer "what happened." AgentPeek answers "what's happening right now."

Session-Scoped MCP Servers Node · per-session

Some MCP servers offer locks or a task queue, but they live and die with the session that spawned them. Two sessions means two servers means no shared state.

  • Outlives sessions
  • Cross-session locks
  • Zero dependencies
  • MCP-native
Memory Layers mem0 · knowledge graphs

Store what an agent did so it can recall it later. They answer "what happened" — not "what is happening right now."

  • Resource locking
  • Real-time arbitration
  • Recall / memory
  • Zero dependencies
DIY (Redis · lockfiles) roll your own

Technically capable, but invisible to your agents: no MCP surface, manual setup, and lockfiles crash-deadlock with no TTL.

  • Resource locking
  • MCP-native
  • TTL auto-expiry
  • Zero setup
This one
AgentPeek new

Native macOS daemon that gives every agent a shared coordination layer — named locks with TTL, shared notes, no cloud.

  • ✓ Always-on daemon
  • ✓ Cross-session locks + TTL
  • ✓ MCP-native
  • ✓ Zero dependencies

Session-scoped servers die with the session that spawned them. AgentPeek is a daemon — it outlives every session and arbitrates between all of them.

vs. other approaches
Why AgentPeek

Three approaches.
One that actually works.

How do your agents coordinate shared resources when they all run at once?

🖥️
Shell Workarounds
lockfiles · flock · manual scripts
  • Resource lockingNo atomic, named locks
  • Shared stateNo key-value notes
  • Persists across restartsNo
  • Multi-agent safeNo — race conditions
  • Runs as daemonNo
  • Works across toolsNo
⚡
Session-Scoped Skills
claude code skills · one session
  • Resource lockingNo cross-session locking
  • Shared stateNo shared state
  • Persists across restartsNo
  • Multi-agent safeNo — one session only
  • Runs as daemonNo
  • Works across toolsSession only
Recommended
🔒
AgentPeek MCP
agentpeek · shared daemon
  • Resource locking✓ named, with TTL
  • Shared state✓ key-value notes
  • Persists across restarts✓ UserDefaults
  • Multi-agent safe✓ any MCP client
  • Runs as daemon✓ LaunchAgent
  • Works across tools✓ Claude+Cursor+Copilot

Shell scripts and skills give one agent visibility for one moment. AgentPeek gives every agent a shared coordination layer — Agent A locks npm-install, Agent B sees it's held and backs off. No conflicts. No manual work.

See the 7 MCP tools
7 MCP Tools

Everything agents need to coordinate.

All tools available on 127.0.0.1:27183 — any MCP-compatible agent, one shared daemon.

Locks
lock_resource unlock_resource renew_lock list_locks
Scratchpad
set_note get_note list_notes

Install via Homebrew

Installs the binary and places the LaunchAgent plist on your system.

brew install adamorad/tap/agentpeek

Load daemon

Register with launchd so AgentPeek starts automatically at login.

cp $(brew --prefix)/share/agentpeek/com.agentpeek.daemon.plist ~/Library/LaunchAgents/ && launchctl load ~/Library/LaunchAgents/com.agentpeek.daemon.plist

Configure agent

Add to ~/.claude/mcp_servers.json

{"agentpeek": {"transport": "http", "url": "http://127.0.0.1:27183"}}
v2 in design: blocking waits · atomic counters · Linux — read the roadmap →
← Back to top