Roadmap

ClaudeLink is open source and developed in the open. This is the current direction. Priorities shift with what people actually use, so treat it as intent rather than a schedule.

Multi-machine, hub and spoke

The next major piece lets agents on different machines share one mesh. One machine owns the SQLite database and exposes a small HTTP API; the others run a lightweight spoke that polls the hub and dispatches local keystrokes. Bearer-token auth, LAN-bound by default. This is designed and approved, with the build queued.

More client integrations

Beyond the four first-class clients, the plan is one-command support for more MCP-compatible CLIs. The integration pattern is small and repeatable, so contributions move quickly here.

Richer messaging

• Channels and topics: named buses for topic-based collaboration, instead of only role-to-role messages.
• Message search and history: query past messages, not just unread ones.
• Structured payloads: file paths, code snippets, and diffs as first-class message types.
• Priority interrupts: break a recipient's current turn for a genuinely urgent ping.
• Agent templates: pre-built role configs for common workflows.
• Encryption at rest for the local database.

Help shape it

If one of these would help your workflow, or you have built something not listed here, open an issue or send a pull request on GitHub. For how things work today, head back to the documentation home.