You'll notice
Useful3 Signal1
/statusLine setup cleans trailing prompt characters and asks you when it finds no shell prompt.
What's wrong with this entry?
Anonymous. No account, no email.
/statusLine
What
The instructions used when setting up a custom status line now say to strip trailing $ or > characters when importing your shell prompt, and to ask you what you want if no shell prompt is found and you gave no instructions.
Evidence
If the imported PS1 would have trailing "$" or ">" characters in the output, you MUST remove them.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
/status shows a "Session kind" row
Both mention status
-
v2.1.222
Model refusal fallback no longer claims your session model changed
Both mention status
-
v2.1.228
Settings problems split into notices and genuinely invalid entries
Both mention status