NCF Agent Interconnect
“NCF Agent Interconnect” connects AI assistants on demand for a shared task.
Supported applications: Codex Desktop, Claude Code, Cursor, OpenCode and AionUi with Cursor Agent.
For example, you want to add search to a message history. Open two Codex chats on one computer. In the first: “Connect as agent Charlie. Define the requirements for searching message history.” In the second: “Connect as agent Maya. Implement search using agent Charlie’s requirements. Clarify open questions with Charlie.”
Charlie defines what the search should do; Maya uses those requirements to build it. The agents address one another by name and exchange the messages and files the work requires. You set priorities and discuss the result in those same chats. Each new agent joins through a chat request, without separate setup. Later, chats in other supported programs and paired computers on a local network can join the work.
Official website: no-colours-fabric.github.io/ncf-agent-interconnect.
LLM-optimized documentation: llms.txt.

Settings and monitoring: agents and connection status.
How to start
- Install NCF Agent Interconnect and configure your AI application using the setup guide.
- Open separate chats for the shared task. Choose a name and a role for each assistant; connect each one in its own chat.
- Name the collaborator and the result their work depends on, as in the Charlie and Maya example above. Let the assistants resolve questions directly or appoint an agent to coordinate.
- Keep discussing requirements, priorities and results in those AI chats as work progresses.
Confirmation that a message was received does not mean the task is complete.
Work in one application or connect different tools and computers on your local network. See the user guide for practical workflows.
NCF Agent Interconnect settings and monitoring
Discuss the task and its result in those same Codex chats. Charlie and Maya use “NCF Agent Interconnect” to coordinate requirements and implementation and share the materials they need. The app window provides connection settings, delivery status and message history for diagnostics and administration.
The Agents page shows local agents and known agents on paired computers. You can view a local agent's messages and files, or delete one or all local agents along with their history.
Features
- Agents and history: user-chosen names, exact chat bindings, local message history and verified attachments. Moving an occupied name to another chat requires your explicit choice to preserve or delete its local MCP history.
- Connections: local exchange and separately paired remote computers. Names on different computers can be identical, so a remote destination includes its computer.
- Client setup: a dialog for each supported application. The selected client configuration changes only when you click Apply. Saved settings, a live client connection and delivery to a chat are separate states.
- Installed applications: read-only discovery for Cursor, OpenCode, Codex, AionUi (with Cursor Agent support) and Claude, with local application icons and one-time setup offers. Refresh or choose an installation manually; discovery does not prove setup or chat readiness.
- Delivery information: a sent message may be queued, accepted by a remote node or received by the agent. These states do not report whether the agent finished the work.
- Preferences and controls: fifteen interface languages, light and dark themes, remote pairing, history and data removal. Agent names, messages and filenames retain their original language.

Settings and monitoring: message history and files.
Download and client support
Download the latest installers for Apple Silicon Mac (arm64 DMG), Intel Mac (x64 DMG), Windows x64 (EXE) or Linux x86_64 (AppImage). macOS requires version 13 or later. Installers include the runtime; Node.js and source files are not needed. Intel packages are built on macOS but have not been run on Intel hardware. Installation details cover verification, updates and removal.
| AI application | Exchange and history | Delivery to the bound chat |
|---|---|---|
| OpenCode with the bundled v1 plugin | Yes | Automatic; busy chats wait for an idle event |
| Codex Desktop | Yes | Experimental, version dependent |
| Cursor | Yes | Bundled plugin delivers to open exact chats; see setup limits |
| AionUi with Cursor Agent | Yes | Exact-chat delivery after owner authorization and bridge setup |
| Claude Code with compatible mods | Yes | Full exact-chat Incoming; see native version and permission limits |
| Other compatible MCP clients | Through MCP | Requires a client adapter |
Cursor setup installs its included reactive plugin after your Apply action; the verified Mac scope and platform limits are in application setup. Cursor Agent inside AionUi can use the same MCP entry in the selected Cursor configuration file, but also needs owner authorization and a live bridge. The OpenCode plugin targets its v1 plugin contract. See setup for what each client requires.
Claude Code uses bundled main and gate plugins enabled by Apply. The owner saves exact connect/send allow rules through Claude's native permissions UI for the tested auto-mode setup; Apply adds only the read rule. Full native Incoming carries sender, body, attachment links and the reply route directly to the model and visible chat. Linux Desktop and terminal evidence is frontend-specific; live Claude behavior on macOS and Windows is unverified. See Claude Code setup and limits.
Documentation
Use the product
- Work with agents from your chats: the main task workflow, coordination, retrospectives, progress and common problems.
- Learn NCF Agent Interconnect with your own AI: browse 13 prepared prompts for a detailed guide in your language, or ask a focused question for a direct answer.
- Set up NCF Agent Interconnect: installation, client configuration, optional computer pairing and a first exchange.
- NCF Agent Interconnect settings and monitoring, installation and updates, application-specific setup, AionUi with Cursor Agent setup and privacy and storage: user reference.
Develop and verify the product
- Developer documentation: source setup and links to architecture, protocol, adapter, verification and release material.
- Adapter development manifest: required behavior, acceptance evidence and conditional integration techniques for independent adapter developers.
- Contributing, changelog and security reports.
For a bug report, include the app version, platform, client and steps to reproduce. Exclude credentials and private chats. See Security for vulnerability reports.
License
BSD-3-Clause. Dependencies retain their own licenses; see third-party notices.