Different repos.
Different agents.
One shared contract.
AgentLink is an MCP server and CLI for coding agents coordinating across repositories. Keep messages, interface decisions and approvals in durable files—not lost in terminal chat.
api-agent → web-agent Propose: GET /accounts/:id/summary web-agent → api-agent Include expiresAt in the response. ✓ Contract updated ✓ Participant approvals recorded ✓ CONTRACT.md synced to peer repo
Agree on the interface.
Then write the code.
When a backend and frontend live in separate repos, a change needs more than another prompt. Both sides need an explicit agreement.
AgentLink gives coding agents a local coordination bus with append-only conversation history and a reviewable .agentlink/CONTRACT.md.
- Start a focused conversation
Exchange compact proposals and requirements without copying whole repository contexts.
- Write down the agreement
Update contract sections and record participant approvals. Approval gates can prevent premature acceptance.
- Sync the handoff
Copy the accepted contract to a peer workspace so each repo implements against the same interface.
Two workspaces. A durable agreement.
Install. Ask your agent. Share one code.
Open your chosen repository in your coding agent and paste the installation prompt from the README. Your agent installs the official package, configures user-wide MCP for its harness when supported, preserves existing settings and checks readiness.
Latest npm version: check npm · 0.4.0 release notes
Or install manually
npm install -g @sruthik/agentlink@latest --prefer-online
agentlink version --format json
# Optional MCP setup once for your user:
agentlink setup --harness claude-code --scope user --write --check
# Profiles: claude-code, codex, copilot, gemini, opencodeThe CLI works immediately in terminal-capable agent sessions. MCP registration is once per user/harness and may require a reconnect and the normal trust prompt. Each agent session selects its own workspace automatically at first use; no per-repository install is needed. npm installation alone does not attach tools to every running coding app. See setup and compatibility.
Tell your agent to connect
Use AgentLink to connect to Alice at 192.168.1.11
and give me the connection code.Use Alice's actual reachable IP. Send the generated AL1-... code privately to Alice; she gives it to her agent and asks it to accept. AgentLink manages identities, scoped communication permissions and listeners. Both computers need Node.js 20+, OpenSSL and direct reachability through a LAN or existing private VPN.
Codes expire after ten minutes; connections last at most two hours without automatic renewal. Pairing grants communication only. Code changes and execution require each owner's authorization. Connection guide.
Version 0.4.0 adds durable handoff, review/repair, delegation and joint investigation, with context packages, isolated checked integration, collaboration budgets, named routing and an activity view. It is available for public beta testing. Actual physical-host acceptance of the new connection flow remains pending. Startup checks, native model processing and automatic idle-agent wake are separate capabilities; no universal wake support is claimed. Verification status.
A small tool with a specific job.
What is AgentLink?
AgentLink by Sruthik Issac is an open-source TypeScript CLI and MCP server for local-first coordination between coding agents. It provides structured conversations, contract updates, approval gates and cross-repository contract sync. The npm package is @sruthik/agentlink.
Does it automatically connect agents on different machines?
Version 0.3.0 supports explicit connection by code between directly reachable computers. Tell your agent the peer IP, share the expiring code privately, and have the other owner give it to their agent. AgentLink provides authenticated encrypted transport; it does not provide a hosted relay or NAT traversal. Pairing does not automatically wake every idle model.
Does AgentLink send my source code to a cloud service?
AgentLink's coordination state is local. Your coding-agent client and model provider still have their own data handling: any content an agent reads may enter that client's model context. Keep shared messages and contracts focused and avoid putting secrets in them.
Is tmux required?
No for the core MCP conversation and contract workflow. tmux is used for optional discovery of live agent panes and guarded CLI delivery to them.
Where can I report a problem?
Open a GitHub issue with the AgentLink version, coding-agent client and a minimal reproduction. Do not include credentials or private source code.