@godriftless/driftless-orchestrator
v0.4.0
Published
Public Driftless orchestrator — run coding agents against your own repos, driven by the Driftless task board.
Downloads
207
Readme
driftless-orchestrator
Public NPM package that lets you run coding agents (OMP or Claude Code) against your own repos, driving work from the Driftless task board. The orchestrator runs on your local computer — Driftless hosts zero compute. You bring your own inference (BYOK).
Install
npm install -g @godriftless/driftless-orchestratorQuick start
driftless runOn first launch, if config is missing or incomplete, the setup wizard runs automatically. It prompts for:
- Driftless API key — from your agent settings page on app.godriftless.ai (this is the only credential you need)
- Coding agent runtime — OMP or Claude Code
If OMP is selected, the wizard writes the Driftless MCP config and copies the
driftless-task-execution-protocol skill file into ~/.omp/agent/. Then run
omp separately to log in to your model provider and select a default model —
the orchestrator keeps polling, no restart needed.
Repo and workspace paths are configured at the agent settings level in Driftless (not locally). The orchestrator reads them from the Driftless API at dispatch time.
Commands
| Command | Description |
| --- | --- |
| driftless run | Validate config (run setup wizard if missing), then enter the poll loop. |
| driftless status | Show config and last poll timestamp. |
| driftless tasks | List currently assigned tasks. |
run is the only command you need. The setup wizard is embedded — no separate
setup command.
How it works
The orchestrator is a persistent polling binary:
- Polls the Driftless API for assigned tasks every 5 minutes (configurable via
POLL_INTERVAL_MS). - Picks the highest-priority assigned task (skipping blocked-by dependencies).
- Dispatches your configured coding agent with the task directive.
- Captures agent stdout, filters OMP JSON events for readable console output, streams live log lines to the Driftless UI via Socket.IO.
- Parses OMP phase progress and persists it to the Driftless API in real-time.
- Extracts cost data from OMP output and reports it as BYOK (actual cost on the task for analytics, billable cost to Driftless is zero).
- Pushes the captured log to S3 via a presigned URL from the Driftless API (permanent audit trail, viewable in the task History tab).
- Continues polling for new assigned work.
Configuration
Config lives at ~/.driftless-orchestrator.env with file permissions 0600.
Server endpoint is hardcoded to https://app.godriftless.ai — not configurable.
Agent ID and org ID are resolved automatically from the API key via the
agents/me endpoint; you only provide the API key.
Security
- The client holds zero infrastructure credentials — only your Driftless API key plus local git credentials.
- No DB connection strings, no Redis strings, no AWS credentials on the client.
- S3 uploads use presigned URLs from the Driftless API.
- Coding agent runs locally as your own process; Driftless never touches inference.
Requirements
- Node.js 22+
- A coding agent installed locally (OMP or Claude Code)
- A Driftless account with an agent and API key (app.godriftless.ai)
