agents/AGENTS.md

@@ -14,42 +14,6 @@
   project's `AGENTS.md` / `CLAUDE.md` specifies a different directory,
   that wins.
 
-## Code health
-
-Strategic over tactical, with follow-through. Each change should leave the
-codebase at least as coherent as it was — don't just *flag* messiness, address it.
-
-- **Default to acting on cleanups, not just mentioning them.** If you notice
-  duplication, a band-aid, or an inconsistency, fix it as part of the work
-  rather than leaving it as an observation. "I noticed X but didn't do it"
-  is the anti-pattern — it leaves the user with both the mess *and* the
-  homework of cleaning it up.
-- **Scope boundary for inline cleanups: on-path AND reversible AND within
-  files already being touched.** Inline when all three hold. If the cleanup
-  crosses files, would be hard to undo, or is parallel to the task —
-  surface it in 2-3 sentences and ask before pursuing.
-- **Tolerate duplication until the pattern is real.** Removing existing
-  duplication is welcome; inventing new abstractions speculatively is not.
-  Rule of three: don't unify two instances, wait for the third.
-- **Treat friction as architectural data.** Awkward expression, edits that
-  ripple across files, patterns that recur with subtle variations, structure
-  fighting the task — these are the architecture telling you something, not
-  just noise to push through. Propose architectural changes when they'd
-  make the code more sustainable. Frame as proposals with a clear ask
-  ("now, or follow-up?"), not silent rewrites.
-
-## Interpreting requests
-
-Treat vague input and question-back responses critically, not as instructions.
-
-- **Vagueness is not authorization.** "Make it cleaner", "maybe X?",
-  "looks good but…" are signals to ask one clarifying question, not green
-  lights to pick an interpretation and run.
-- **A tangent is not an answer.** If you ask "A or B?" and get "maybe X?",
-  that's a new question, not a pick. Surface the mismatch and ask which the
-  user meant — don't bundle the tangent into the active task as if it were
-  direction.
-
 ## Sandbox
 
 - **Always run commands sandboxed first.** Only use `dangerouslyDisableSandbox: true` as a last resort after a sandbox-related failure — never preemptively.
@@ -61,22 +25,6 @@ Treat vague input and question-back responses critically, not as instructions.
 - `$TMPDIR` is set by the sandbox to a writable path. `.tmp/` inside the project directory is always writable without prompts.
 - Ensure `.tmp/` is listed in `.gitignore` when creating temp files in a tracked repo.
 
-## Shell — literal `!` in Bash commands
-
-- **Never put a literal `!` in an inline Bash command.** Claude Code's Bash tool
-  escapes every `!` to `\!` at the transport layer before any shell sees it —
-  even inside single/double quotes and in non-interactive shells
-  (anthropics/claude-code#61121, a regression of a fix shipped in 2.1.87). The
-  stray backslash corrupts downstream tools: Python `!=` → SyntaxWarning + broken
-  string, jq, Jira JQL (`status != Done` → server 400), branch names, etc.
-  `bash -c '...'` and quoted heredocs do **not** avoid it.
-- **One rule covers everything:** if a command needs a `!`, write the command/code
-  to a file with the Write tool under `.tmp/` and run the file. `.tmp/` is
-  prompt-free via the `Edit(.tmp/**)` allow rule in `~/.claude/settings.json`. Do
-  **not** create the file with inline `printf`/`echo >` — that re-escapes the `!`.
-- Need a literal `!` inline anyway: ANSI-C hex `$'\x21'` (e.g. `B=$'\x21'; cmd
-  "${B}=…"`) yields a real `!` with no literal `!` in the command.
-
 ## Tooling
 
 - **`ccc` for semantic code search.** Repos containing a
@@ -88,8 +36,3 @@ Treat vague input and question-back responses critically, not as instructions.
   it, results are filtered to the current working directory's
   subtree. The `ccc` skill has the full reference;
   `grep`/`rg`/`find` remain fine for exact-string lookups.
-- **`ccc index` / `ccc init` are read-safe maintenance.** They only
-  write to the gitignored `.cocoindex_code/` directory, never to
-  source. Run them without confirmation prompts — at session start,
-  after refactors, or before a search when the index may be stale.
-  Treat like `grep` for permission purposes, not like a code edit.

claude/statusline-command.sh

@@ -12,40 +12,7 @@ used=$(echo "$input" | jq -r '.context_window.used_percentage // empty')
 
 # Rate limits
 rl_5h=$(echo "$input" | jq -r '.rate_limits.five_hour.used_percentage // empty')
-rl_5h_reset=$(echo "$input" | jq -r '.rate_limits.five_hour.resets_at // empty')
 rl_7d=$(echo "$input" | jq -r '.rate_limits.seven_day.used_percentage // empty')
-rl_7d_reset=$(echo "$input" | jq -r '.rate_limits.seven_day.resets_at // empty')
-
-# Whole hours until a unix-epoch timestamp, ceiling-rounded; falls back to label on past/empty
-hours_until() {
-	local ts="$1" fallback="$2"
-	[[ -z "$ts" ]] && { printf '%s' "$fallback"; return; }
-	local diff=$(( ts - $(date +%s) ))
-	(( diff <= 0 )) && { printf '%s' "$fallback"; return; }
-	printf '%dh' "$(( (diff + 3599) / 3600 ))"
-}
-
-# Same idea, days
-days_until() {
-	local ts="$1" fallback="$2"
-	[[ -z "$ts" ]] && { printf '%s' "$fallback"; return; }
-	local diff=$(( ts - $(date +%s) ))
-	(( diff <= 0 )) && { printf '%s' "$fallback"; return; }
-	printf '%dd' "$(( (diff + 86399) / 86400 ))"
-}
-
-# Render a percentage with optional suffix; yellow >=80, red >=90. \e[39m restores default fg without dropping the surrounding dim.
-pct_color() {
-	local val="$1" suffix="$2" int color=''
-	int=${val%.*}
-	(( int >= 90 )) && color=$'\e[31m'
-	(( int >= 80 && int < 90 )) && color=$'\e[33m'
-	if [[ -n "$color" ]]; then
-		printf '%s%.0f%%%s\e[39m' "$color" "$val" "$suffix"
-	else
-		printf '%.0f%%%s' "$val" "$suffix"
-	fi
-}
 
 # Thinking / effort
 thinking=$(echo "$input" | jq -r '.thinking.enabled // empty')
@@ -56,12 +23,11 @@ dim=""
 [[ -n "$branch" ]]          && dim="$dim ($branch)"
 [[ -n "$model" ]]           && dim="$dim $model"
 [[ -n "$effort" ]]          && dim="$dim $effort"
-[[ -z "$effort" && -n "$thinking" ]] && dim="$dim thinking"
-[[ -n "$used" ]]            && dim="$dim $(pct_color "$used")"
+[[ -n "$used" ]]            && dim="$dim $(printf '%.0f%%' "$used")"
 
 usage=""
-[[ -n "$rl_5h" ]]  && usage="$usage $(pct_color "$rl_5h" "/$(hours_until "$rl_5h_reset" 5h)")"
-[[ -n "$rl_7d" ]]  && usage="$usage $(pct_color "$rl_7d" "/$(days_until "$rl_7d_reset" 7d)")"
+[[ -n "$rl_5h" ]]  && usage="$usage $(printf '%.0f%%/5h' "$rl_5h")"
+[[ -n "$rl_7d" ]]  && usage="$usage $(printf '%.0f%%/7d' "$rl_7d")"
 [[ -n "$usage" ]]   && dim="$dim -$usage"
 
 printf '\033[1m%s\033[0m\033[2m%s\033[0m\n' "$dir" "$dim"