01 / Route
Pull eligible Linear work
Project routing rules pick the right workspace, issue, and execution context before an agent starts touching code.
Agentic Development Hub & Daemon
devos.ing
Talk is cheap, show me your agent system.
Turn Linear issues into an agent-driven engineering workflow: plan, implement, review, test, and loop with operators still in control.
run console
Current issue
Refactor billing events without losing audit history
Linear
ENG-123
Plan
strategy
Implement
worktree
Review
PASS
Daemon trace
01 route project: core-platform
02 attach skill: piv-implement
03 create draft PR: codex/eng-123
04 RESULT: PASS
Review contract
RESULT: PASS
SUMMARY: ready for merge
BUGS_JSON: []
How this works
A staged loop for real engineering work.
02 / Plan
Turn intent into a run plan
The planning stage builds a scoped implementation strategy from issue context, project config, and selected skills.
03 / Implement
Ship changes into PR context
The implementation agent works in the project workspace, updates code, and keeps pull request context synchronized.
04 / Verify
Review, test, and loop
Structured review output feeds failures back into implementation until the run is done or clearly blocked.
Features
Built for repeatable agent operations.
Auditable project routing
Route issues across many repositories without hard-coding behavior to a single workspace.
Linear-native status sync
Comments, labels, status transitions, and issue state stay aligned with each workflow boundary.
PR-aware implementation
Agents preserve pull request context and can update draft PRs as review feedback arrives.
Stable review contract
Review parsing stays machine-readable with RESULT, SUMMARY, and BUGS_JSON outputs.
Polling and scheduled sweeps
Run one issue, poll for new work, or let server-owned cron automation sweep eligible queues.
Operator control
Humans can inspect stage, outcome, and risk while devos.ing handles the repetitive loop.
FAQ
The useful answers first.
What is devos.ing?+
devos.ing is ADHD: Agentic Development Hub & Daemon. It turns Linear issues into staged agent workflows for planning, implementation, review, and testing.
Does it replace engineers?+
No. It removes repetitive coordination and execution loops while keeping operators in control of routing, review, and outcomes.
Which tools does it work with?+
The current workflow centers on Linear, GitHub pull requests, CLI execution, server cron jobs, and agent adapters for Codex and Claude Code.
Can it run unattended?+
Yes. It can run one scoped issue, poll locally, or use scheduled server-owned automation sweeps across configured projects.
How does review stay reliable?+
Review output follows a stable contract: RESULT, SUMMARY, and BUGS_JSON. Failures are fed back into implementation.
Where is run state stored?+
Run state is owned by the workflow layer inside the configured workspace, with safe recovery paths for partial runs.