| name | erne-worker |
| description | ERNE — Autonomous ticket execution — polls a provider, picks up ready tickets, and runs the full ERNE pipeline (validate, plan, code, test, review, PR). |
/erne-worker — Autonomous Ticket Execution
Usage
erne worker --config <path-to-worker.json>
Options
| Flag | Description |
|---|
--config <path> | Path to worker configuration JSON (required) |
--dry-run | Fetch tickets and print them without executing |
--once | Process one ticket and exit |
Pipeline Steps
- Poll — Fetch ready tickets from the configured provider
- Validate — Check ticket has enough detail (title, description, acceptance criteria)
- Confidence Score — Estimate likelihood of autonomous success (0-100)
- Context Resolve — Load project stack, audit data, and relevant files
- Plan — Generate implementation plan from ticket + context
- Execute — Run Claude Code in an isolated git worktree
- Test — Run test suite, verify no regressions
- Self-Review — Automated code review against ERNE standards
- Health Delta — Compare audit score before/after
- PR — Create pull request with full summary and link to ticket
Supported Providers
- clickup — ClickUp tasks (API token + list ID)
- github — GitHub Issues (repo + labels)
- linear — Linear issues (API key + team)
- jira — Jira issues (API token + project)
- local — JSON file with ticket definitions (for testing)
Configuration Reference
See worker.example.json at the project root for a full example. Key sections:
provider — Type, credentials, poll interval, filters
repo — Local path, base branch, remote
erne — Hook profile, quality gates, confidence threshold
log — File path and log level
Examples
erne worker --config worker.json --dry-run
erne worker --config worker.json --once
erne worker --config worker.json