Status line
Whether the repository has a status line is not a config key: the presence of .claude/statusline.sh and a statusLine entry in .claude/settings.json is the whole state. /devstride:setup offers to write both. The optional statusLine block covers two other things.
| Key | Shape | Default | Purpose |
|---|---|---|---|
statusLine.hiddenSegments |
string[] | [] |
Segments this repository has confirmed do not apply. Use it to record a deliberate absence — not to hide a segment whose value is merely missing, which the script already omits on its own. |
statusLine.autoUpdate |
boolean | true |
Whether the session-start hook may refresh a copied script that still carries its managed marker. It keeps the previous copy as devstride/statusline.bak in the repository's git directory, never in the work tree. From 3.18.0 a committed copy that is only behind is left alone when the branch's upstream (or origin/<baseBranch>) already carries the newer one — the hook says to pull instead — and on a detached checkout or a base, production or protected branch; on a feature branch it is refreshed and you commit it. |
From 3.26.0 the status line is two lines, each segment led by a symbol. Line 1 says where you are: ◆ model, ↯ effort, ▣ repository, ⑂ checkout, ⎇ branch. Line 2 says what is in flight, and prints only when it has something on it: ⊞ the plugin version this session runs (dim while current, coloured with the fix when a newer copy is installed or published), ▲ stage, ⇄ pull request, ⚑ release (only while a release clearance is held, or while this machine still owes close-out work). The keys statusLine.hiddenSegments takes are model, effort, repo, checkout, branch, plugin, stage, pr and release. A segment with no value is not drawn at all, symbol included, so a repository with no stage never shows a dangling ▲. Setup writes "refreshInterval": 30 in the statusLine setting so the line redraws every 30 seconds, and doctor reports a shared setting without it. The script is repo-agnostic and identical everywhere, reading your config at runtime, so re-copying it is always safe. The script's second line carries a # ds-statusline: managed v<x.y.z> marker; deleting that line is the supported way to take the file over, and nothing replaces it afterwards.
Because a shared project setting outranks a personal one, a repository status line wins over a statusLine in your own ~/.claude/settings.json. Override it for yourself alone in .claude/settings.local.json.