You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update the README's bilingual feature description to match the current Down panel behavior: grouped tasks, subagents, terminals, detail views, elapsed runtime, and workspace git status visibility.
Copy file name to clipboardExpand all lines: README.md
+30-6Lines changed: 30 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,10 +129,12 @@ The shared interaction model is:
129
129
130
130
-**Manual backgrounding** — `Ctrl+B` sends the current active exec/terminal activity to the background without submitting a core op, clearing the foreground task-running UI while preserving streamed output.
131
131
-**Foreground state** — foreground model activity still drives the normal `Working` status, while background work is counted separately in the status line as `bg <n> subagent / <m> terminal`.
132
-
-**Task picker** — pressing `Down` when background work exists opens the bottom-pane background task picker instead of inserting a chat-stream summary. The picker separates `Subagents` and `Terminals`; `Up`/`Down` moves selection, `Enter` opens details, `Left` returns to the list, and `Esc` closes it.
133
-
-**Terminal details** — terminal detail view shows the command and the recent output tail. Pressing `x` in the picker or detail view stops background terminals through the same cleanup path as `/stop`.
132
+
-**Down task panel** — pressing `Down` opens a persistent bottom-pane task panel instead of inserting a chat-stream summary. The panel updates in place and separates `Tasks`, `Subagents`, and `Terminals`.
133
+
-**List navigation** — `Up`/`Down` moves selection, `Enter` opens details, `x` stops the selected stoppable terminal, and `Esc`/`Left` closes the panel.
134
+
-**Terminal details** — terminal detail view shows status, elapsed runtime, wrapped command/task metadata, and the recent output tail. `x` stops the terminal through the same cleanup path as `/stop` when the terminal is stoppable.
134
135
-**Slash commands** — `/ps` prints a chat-history summary of running background terminals, while `/stop` terminates all running background terminal processes for the thread.
135
-
-**Subagent details** — subagent detail view shows agent title, status, and progress. Subagents are inspectable in the background picker and switchable through the agent-thread workflow; `/stop` and picker `x` are terminal-only controls and do not kill subagents.
136
+
-**Subagent details** — subagent detail view shows agent title, role, task prompt, status, elapsed runtime, and progress lines. Subagents are inspectable in the background picker and switchable through the agent-thread workflow; non-stoppable subagents do not expose `x stop`.
137
+
-**Plan tasks** — the same `Down` panel also surfaces the latest visible plan/task list, including completed tasks, so task history is inspectable without relying only on the compact status-line count.
136
138
-**Completed background work** — completed background exec cells are flushed back into history once they finish, preserving the command and captured output without re-foregrounding the task.
137
139
138
140
This is the essential interaction change behind the Claude Code-style behavior: background work stays visible and controllable, but it no longer blocks normal chat flow.
@@ -148,6 +150,16 @@ From commit `85e937b855`:
148
150
149
151
This is intentionally marked **Beta**: the current value is useful as a rough responsiveness signal, but it is not yet an exact real-time throughput metric.
150
152
153
+
### 9. Workspace git status in the status line
154
+
155
+
The status line can now surface the current workspace diff through the configurable `workspace-changes` item:
156
+
157
+
- renders tracked changes as `+<added>/-<deleted>` using Git numstat data from the active workspace
158
+
- appends `?<count>` when untracked files are present, so a dirty workspace is still visible even before files are staged or modified in tracked paths
159
+
- hides itself for clean workspaces, keeping the status line compact when there is nothing to review
160
+
161
+
This is intended as a lightweight situational-awareness signal: it answers "did this session leave local changes behind?" without opening a separate shell or `/status` view.
162
+
151
163
### Near-term roadmap
152
164
153
165
The near-term roadmap is intentionally focused on a few CLI-facing improvements:
0 commit comments