statusline

The user wants the pi indicator in their status line: $ARGUMENTS

statusLine is a single global field in ~/.claude/settings.json. There is exactly one, and a plugin cannot ship its own — the plugin settings.json supports only agent and subagentStatusLine. So there is no way to add this without writing to the user's settings, and every step below exists because of that: whatever is already there is theirs, it is probably the only status line they have, and replacing it is not a thing to do quietly.

Work through this with them. Do not run it end to end and report afterwards.

1. Find out what is already there

python3 -c "
import json, os
p = os.path.expanduser('~/.claude/settings.json')
d = json.load(open(p)) if os.path.exists(p) else {}
print(json.dumps(d.get('statusLine', None), indent=2))
print('refreshInterval:', (d.get('statusLine') or {}).get('refreshInterval', '(unset)'))
"

If the command contains pi-delegate/statusline-wrapper.sh, it is already ours. Stop and go to step 6 (update in place). Wrapping a wrapper is the obvious way to end up running the user's real status line twice, and then four times.

2. Probe it — do not reason about it

Whatever is there, run it and look. It gets a JSON payload on stdin, so give it one:

printf '%s' '{"session_id":"probe","cwd":"'"$PWD"'","model":{"id":"claude-opus-5","display_name":"Opus 5"},"workspace":{"current_dir":"'"$PWD"'","project_dir":"'"$PWD"'"},"version":"2.0.0","context_window":{"used_percentage":25}}' \
  | <their command> > /tmp/pi-probe.out 2>/tmp/pi-probe.err
echo "exit=$?  lines=$(wc -l < /tmp/pi-probe.out)"
cat /tmp/pi-probe.out

This is the whole reason the composition is safe for people whose setup you have never seen. You are not guessing at ccstatusline, starship, powerline or a personal shell script — you are looking at the bytes it produced. Note the line count; that is what the "after" preview needs.

Then show them their pi segment, on its own:

"${CLAUDE_PLUGIN_ROOT}/scripts/statusline.sh"