Tell agents not to override or list backlogs
Assisted-by: Claude Opus 4.7 via Claude Code
change lspxvrvlzyolywnyprtqpqwrkrovwzol
commit 1bcc3dae70073390f46b042f50f9e7d625e05ba1
author Alpha Chen <alpha@kejadlen.dev>
date
parent ukyvzkyx
diff --git a/AGENTS.md b/AGENTS.md
index b7374a5..0df273b 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -2,7 +2,7 @@
 
 ## Task management
 
-The backlog lives in the `ranger` CLI, not GitHub Issues. Use `ranger` to read and update tasks. `RANGER_DEFAULT_BACKLOG=quire` is set in the shell, so `--backlog` can be omitted.
+The backlog lives in the `ranger` CLI, not GitHub Issues. Use `ranger` to read and update tasks. `RANGER_DEFAULT_BACKLOG=quire` is set in the shell, so `--backlog` can be omitted — and you should never pass it. Don't run `ranger backlog list` either; the default is already correct, and listing other backlogs is out of scope for this project.
 
 The backlog shifts between sessions and even within a session — tasks get reordered, retitled, moved between states, closed, or added by the user without notice. Before acting on a task you remember (or one referenced earlier in the conversation), re-run `ranger task show <key>` and confirm state, ordering, and description against ground truth. Do not trust earlier `ranger task list` output to still be accurate; refetch when placement matters (e.g. moving to top/back of ready).