Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@rk0429/agentic-relay) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

agentic-relay

agentic-relay is a TypeScript MCP server that launches Claude Code, Codex CLI, and Gemini CLI through a single MCP endpoint. It now exposes both agent execution tools, Phase 2 task management tools, and Phase 3 task-type routing.

Current scope

Phase 1 foundation from docs/requirements.md
Phase 2 task management from docs/requirements.md
Phase 3 task-type routing from docs/requirements.md
relay mcp serve over stdio
Parallel spawn_agents
Backend routing, depth guard, response persistence, and session metadata
Automatic cross-backend handoff when session_id is resumed with a different backend
Task CRUD, status transitions, dependency resolution, review flow, and spawn_agents/agents[].task_id linkage
Task write permissions scoped to the assigned task subtree, while reads remain open
Task warnings for missing acceptance_criteria, with leaf tasks blocked from execution until criteria are defined
task_type-based backend auto-selection and orchestration-only re-delegation

Usage

pnpm install
pnpm build
pnpm relay mcp serve

Responses are stored under .relay/ in the current working directory.

MCP Tools

spawn_agents
create_task
update_task_status
assign_agent
list_tasks
get_task
update_task
delete_task

Task operations are read-open by default. Mutations are limited to the current agent's assigned subtree (plus bootstrap operations on tasks the agent created), and task payloads include warnings when acceptance_criteria is missing. Leaf tasks cannot transition to ready or in_progress until their acceptance_criteria is defined.

spawn_agents links task automation through agents[].task_id. When a given agent entry includes task_id, only that task is auto-transitioned and auto-assigned from the spawned session.

When backend is omitted, spawn_agents resolves it from task_type. The default routing is orchestration/document_writing/code_review -> claude and research/document_review/code_writing -> codex, with fallback to another installed backend if the preferred one is unavailable. Only task_type="orchestration" child agents receive spawn_agents; all other task types are treated as leaf agents.

Use From This Workspace

This workspace is configured to consume the published package via @rk0429/agentic-relay@latest.

Claude Code

Project MCP registration lives in .mcp.json:

{
  "mcpServers": {
    "agentic-relay": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@rk0429/agentic-relay@latest", "mcp", "serve"]
    }
  }
}

Claude project enablement lives in .claude/settings.local.json (symlinked to .agents/settings.local.json) and must include agentic-relay in enabledMcpjsonServers.

Codex CLI

Workspace config lives in .codex/config.toml:

[mcp_servers.agentic-relay]
command = "npx"
args = ["-y", "@rk0429/agentic-relay@latest", "mcp", "serve"]

Gemini CLI

Workspace config lives in .gemini/settings.json:

{
  "mcpServers": {
    "agentic-relay": {
      "command": "npx",
      "args": ["-y", "@rk0429/agentic-relay@latest", "mcp", "serve"]
    }
  }
}

Verify

claude mcp list
codex mcp list
gemini mcp list