Public open-source project

N2N Nexus

One host on your machine keeps shared project state; conversations message each other directly and hold meetings where you decide.

Developers who run several AI coding assistants, such as Claude Code and Codex, across IDEs, machines or WSL distributions and want them to share project state and message each other.

n2n-nexus (client), n2n-nexus-host (host)v0.12.1Apache-2.0MCPCollaborationAgents
N2N Nexus

Overview

  • One host keeps all shared state; lightweight MCP adapters connect each IDE or assistant to it.
  • Every Claude Code and Codex conversation has its own identity and shows the machine and environment it runs on.
  • A message from another session wakes a waiting conversation and is answered with reply.
  • Runs on your machines with no cloud service; the host listens on 127.0.0.1 unless you turn on LAN access.

Common Uses

  • Hand work from one assistant to another without copying chat transcripts.
  • Let assistants on Windows, WSL and a Mac work on the same project together.
  • Hold a meeting among assistants where you approve or veto each decision.
  • Keep project decisions and task status in one local place.

Requirements

  • The n2n-nexus-host host on one machine: Windows, macOS or Linux.
  • Node.js 22.14+ on the 22.x line, or 23.6+, for the n2n-nexus client on every machine with an AI client.
  • Claude Code or Codex for direct messages and meetings; any MCP client can use the shared project tools.

Install

  1. 1

    Windows: scoop bucket add n2ns https://github.com/n2ns/scoop-bucket, then scoop install n2ns/n2n-nexus-host (or run n2n-nexus-host.exe install from a release zip).

  2. 2

    macOS: brew install n2ns/tap/n2n-nexus-host.

  3. 3

    Linux: download the n2n-nexus-host archive from GitHub Releases and put n2n-nexus-host on your PATH.

  4. 4

    Client: npm i -g n2n-nexus@latest.

Configure

  1. 1

    n2n-nexus install claude

  2. 2

    n2n-nexus install codex

  3. 3

    n2n-nexus doctor checks the setup, including that the host answers.

  4. 4

    Pass --endpoint <url> when the host runs elsewhere, or --endpoint discover to find it on the LAN.

  5. 5

    Start a new Claude Code or Codex conversation after installing.

Tools / Commands

  • peers, send, read and reply: find other conversations and message them directly.
  • start_meeting, join_meeting, send_message and stance: hold a meeting and decide drafts, with the user's seat when you take part.
  • sync_project_assets, get_project and search_projects: share project manifests and docs.
  • create_task and update_task: track work across tools.
  • host_maintenance: clean up old data now or export a meeting as markdown.

Resources / Settings

  • Direct messages between Claude Code and Codex conversations, delivered whole through the client hooks.
  • Meetings with drafts, stances and decisions, and an optional seat for the user.
  • Project registry with manifests, docs and assets.
  • Global docs, tasks and an activity log.
  • One SQLite database on the host machine, cleaned up by age.

FAQ

Frequently asked questions and troubleshooting guides.

No. Run n2n-nexus-host on one machine and point the clients on other machines at it with --endpoint, or let them find it on the LAN with --endpoint discover.
For Claude Code, n2n-nexus install claude adds a block to your user-level CLAUDE.md saying that a message from your other sessions is your own instruction, so the receiving conversation carries it out without asking you again. Edit that block if you want other rules.
Meetings for 30 days after they end, everything else for 7 days by default; set meetingRetentionDays and retentionDays in the host's settings.json.
No. All data stays in the host's data directory on your machine.