Start a task in your terminal and walk away. AFK verifies its own work, texts you when it’s done, and leaves a receipt of every step. Unsure? It stops and asks.
You kick off a task and check back every few minutes. “Autonomous” that needs watching isn’t.
The agent says “done” but you still have to verify it actually worked.
Watching every step isn’t trust, it’s supervision. AFK is built for the gap between “go” and “done.”
Built around the ways agents actually break.
I built this because finished kept not meaning correct: the agent's own check approved the work, but the next stage expected that approval in a slightly different format; good work, rejected three times, nothing crashed. That's what real agent failure looks like.
Griffin Long, creator of Agent AFK
Fake done
Claims completion without verification: confident, unchecked, sometimes just wrong.
Context rot
Long runs decay into unreadable soup. The longer it works, the less anyone can follow.
Babysitting tax
You still supervise every few minutes. “Autonomous” that needs watching isn’t.
Familiar surface. Deeper machinery.
01Subagent orchestration
Most agents can spawn subagents but rarely do. AFK makes them the default. The agent you talk to in-session is the orchestrator, tasked with delegating work to subagents and coordinating the final result.
02Verification workflows
A second adversarial agent re-derives claims before they reach your diff: finished has to prove it is correct.
03Remote supervision
Leave the desk. Your phone buzzes when the run finishes or stalls.
Composable orchestration primitives
Slash skills, not single prompts.
One command, a full parallel pipeline: each skill fans out subagents, gathers results, and re-checks. That's the orchestration you'd otherwise ask for every time. These five see the most use; /forge makes more.
afk ›/review 642
parallel reviewers · one diff
✓correctnesslogic holds
!testserror path uncovered
✓securityinputs sanitized
⚠︎ChangesAdd a test for the error path·2 reviewers clean
A demonstration of the /review skill. Reviewing pull request 642: three reviewers run in parallel over one diff. Correctness (logic holds) and security (inputs sanitized) pass; the tests reviewer flags an uncovered error path. The findings converge into a single merge recommendation: request changes to add a test for the error path, with two reviewers clean.
/mint
End-to-end feature pipeline: spec → research → plan → parallelize → build → verify → heal → ship.
Ship-ready in one pass; pauses for approval.
/diagnose
Parallel hypotheses for bugs and failing tests.
Each validated in an isolated git worktree.
/shadow-verify
Adversarial re-derivation of sub-agent claims before you act.
Re-checked before the build pipeline.
/review
Parallel reviewers across a diff or PR: security, correctness, api-compat, tests, perf.
Synthesized by severity into a merge recommendation.
/ship
Release pipeline for finished local work: pre-flight, tests, commit, push, PR.
Three attach surfaces (the CLI REPL, the background daemon, and the Telegram bridge) all route into a single isolated root directory, ~/.afk/, which holds config, plugins, plans, skills, session traces, and memory.
◆
The model isn’t the product. The loop is.
Agent AFK operating contract, published in the repo
07pricing
Pricing
Free and open source. Pay for ongoing expertise, not features.
The runtime is Apache-2.0 and free: every feature, no unlocks. Paid plans are monthly support from the maintainer, not feature gates.
Open SourceApache-2.0
$0free, forever
The whole runtime: yours to run, read, fork, and ship. Nothing held back.