21c35ff2c3
Passthrough is verified and pinned by regression tests that assert on what cortex forwarded upstream, so tireless can rely on it. The design no longer carries it as an open dependency. Two residual behaviours replace it, neither a passthrough defect: Multiple system messages are forwarded unmerged and in order, last one wins. OpenCode sends its own preamble alongside an agent's configured prompt, so the stage 5 question becomes "did implement.oc.md arrive last", not "did it arrive". That failure is silent -- an agent that reads as a generic coding assistant and ignores Out of scope -- and would present as a prompt-quality problem rather than a plumbing one, so stage 5 now asserts on the upstream request. helexa#223: /no_think is ignored on /v1/responses, where a thinking model can spend its whole output budget on reasoning and return "" with status incomplete. Added RunOutcome::OutputBudgetExhausted so that is retryable but blameless -- a mis-sized ceiling must not trip a circuit breaker on a lane with nothing wrong with it. Config pins the chat/completions surface. The qwen3_next gap is recorded as a gap, not a hole: the system slot is not arch-branched, so there is no family-specific path to fail. Fleet now offers Qwen3-Coder-Next, a better fit for executing a written spec, but cold and feasible only on beast where the pinned 27B lives. Recorded as an operator decision per generic.md §14 rather than taken here. Config also notes why tireless pins a model name and never a helexa/* capability alias. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DHhHtohxcdk1PL3tfnYJdH
tireless
Watches labelled issues on Gitea (and GitHub, for legacy repos), claims them, and either decomposes them into an epic with child issues or implements them and opens a pull request. A human reviews everything; nothing merges itself.
Two coding agents do the work, each spawned as the vendor's own binary:
- Claude Code — planning, and implementation of issues that need interpretation. Uses the operator's Claude subscription by default, or pay-as-you-go if an API key is supplied.
- OpenCode — implementation of issues that a tireless plan already specified, against the self-hosted helexa fleet. Never Anthropic; enforced at startup.
The rule of thumb: Claude Code gets judgement, OpenCode gets specification.
Full design, constraints and the staged implementation plan:
doc/plan/design.md.
Status
Stage 0 (foundations) is scaffolded. Ingestion, claiming and the agent lanes are not built yet — see §7 of the design document for what lands when.
Build
cargo test --workspace
cargo clippy --all-targets --all-features -- -D warnings
cargo fmt --all
cd dashboard && npm ci && npm run build
Run locally
cargo run -p tireless-api -- --config ./config.toml
cargo run -p tireless-worker -- --config ./config.toml poll
cargo run -p tireless-worker -- --config ./config.toml run
cd dashboard && npm run dev # proxies /v1 to 127.0.0.1:23296
tireless preflight verifies configuration and credentials without starting a
service: it reports which billing mode a Claude Code run would use and asserts
the OpenCode lane is not pointed at Anthropic.
Deploy
CI-driven via Gitea Actions on merge to main
(architecture/deployment-gitea-actions.md). One-time host provisioning —
including the interactive Claude Code login and the Gitea bot account — is
script/infra-setup.sh.
| Host | bob.hanzalova.internal |
| API port | 23296 (registered in architecture/port-allocations.md) |
| Dashboard | https://tireless.internal (mesh only) |
| Database | magrathea.kosherinata.internal:5432, mTLS |
Conventions
Follows lair/architecture;
generic.md is the baseline. Two deliberate deviations:
tireless-agentcrate beyond the standard entities/core/data split. Process orchestration is not data access, and it is shared by the runner and the CLI. (§1)MemoryDenyWriteExecute=falseontireless-runner. Both agents are Node programs and V8's JIT needs write-then-execute pages. The API and poller keep the setting. (§8)