Asqend CLI

External CLI for bootstrapping a local Asqend runner, managing its background service, and exposing the managed MCP server through asqend mcp serve.

Current boundary:

• Asqend is the control plane for schedules, execution targets, workflow state, and review state
• asqend-local is the local machine bridge
• OpenClaw is the local execution engine for openclaw_task
• OpenClaw users install asqend-local; they do not install a separate asqend-mcp package

Install

npm install -g asqend-local

Quickstart

OpenClaw-specific install and template guidance lives in docs/runbooks/runtimes/openclaw-install.md.

1. Install the CLI.

npm install -g asqend-local

The installed command is still asqend.

2. If you are using OpenClaw, use the OpenClaw runtime explicitly.

asqend bootstrap --runtime openclaw

For a lane-specific OpenClaw target such as a dedicated research worker, persist the lane on the target during bootstrap:

asqend bootstrap --runtime openclaw --openclaw-agent-id research

This opens a browser approval flow against https://app.asqend.com by default. Approve the machine in the browser window before returning to the terminal.

3. Attach and repair the local OpenClaw runtime.

asqend doctor --fix

For --runtime openclaw, this release attaches to an existing local OpenClaw runtime. Initialize OpenClaw first, or point the CLI at an existing runtime with OPENCLAW_CONFIG_PATH and optionally OPENCLAW_STATE_DIR.

That repair step writes or repairs the managed mcp.servers.asqend entry in your OpenClaw config, so OpenClaw can use the bundled Asqend MCP server without a separate asqend-mcp install.

4. Install the background service on macOS if you want the runner to start automatically on login.

asqend install

On Linux, the same command installs a user-level systemd service.

For a lane-specific OpenClaw target such as a dedicated research worker, install can still pin the local lane explicitly:

asqend install --yes --openclaw-agent-id research

5. Check current status at any point.

asqend status

If you are not using OpenClaw and only want the generic runner path, use:

asqend bootstrap
asqend doctor
asqend install

First System

The CLI bootstraps the local runner and writes managed MCP configuration. It does not create systems directly by itself.

To create your first operational system after bootstrap:

1. Open your MCP-compatible client, typically Claude Code or Codex.
2. Confirm the managed Asqend MCP server is available through the config written by asqend bootstrap.
3. Start with platform_discover to see available templates and deployed systems.
4. Use systems_template_deploy to create a first CRM, ticketing, or project system.

For OpenClaw scheduled execution, the runtime path is:

1. Asqend creates a run request for an execution target
2. asqend-local claims the run
3. asqend-local invokes local OpenClaw
4. asqend-local reports the result back to Asqend

For most users:

• leave bootstrap on its default runtime of claude_code
• use --runtime codex only when you specifically want Codex-managed MCP config
• use --runtime openclaw only when you already have a local OpenClaw runtime to attach

Platform Support

• bootstrap, status, doctor, drain, and mcp serve work cross-platform on supported Node versions.
• install supports macOS via launchd and Linux via a user-level systemd unit.
• On other platforms, run asqend start under your own supervisor such as tmux, screen, or an equivalent service manager.

Commands

• asqend bootstrap
• asqend start
• asqend install
• asqend status
• asqend drain
• asqend doctor
• asqend mcp serve

Current Scope

• Primary supported install path is npm global install.
• install is macOS-first and currently manages a launchd service.
• Managed MCP setup writes runtime config that points to the asqend binary, not to a separate asqend-mcp install.
• For --runtime openclaw, doctor --fix manages the OpenClaw-owned mcp.servers.asqend registry entry with openclaw mcp set.
• For --runtime openclaw, install persists the saved runtime profile into the managed service and accepts --openclaw-agent-id for lane-specific runners.
• OpenClaw integration does not require OpenClaw source changes or plugins.

Development Verification

From the repo root:

npm --workspace asqend-local run verify
npm --workspace asqend-local run pack:smoke

pack:smoke is the release-blocking clean-room tarball test. It installs the packed artifact into a temp directory and verifies that the CLI and asqend mcp serve run from built package artifacts only.