acp-router

Route plain-language requests to OpenJordy ACP harness or acpx sessions.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jason9693/Open-Jordy --skill acp-router-jason9693
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-router
Source: https://github.com/jason9693/Open-Jordy/tree/main/openjordy/extensions/acpx/skills/acp-router
Command: npx skills add https://github.com/jason9693/Open-Jordy --skill acp-router-jason9693

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route plain-language requests for OpenJordy ACP harness work into the appropriate runtime sessions or direct acpx-driven sessions, ensuring correct routing and lifecycle handling.

Core Features & Use Cases

  • Route user intent to ACP runtime sessions or direct acpx sessions for coding-agent tasks.
  • Enforce preflight checks before creating harness threads.
  • Map user-provided harness names to standard agentIds and manage session contexts.

Quick Start

Route a coding task to the ACP harness session for Codex and start a new thread.

Frequently Asked Questions about acp-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route coding-agent requests to ACP harness sessions?

You can route coding-agent requests by using the acp-router skill to map plain-language intents to the appropriate OpenJordy ACP harness runtime sessions or direct acpx-driven sessions.

What is the difference between ACP runtime sessions and direct acpx sessions?

ACP runtime sessions are managed harness environments with mapped agentIds, while direct acpx sessions bypass the runtime layer. The router evaluates your request to determine the correct flow before thread creation.

Do I need to run preflight checks before creating ACP harness threads?

Yes, preflight checks are enforced before ACP harness thread creation. The router validates your environment and session context to ensure the coding-agent task can be routed and executed safely.

How do I map a harness name to an agentId for coding-agent routing?

The router maps user-provided harness names to standard agentIds automatically. This mapping manages session contexts and lifecycles for common tools within the ACP environment.

Can I route plain-language requests directly to OpenJordy ACP sessions?

Yes, the router accepts plain-language requests and interprets user intent to route tasks to the appropriate OpenJordy ACP harness sessions without requiring specific session identifiers upfront.

What are the limitations of routing coding-agent threads through ACP?

Routing is limited to supported harness names that map to standard agentIds. If a harness name is unrecognized or preflight checks fail, the router will not create the thread or initiate the session.