agent-afk weekly downloads statistics

Agent AFK

Start a task and walk away. AFK builds the feature, verifies its own work, and texts you when it's done. You come back to a receipt of every step, every decision, and what's waiting on you.

Open source. Runs locally. Works with any model provider, including local models. Your keys, your machine, your rules.

<p align="center"> <video src="https://github.com/user-attachments/assets/4a84f6e4-2494-4065-a01f-54a1c557f7f3" width="820" autoplay loop muted playsinline> Your browser does not support the video tag. </video> </p>

⭐ Like the idea of an agent you can walk away from? Star the repo -- it's the fastest way to help other people find it.

Quick Start

npm install -g agent-afk    # Node 22.22.2–22.x, 24.15–24.x, or 26+ (23.x and 25.x excluded)
afk login                   # authenticate (auto-detects Claude Code / Codex creds)
afk doctor                  # verify everything works
afk chat "hello"             # first real conversation

# Preview a behaviour change before applying it
afk whatif --append "Always ask a clarifying question before using tools." --verify

That's it. You're in.

Using pnpm? pnpm add -g agent-afk works, but pnpm 10 and later block build scripts by default and skips postinstall (with an easy-to-miss warning — see #2199). Run pnpm approve-builds -g after install to approve the hook, or use npm install -g agent-afk instead. If an afk daemon is already running and pnpm skipped the hook, restart it manually with afk service restart daemon — on macOS the hook restarts the daemon automatically when it runs, but on Linux you must always run this command after an upgrade even when the hook ran. If you have a manually-started Telegram bot, also run afk telegram restart.

Try without installing: npx agent-afk chat "hello" runs a one-shot turn with zero global install.

Already using Claude Code or Codex? afk login will detect your existing credentials automatically. Run afk migrate to import your plugins, skills, and MCP servers too -- it live-reads the source tool's dirs, so anything you install there keeps showing up in AFK with no re-run.

Codex imports use CODEX_HOME when set (otherwise ~/.codex) and also discover shared skills in ~/.agents/skills. Native .codex-plugin/plugin.json manifests are recognized alongside Claude-format manifests; explicit [plugins."name@marketplace"] enable/disable settings apply at runtime. Without an installed-plugin registry, discovery selects one cached directory per marketplace/plugin using descending numeric-aware directory order. This is a filesystem fallback, not a guarantee of the version selected by Codex. Codex-hosted app connectors and TOML MCP server loading are not imported.

📖 Full documentation at docs.agentafk.com -- quickstart, configuration, model setup, surfaces, skills, and SDK reference.

What you can do with it

• Chat from your terminal — afk chat "..." for one-shot, afk for a REPL with full tool access (Bash, file ops, web fetch, grep/glob, subagents).
• Hand long work off to a daemon — afk daemon runs headless. Pair it with send_telegram and you get pings on your phone when work lands in a terminal state.
• Read the trace — every run writes an append-only record of what the agent did. afk trace show prints it back as a human-readable receipt — tool calls, gate decisions, subagent lifecycles, cost — so you can audit a run without reaching for jq.
• Message Claude from Telegram — afk telegram setup walks you through bot token + allowlist. After that you have a private chat surface backed by the same session manager as the REPL.
• Built-in orchestrators — /mint, /diagnose, /spec, /research, /ship, /review dispatch subagent waves. /mint takes a feature idea and runs spec → research → plan → parallelize → build → verify → ship. /diagnose forks parallel root-cause hypotheses for failing tests and bugs.
• Cross-session memory — Claude remembers preferences, decisions, and procedures across runs. See Memory below.
• Background subagent jobs — dispatch a subagent with mode:'background'; results auto-deliver into the model's context when they finish. /bgsub lists running and completed jobs, /bgsub:join <id> replays a result manually.

What only afk does

afk whatif behavioural impact predictor. Before changing a prompt, model, skill, or memory rule, predict how the agent's behaviour will shift without touching your real config. Run afk whatif --append "Always ask a clarifying question before using tools." --verify and the engine diffs the system prompts, predicts labelled behaviour shifts, then optionally verifies empirically by running sandboxed episodes and measuring rates. No real writes happen during the run. Source: src/whatif/, docs/whatif.md.…