Current surface version is recorded in VERSION.

The npm package is @sonim1/preqstation, and the installed command is preqstation. The OpenClaw plugin id is preqstation-dispatcher.

What this repo owns

This repository is the durable public PREQ CLI and dispatcher surface for PreqStation. It prepares an operator host, configures request entrypoints, maps local projects, runs health checks, and can launch Claude Code, Codex, or Gemini directly or through integrations such as OpenClaw and Hermes.

• bin/preqstation.mjs exposes the platform-neutral CLI
• src/core/ owns project mapping, git worktree preparation, instruction rendering, and detached engine launch
• src/adapters/openclaw/ owns the OpenClaw before_dispatch hook and /preqstation
• src/adapters/hermes/ owns optional Hermes payload normalization for deferred webhook experiments

OpenClaw still loads this package through openclaw.plugin.json and root index.mjs. Worker lifecycle actions now run through the preqstation CLI rendered into .preqstation-instructions.txt; preqstation-skill is legacy optional worker support that status, doctor, update, and uninstall can inspect or clean up.

What It Does

The dispatcher receives PREQ intent, resolves a local project checkout on the dispatcher host, creates or reuses an isolated git worktree, writes .preqstation-instructions.txt, and launches the selected engine as a detached process, including detached Codex runs. This is intentionally not the old PTY/background session model: it does not rely on OpenClaw background:true exec or process action:poll / process action:log for the dispatched coding run.

Supported engines:

• claude-code
• codex
• gemini-cli

Hermes is not an engine. Hermes can be a Telegram host that wakes this dispatcher.

Usage

Quick Start

npx -y @sonim1/preqstation@latest install
npx -y @sonim1/preqstation@latest status

preqstation install is the default setup path. It opens an interactive wizard for request entrypoints, agent runtimes, CLI server URL config, and project setup. Native PREQ runtime MCP registration is now a legacy opt-in via preqstation install --with-mcp. See INSTALLATION.md for detailed install, update, uninstall, project setup, and local development flows.

Command Reference

| Command | Description | | --- | --- | | preqstation install | Interactive setup for entrypoints, agent runtimes, CLI config, and project mappings. | | preqstation install --with-mcp | Legacy opt-in for native PREQ runtime MCP registration. | | preqstation status | Read-only installed-state summary for entrypoints, runtimes, CLI auth, legacy MCP, and project mappings. | | preqstation doctor | Read-only health check for dispatcher configuration and runtime availability. | | preqstation auth login | Store the PREQSTATION server URL and create the shared OAuth cache. | | preqstation auth status | Read-only CLI auth readiness check, including the inspected home and OAuth path. | | preqstation task get PROJ-123 | Read task lifecycle data through the CLI JSON contract. | | preqstation comment reply --comment-id ID --body-file reply.md | Reply to task comments without native MCP tool calls. | | preqstation project settings --project PROJ | Read deployment/project settings through the CLI JSON contract. | | preqstation setup auto | Discover local projects and save shared PREQ project mappings. | | preqstation mcp disable codex | Remove only a legacy PREQ MCP registration for a runtime. | | preqstation run | Dispatch a PREQ task or project objective directly from the CLI. | | preqstation uninstall | Remove installed entrypoints, legacy worker support, legacy MCP, or project mappings. |

Documentation

• Installation and CLI Usage — install/update/uninstall, project setup, direct dispatch, and extended command reference
• Configuration — dispatcher host env vars and local project mapping file shape
• OpenClaw Adapter — before_dispatch flow and /preqstation path
• Hermes Telegram Host — Telegram-hosted dispatcher flow
• Command Shape — supported trigger styles and parsed fields
• Detached Runtime — process artifacts, launch model, and limitations
• Publishing — npm release workflow