JSPM

  • Created
  • Published
  • Downloads 10134
  • Score
    100M100P100Q132926F
  • License MIT

CLI for AgentXchain — multi-agent coordination in your IDE

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 (agentxchain) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    agentxchain

    CLI for multi-agent coordination in your IDE. Define a team of AI agents, launch them in Cursor / Claude Code / VS Code, and let them coordinate via a shared protocol.

    Install

    npm install -g agentxchain

    Or run without installing:

    npx agentxchain init

    Quick start

    # 1. Initialize a project (creates agentxchain.json, lock.json, state.json, log.md)
    agentxchain init
    
    # 2. Check status
    agentxchain status
    
    # 3. Launch agents in your IDE
    agentxchain start --ide cursor
    
    # 4. Stop agents
    agentxchain stop

    Commands

    agentxchain init

    Interactive setup. Creates all protocol files in the current directory.

    • -y, --yes — skip prompts, use 4 default agents (pm, dev, qa, ux)

    agentxchain status

    Show current lock holder, phase, turn number, and all agents.

    • -j, --json — output as JSON

    agentxchain start

    Launch agents in your IDE.

    • --ide <ide> — target IDE: cursor, claude-code, vscode (default: cursor)
    • --agent <id> — launch only one specific agent
    • --dry-run — preview what would be launched

    For Cursor Cloud Agents, set CURSOR_API_KEY in your environment. Without it, the CLI prints seed prompts you can paste manually.

    agentxchain stop

    Stop all running agent sessions. Reads .agentxchain-session.json to find active agents.

    How it works

    AgentXchain uses a claim-based protocol:

    1. Agents are defined in agentxchain.json (name, mandate, rules)
    2. A lock.json file tracks who holds the lock
    3. When the lock is free, any agent can claim it
    4. The agent does its work, logs a message, and releases the lock
    5. Another agent claims. The cycle continues.

    No fixed turn order. Agents self-organize. See PROTOCOL-v3.md for the full spec.

    License

    MIT