A LOCAL MCP SERVER / v0.0.1

Your agents.One hive.

Codex and Claude Code, working through one local endpoint. Delegate a task. Keep the context. Call the shots.

Put your hive to work Read the setup guide

Runs on your machine. Uses your existing agent logins.

ILLUSTRATED WORKFLOW

spawn → send → wait127.0.0.1:46100

12 MCP TOOLSPERSISTENT SESSIONSNODE.JS 24+MIT LICENSE ↗

01 / THE WORKFLOW

A task ends.
The context stays.

Your calling agent decides what happens next.
Vespiquen handles the connection and the session.

01 / DELEGATE

Give it a task.

Brief Codex or Claude Code. Get the answer, reported file changes, and a transcript.

spawnwait

02 / CONTINUE

Keep the thread.

Follow up in the same session. Steer a running turn. Fork the conversation when you need another path.

sendsteerfork

03 / STAY IN CONTROL

See it through.

Answer a permission request. Inspect the event log. Stop a turn or close the session.

respondtailstopclose

02 / ON YOUR MACHINE

One install.
Your own logins.

You need Node.js 24+ and an authenticated Claude Code or Codex CLI. The ACP adapters are downloaded on first use.

vespiquen on npm

01 / INSTALL FROM NPM

npm install --global vespiquen

02 / START IN A SEPARATE TERMINAL

vespiquen start

Keep it running while your agent works.

Then connect your agent using the setup prompt below.

03 / CONNECT THE HIVE

Let your agent
take it from here.

Copy the prompt into Claude Code or your coding agent. The guide covers installation, MCP registration, and a first task.

Published on npm · v0.0.1 · MIT

GIVE THIS TO YOUR AGENT

Read https://vespiquen.irving.dev/llms.txt and help me install Vespiquen, connect it to Claude Code, and verify a first subagent task. Reuse any existing installation and running server.

Built for my own workflow.
Shared for yours.

Irving Dinh

Your agents.One hive .

A task ends.The context stays.