Cosmonapse

An agent-to-agent protocol built for harness engineering

13 followers

An agent-to-agent protocol built for harness engineering

13 followers

Visit website

AI Infrastructure Tools

•

LLM Developer Tools

•

AI Workflow Automation

Cosmonapse is an event-driven agent-to-agent protocol modeled on a nervous system. Agents are pure functions no base class, no lifecycle. Orchestration is a role, not a bottleneck: any node can dispatch, any node can react. Harnesses are built from typed signals instead of loops tool calls (incl. MCP), shared memory, human approval, and retries each compose as a node or hook around a stock model call. Same code scales from in-memory tests to NATS/Kafka. MIT. Python + TypeScript SDKs + CLI.

Free

Launch tags:Open Source•Developer Tools•Artificial Intelligence

Launch Team

ReplayAutonomous app testing for teams who ship at AI-speed

Promoted

Maker

📌

Hey Product Hunt 👋 Every multi-agent framework I tried handed me one orchestrator class that had to know every agent, every step, every branch. Fine in the demo then you add a fourth agent or a human-approval step, and that file becomes the bottleneck every change routes through. And the "agent harness" everyone's building now? Usually the same god-object one level down: a while-loop that owns the model call, the tools, the memory, and the approvals. So I built Cosmonapse, an event-driven agent-to-agent protocol where a harness is a set of reactions, not a loop. The mental model is a nervous system: 🧠 Neuron — your agent, a pure (input) -> output function. No base class, no lifecycle. ⚡ Axon — turns output into a protocol-valid Signal. 🌿 Dendrite — receives and reacts. Any node can dispatch; any node can react. 🔗 Synapse — the bus. In-memory for tests → local broker in dev → NATS/Kafka in prod, same code. 💾 Engram — shared memory. Answered or approved once → recalled, not re-asked. Harness concerns decompose into typed signals: tools are TOOL_CALL/TOOL_RESULT (MCP plugs in the same way), human-in-the-loop is a clarification/permission signal any node can answer, and retries/routing/bidding are just nodes reacting to events. Add a capability by adding a node never by editing a loop. And the "orchestrator" is the same primitive as a worker (Cortex = Dendrite), so you run centralized or fully decentralized with zero code change. Apache -2.0 licensed. Python + TypeScript SDKs + cosmo CLI. pip install cosmonapse I'd love your take on two things: does the nervous-system naming help or get in the way? And how are you structuring your agent harness today?

Report

2mo ago