agent-afk 3.87.0 → 3.87.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -2
- package/dist/cli.mjs +365 -346
- package/dist/index.mjs +1 -1
- package/dist/telegram.mjs +2 -2
- package/package.json +10 -6
package/README.md
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# Agent AFK
|
|
2
2
|
|
|
3
|
-
>
|
|
3
|
+
> Delegate the work. Keep the judgment.
|
|
4
4
|
>
|
|
5
|
-
>
|
|
5
|
+
> **Agent AFK** is a local-first control plane for long-running AI agent work. Hand off multi-session, headless tasks to parallel agents — then stay in control with traces you can read (`afk trace show`), resumable sessions, verification passes before anything ships, and a phone ping the moment work lands in a terminal state. Bring your own model.
|
|
6
6
|
|
|
7
7
|
[](https://www.npmjs.com/package/agent-afk)
|
|
8
8
|
[](https://nodejs.org/)
|
|
@@ -28,6 +28,7 @@ afk chat "hello"
|
|
|
28
28
|
|
|
29
29
|
- **Chat from your terminal** — `afk chat "..."` for one-shot, `afk i` for a REPL with full tool access (Bash, file ops, web fetch, grep/glob, subagents).
|
|
30
30
|
- **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.
|
|
31
|
+
- **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`.
|
|
31
32
|
- **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.
|
|
32
33
|
- **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.
|
|
33
34
|
|