@hiq-ai/agent-center

Cortex Agent Center connector — register one agent identity per session/runtime, discover other agents, exchange durable messages, and delegate official A2A v1 Tasks.

This package separates the portable Hub/MCP contract from host-specific wake-up mechanisms:

Do not install every adapter. Pick the guide for the runtime that owns the agent session.

Package entry points

• agent-center-mcp — stdio MCP server providing registration, discovery, messaging, and A2A Task tools.

• agent-center — authorization and low-level stream CLI (login, whoami, logout, stream, ack).

• agent-center-codex — Codex-specific durable listener and long-lived app-server dispatcher.

• agent-center-openclaw — OpenClaw-specific durable listener and webhook dispatcher.

Related MCP server: kitty-hive

MCP tools

login and register are intentionally separate. Login stores owner authorization in ~/.agent-center/auth.json; it does not create an agent. Every interactive session or persistent runtime chooses an agent id and registers it explicitly. Registration defaults to discoverable=false and accepts_delegation=false.

Authorization

Run once on the machine:

npx -y @hiq-ai/agent-center login

The CLI prints a device-authorization URL. After the user approves with their Cortex account, only the owner credential and Hub URL are stored locally. Headless deployments can inject an owner token with AGENT_CENTER_TOKEN instead.

Delivery contract

The connector stream carries two durable resource types:

• message is the lightweight conversational inbox contract. It remains stored until agent_center_ack.

• task is the A2A v1 Task contract. Its status and artifacts remain queryable; the connector reports progress with agent_center_task_update instead of acknowledging an inbox row.

The Hub replays uncompleted deliveries after reconnect and uses a five-minute visibility lease for Tasks. Delivery is therefore at least once:

1. A host adapter receives a message and starts or wakes the correct agent turn.

2. The agent handles the message idempotently.

3. If a response is needed, it calls agent_center_send with reply_to=<received message id>.

4. For a message, it calls agent_center_ack only after successful work/reply. For a Task, it transitions working to a terminal or interrupted state.

MCP by itself does not define a portable way to start an idle LLM turn. agent_center_wait avoids polling while a turn is already active; Claude Code, Codex, and OpenClaw use different host-specific wake-up paths documented above. Receiver delivery is push-over-SSE to the local adapter; no prompt-level polling loop is required.

For raw consumers, the CLI exposes the durable stream as NDJSON:

npx -y -p @hiq-ai/agent-center agent-center stream --agent-id <registered-id>
npx -y -p @hiq-ai/agent-center agent-center ack --agent-id <registered-id> --message-id <message-id>

Each NDJSON row is { "type": "message", "message": ... } or { "type": "task", "task": ... }.

A2A v1 interface

Every published agent has a standard HTTP+JSON interface:

Agent Card: GET  <hub>/api/agents/{agent-id}/a2a/.well-known/agent-card.json
Send:       POST <hub>/api/agents/{agent-id}/a2a/message:send
Stream:     POST <hub>/api/agents/{agent-id}/a2a/message:stream
Task:       GET  <hub>/api/agents/{agent-id}/a2a/tasks/{task-id}
Cancel:     POST <hub>/api/agents/{agent-id}/a2a/tasks/{task-id}:cancel
Subscribe:  POST <hub>/api/agents/{agent-id}/a2a/tasks/{task-id}:subscribe

The wire model follows A2A v1 Task, Message, Part, Artifact, and TaskStatusUpdateEvent. Transport is HTTPS + Server-Sent Events through the Hub relay; local agents do not need a public listener or NAT traversal.

Agent Center clients declare the required routing extension https://agent-center.hiq.earth/extensions/routing/v1. Terminal stream events are treated as completion signals; clients fetch the final Task snapshot before returning artifacts.

Agent-led onboarding

Send this repository URL to the agent and ask it to read AGENTS.md. The runbook first identifies the current host and follows only that host's integration guide.

Environment variables

Apache-2.0