Feature: statusline under the input box — model, effort, usage windows (5h/7d/monthly) with $ spent/cap and reset countdowns

[grknbyk]

Feature Description

Add a persistent one-line statusline under the input box showing live session + usage info:

deepseek/deepseek-v4-flash [high] · 5h $0.24/$3.00 (3h 40m) · 7d $0.24/$6.00 (6d 22h) · 1m $0.23/$10.00 (30d 20h)

Segments:

• Current model + configured reasoning effort (shown only when explicitly set via /effort or the model picker; hidden when "Default" is selected)
• 5h window: credits spent / cap, colored by percentage, with reset countdown
• 7d window: same for the weekly window
• 1m: monthly credits spent / pool, with billing-period reset countdown

Everything needed is already available client-side from the existing usage endpoint (credits.windowLimits.fiveHour/weekly {used, cap, resetAt}, credits.credits.monthlyCredits, summary.totalCost, subscription.data.currentPeriodEnd) and existing helpers (formatCredits, formatDuration, getUsageColor). We prototyped this locally by patching dist/cli.mjs (v1.7.0) and it works with real data.

Two related small UX fixes:

1. Merge the two bottom-bar lines into one: » auto-accept on [shift+tab] · ? for shortcuts · taste on (saves a terminal row).
2. The mode indicator labels the auto-accept mode as "accept edits on", while /mode auto-accept and permissions.defaultMode: "auto-accept" call it auto-accept — renaming the label to "auto-accept on" makes them consistent.

Use Case

No response

Additional Context

Working prototype (v1.7.0 on Windows, patched dist/cli.mjs — usage fetched once on input-component mount, segments render as data arrives; model name shows immediately):

• A context-usage segment (e.g. 48k/1000k) would round this out, but contextUsage isn't currently populated for the input component, so we skipped it.
• Happy to share the exact patch details or open a PR if the CLI source becomes available. (Prototype written with help from Claude Code.)

How important is this to you?

None

[dthyresson]

FYI there is a planned mod feature to have setStatus as part of https://commandcode.ai/docs/mods#ui-surface to be able to customize the status message which will be nice so people can set to show what is critical for them to see.

[dan64]

This would cover a big chunk of what I'd want from a status line. Adding my vote for three additional segments that would round it out:

• Context usage (e.g. 48k/1000k) — the issue author mentioned it but skipped it because contextUsage isn't populated for the input component; worth wiring that data up.
• Cache hits — prompt cache reads/writes per session/request, since caching has a big impact on both cost and speed.
• Tokens received / sent — per-request and cumulative counters for the session.

The usage-window segments (5h / 7d / monthly with $ spent/cap and reset countdowns) are the most valuable part — those limits are currently invisible until you hit them.

I expect that these info will be available in the standard TUI and not left to the user customization. Are very useful info and are available in almost all "decent" coding agent.