wassname
9c188f60be
Move per-project agent memory into the repo so it is version-controlled. Harness path /root/.claude/projects/.../memory now symlinks here, so auto-load still works while the files live under git. Un-ignore only .claude/memory/ (worktrees, locks, local settings stay ignored). Co-Authored-By: Claudypoo <288921227+claudypoo@users.noreply.github.com>
1.5 KiB
name, description, metadata
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| feedback-afk-autonomy | When the user is AFK (via /afk command or AFK cron pings), prefer more autonomous queueing not less. Do not stand down on speculative work just because the headline question is answered. |
|
When the user is offline (AFK), the default should be to fill the queue with reasonable follow-ups, not to stand down and wait for explicit direction. The user prefers autonomous initiative during AFK windows.
Why: The user said, after I had explicitly chosen to stop queueing speculative work mid-AFK: "actually I'd prefer the opposite if I'm afk". The CLAUDE.md preference for "stop and ask" applies during interactive sessions; during AFK windows, time is the scarcer resource than judgment calls.
How to apply: During /afk-driven or cron AFK pings, when the immediate question is answered and the queue is empty, do NOT default to "standing down until you're back". Instead, queue the natural next batch (additional seeds for confidence, an ablation that resolves the obvious follow-up question, a sweep over a parameter that's now informed by the result). Pick the option with the best information-per-dollar ratio that doesn't require non-trivial code edits or new craft work. Reserve "stop and ask" for moves that genuinely need user judgment (e.g. drafting hand-crafted training data, rewriting non-trivial code, changing experimental direction). See afk-protocol in this memory store if it exists.