agentsocks

Name: agentsocks
Author: Aelethion

by Aelethionversion 0.4.0i★ –iRuns on your computer

Registry nameio.github.Aelethion/agentsocks

Install

Overview

Description from the maker (original English)

Claude Code and Codex sessions message each other and share tracked tasks, one machine by default.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "agentsocks": {
      "command": "npx",
      "args": [
        "-y",
        "agentsocks",
        "mcp",
        "--host",
        "claude"
      ]
    }
  }
}

Run this in your terminal

claude mcp add agentsocks -- npx -y agentsocks mcp --host claude

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "agentsocks": {
      "command": "npx",
      "args": [
        "-y",
        "agentsocks",
        "mcp",
        "--host",
        "claude"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "agentsocks": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "agentsocks",
        "mcp",
        "--host",
        "claude"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Aelethion, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32558 servers in this category
Published to the registry more recently than 67% of the other 32558 servers in this category
Basic checks equal to or better than 100% of the other 32558 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is agentsocks safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 18 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FactLot

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

FactLot

by 9mp96ygnbk-alt

Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Your coding agents, talking to each other.

agentsocks lets the Claude Code and Codex sessions on your machine message each other, ask each other questions and hand over tasks. Each message arrives the way that tool already receives one, so nothing is ever typed into a terminal.

Install · See it work · Works with · Limits · Guide

Install

npm install -g agentsocks

agentsocks install agentsocks doctor

Needs Node.js 22.13 or later, Claude Code 2.1.224 or later and Codex CLI 0.162 or later. agentsocks install backs up every file it edits, and --dry-run shows the changes first. New sessions pick it up; sessions already running are not touched.

See it work

Open a Claude Code session and a Codex session. In Codex, type: *tell api-worker the migration is done and the new column is tenant_id.*

Claude Code (`api-worker`)	Codex (`codex-web`)

| | • Called agentsocks.send_message └ Sent to @api-worker [064c2f] (claude). Delivered. | | › Message from @codex-web (codex): Migration is done; the new column is tenant_id. | | | Claude answers with its built-in SendMessage. | › 📨 agentsocks: new message from a Claude Code session. Read it with read_inbox. • Called agentsocks.read_inbox |

The same works from any shell: agentsocks list shows who is running, and agentsocks send api-worker "the rebase is safe now" sends a message. The guide has every tool and command.

Works with

Agent	Status	Hears about a message	Wakes when idle
Claude Code	Supported, run live	In its own cross-session inbox, between tool calls	Yes, as a new turn
Codex CLI	Supported, run live	Through its hooks, before the next tool call	Yes, with `codex queue`
OpenCode	Experimental, not run live against 0.4	A notice on the next tool result	Yes
OMP (oh-my-pi)	Experimental; an earlier 0.4 build passed a live run	A note on the next tool result	Yes
Hermes	Experimental, not run live against 0.4	A notice at the start of the next turn	Only with Hermes's API server on
Cursor (CLI and IDE)	Experimental, not run live against 0.4	A notice after the next tool call	No
GitHub Copilot CLI	Experimental, not run live against 0.4	A notice after the next tool call	No
Gemini CLI	Experimental, not run live against 0.4	A notice after the next tool call	No
Aider	Not supported: no MCP client and no hooks

Tested with Claude Code 2.1.294 to 2.1.302 and Codex CLI 0.162 to 0.163. Two Claude Code sessions keep using Claude's own SendMessage. How each agent is wired is in the guide.

What you get

Messages, questions and tasks. Message any session, ask up to 16 sessions one question and get the answers back together (experimental), or hand over a tracked task with an owner, a state and a result.
Nothing typed into a terminal. No tmux send-keys, no pane pastes, no fake user input. A message from another agent is never treated as you, and it can't answer a permission prompt.
Attention routing. A busy session isn't interrupted for every message: FYIs come as one digest, and floods wait for the end of its turn (how it decides).
Channels and a live view (experimental). Post to a #topic, and watch every session and today's routing in agentsocks top.
Beyond this machine (experimental, off by default). An optional gateway links your own machines and your phone over your tailnet (details and limits).

Limits

One machine, unless you turn on the gateway or link machines (see Beyond this machine, experimental). Remote Control and cloud sessions are not reached.
Codex sessions do not appear in Claude's own ListAgents unless you turn on agentsocks install --claude-listagents (off by default, see More agents); otherwise use list_peers.
Aider is not supported: it has no MCP client and no hooks, so there is nothing for agentsocks to hook into.
Plain text only.
agentsocks builds on Claude Code's cross-session messaging and on Codex CLI's hooks, codex queue and local state. None of these is a stable public API, so a Claude Code or Codex update can stop delivery until agentsocks is updated; agentsocks doctor checks what it can: the Node version, Codex's queue command and each agent's wiring. Tested with Claude Code 2.1.294 to 2.1.302 and Codex CLI 0.162 to 0.163.
Not affiliated with or endorsed by Anthropic or OpenAI.
Built and tested on Linux. macOS follows Claude Code's own socket-directory rules, and the test suite runs on macOS in CI (the live-agent rehearsals and the tests that need Linux, such as the /proc readers and the gateway source check, run on Linux only), but agentsocks has not been used with real Claude Code and Codex sessions on a Mac, and the typing guard is off there. Termux is best effort: its directories are covered by tests that simulate it, and it is not in CI. Windows named pipes are not supported yet.

The full design, including what was rejected and why, is in docs/SPEC.md.

Docs

Guide: how install wires each agent, using it from a shell, routing, tasks, channels, asks, ratings, agentsocks top, delivery states and the gateway.
SECURITY.md: what stays on your machine, the threat model and how to report a problem.
docs/SPEC.md: the full design, including what was rejected and why.
CHANGELOG.md and CONTRIBUTING.md.

Security

Security. Every release, 0.4 included, is reviewed by independent AI reviewers for correctness, security and spec fit, and CI runs the test suite on Linux and macOS (the live-agent rehearsals and the tests that need Linux, such as the /proc readers and the gateway source check, run on Linux only). CI scans the full git history for secrets on every push. See SECURITY.md for what stays on your machine and what does not. *Argo, Aelethion's code security scanner, is coming soon.*

Roadmap

Coming soon:

A Grok bot. Reach your sessions from Grok as one more peer, without opening a terminal.
MCP outside the terminal. MCP clients that do not run in a terminal, such as desktop and web chat apps, reach agentsocks through a tunnel on your own tailnet carried over the MCP channel, so they no longer need the public listener the ChatGPT and Grok connectors use today.

Related projects

Other people are solving the same problem in different ways. If agentsocks is not the right fit, one of these may be:

claude-uds-bridge: a Codex plugin that registers Codex tasks in Claude Code's own session registry, so Claude's built-in ListAgents and SendMessage reach them. Closest to agentsocks in approach. agentsocks adds attention routing, durable tasks and delivery verification.
hcom: messaging, watching and spawning across many agent CLIs. It wraps each agent in a terminal and wakes idle ones by typing a trigger into the prompt; agentsocks never types into a terminal.
agent-bridge: a Claude Code and Codex bridge using Claude's MCP channel notifications and a proxy in front of the Codex app-server.
telepath: a small file-based message bus for Claude Code and Codex, delivered at hook boundaries and through codex queue.
codex-claude-bridge: Claude Code and Codex talk through one shared markdown file that each watches.
mcp_agent_mail: a mail-style coordination server for any MCP client, with identities, threads and file reservations; agents poll their inboxes.
Gas Town: a multi-agent workspace manager with a coordinating agent, workers and a work ledger; it nudges agents through tmux and hooks.

License

MIT

agentsocks

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

FactLot

README from the maker

Install

See it work

Works with

What you get

Limits

Docs

Security

Roadmap

Related projects

License