setup-statusline

Claude Code only. Codex has its OWN status line, configured through status_line in config.toml from a fixed set of named segments rather than a command — see docs/CODEX-PORT-BACKLOG.md.

Manage the super-token-saver statusline in Claude Code's ~/.claude/settings.json.

Help

ONLY show help if the user's argument literally contains the word "help" (e.g. /setup-statusline help). If no argument or any other argument is given, SKIP this section entirely and proceed to Step 1.

If the user provides "help" as argument, show usage summary and stop:

/setup-statusline — Install or uninstall the live usage monitor

Format:
  [RUN🟢] $0.10/$12.23 | [5H🟢] 9% ⏳1h32m | [W🟡] 65% ⏳1d3h | [CTX🟢] 22%
  ─────   last / total     5h window usage    weekly (≥60% only)  context window
                           (subscribers only)

Options:
  install       Register statusline (default)
  uninstall     Remove and restore previous config
  help          Show this help

Examples:
  /setup-statusline install
  /setup-statusline uninstall

Do not modify any settings. Just display the help text and stop.

Args

• install (default if no arg) — register the statusline script
• uninstall — remove and restore backup if available

Install Flow

1. Read ~/.claude/settings.json

2. Check current statusLine field:

   Case A: No statusLine — install directly.

   Case B: Already our script — check if path matches current ${CLAUDE_PLUGIN_ROOT}. If version differs, update path silently, then print "Updated to current version." and stop. If same version, print "Already installed." and stop. Check by matching the command path containing super-token-saver/scripts/statusline-logger.sh.

   Case C: Different statusLine exists — warn and ask the user:

   ⚠️ Existing statusline detected:
     command: {existing command}
   
   Options:
   1. Replace (backup existing to _statusLineBackup)
   2. Cancel
   
   Which? (1/2)
   

   Wait for user response. If "1", backup to _statusLineBackup then install. If "2", stop.