hiw3c 日报精选
Hacker News Top 网页快照

展示HN:脉冲星 – 跨线束代理间通信与消息传递

原文标题 · Show HN: Pulsar – cross-harness agent to agent communication and messaging

HN ⭐ 8 · 0 评论

来源:Hacker News Top · github.com

正文为英文,可一键机器翻译(仅首次需要等待)

Latest commit

History

Folders and files

Repository files navigation

pulsar

Your AI agents can talk to each other now. In any harness.

pulsar is an MCP server that puts every AI coding agent on your machine on one bus: Claude Code, Codex, OpenCode, pi, omp, Cursor, Gemini CLI. Agents can see who else is running, tag themselves by what they work on, and message one agent, a group, or all of them. A message can wake an agent that is sitting idle.

npx pulsar setup

That's the whole install. Restart your agents.

Coming soon: agents talking across multiple machines, and remote control of your agents over the bus, using Tailscale .

What it does

> list agents on apparish 3 agents (project=apparish): - apparish-auth · [claude] · branch=main · busy · push · tags=workstream:auth - codex@apparish · [codex] · branch=feat/billing · idle · push - omp@apparish · [omp] · branch=main · idle · push > tell everyone on apparish that main is frozen until the release is tagged Sent m_mwk3jlo0 to 3 agents: - apparish-auth: sent via claude-socket - codex@apparish: sent via codex-queue - omp@apparish: delivered via extension

One list for the whole machine. Every live agent, whatever harness it runs in, including Claude Code and OpenCode sessions that never loaded pulsar. Claude sessions keep the names Claude gives them; others are harness@project .

Tags and activity. Agents get harness , model , project , branch (the branch they push to, even from a randomly named worktree), worktree and pr (the PR they work on, found offline from local git refs and their session log) on their own. They add their own, like role:reviewer or issue:1378 , and an activity line such as "reviewing PR #1402".

Send to anyone. Address a name, a selector such as project=apparish , model=fable or pr=1402 role=reviewer , text anywhere ( ~1378 ), or * for every agent on the machine. "Message your reviewer" is one lookup.

Push, not polling. Messages wake an idle agent, and urgent ones land mid-turn where the harness supports it (see delivery ).

Request and reply. reply keeps threads, ask blocks until the answer comes, and wait replaces sleep loops (wait for a message, a reply, or another agent going idle).

Safe by default. Messages are marked as coming from a peer, never your user, and can't approve anything. Each agent can accept, hold or refuse messages. There are rate limits, and no telemetry.

Install

npx pulsar setup

Setup finds your agents, shows exactly which files it will change, and asks once. It backs up every file it touches and copies pulsar to a local folder that each agent runs, so no session start waits on npm.

Setup installs to ~/.local/share/pulsar/<version> and points every agent at the current link, so npx pulsar@latest setup upgrades in place.

No Node? curl -fsSL https://raw.githubusercontent.com/yocontra/pulsar/main/install.sh | bash installs a private Node and runs the same setup.

Prefer your harness's own package manager? These install the MCP server and the skill (push delivery into pi and omp needs the npm package, which carries their extension):

pulsar setup also sets Claude's crossSessionInbound and Codex's tool approval, which plugin installs cannot.

{ "command" : " npx " , "args" : [ " -y " , " pulsar " , " mcp " ] }

Without a push path for that client, messages wait in the agent's inbox, and every pulsar tool result says when unread messages are waiting.

Tools

pulsar also installs a short skill that teaches agents when to use these, and the MCP server sends the same guidance as instructions.

CLI

pulsar ls [selector] # who's online pulsar send ' * ' " main is frozen for the release " pulsar send project=apparish --expect-reply " who owns the auth migration? " pulsar reply m_123 " on it " # answer a message in its thread pulsar inbox # replies sent to you ("operator") pulsar tail # live feed of joins, leaves and messages pulsar doctor # check the daemon and every harness

How delivery works

One small daemon per machine (started on demand, stops when idle) keeps the registry and a SQLite message log at ~/.local/state/pulsar . Each agent's MCP server is a thin client of the daemon over a user-only Unix socket. The daemon pushes each message through the harness's own way in:

The daemon also scans for live Claude Code and OpenCode sessions that never loaded pulsar, so they show up and can receive messages too. Details and edge cases are in docs/adapters.md .

Compared to Claude Code's built-in messaging

Safety

The socket is in a 0700 folder and is reachable only by your user. That is the trust boundary: processes running as you are trusted, as they are with your files. The daemon stamps each sender from its connection, so a message can't claim to come from someone else. pulsar send from inside an agent speaks as that agent, and no agent can use the name operator .

Delivered text says it comes from a peer agent, not your user, and that it can't grant permissions. Claude's own guardrails still apply on top.

pulsar never claims a permission mode on Claude's behalf. Setup asks you to allow pulsar's messages with Claude's documented crossSessionInbound setting instead.

Limits: 64 KB per message, 60 sends a minute, 6 broadcasts a minute per agent, and 50 unread per inbox.

No telemetry. The only network call is pulsar doctor 's npm version check. PR detection is offline: it reads local git refs and the agents' own session logs.

See SECURITY.md to report a vulnerability.

Environment

Development

bun install bun run check # typecheck + lint + tests bun run build # bundles dist/cli.js and dist/extension.js node src/cli.ts ls # runs from source, no build step

License

About

MCP server that lets AI coding agents in any harness find and message each other: one list, tags, multicast, * bus.

Topics

Resources

Contributing

Security policy

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages