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
Copy file name to clipboardExpand all lines: README.md
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ That policy is understandable from the perspective of the upstream maintainers,
38
38
39
39
The goal of **Open Codex CLI** is not to diverge for the sake of divergence. The goal is to keep a small, intentional delta on top of upstream Codex CLI, make that delta easy to understand, and keep the fork mergeable as upstream evolves.
40
40
41
-
## Targets
41
+
## Current Goals
42
42
43
43
- solve real Codex CLI usage problems I run into, whether they are bugs or features worth borrowing from Claude Code
44
44
- keep improving the Codex CLI experience under `zellij` (**Fuck Off Tmux!**)
@@ -120,8 +120,13 @@ This is an instruction-policy feature rather than a hardcoded scheduler: it enab
120
120
121
121
From recent fork-specific TUI changes:
122
122
123
+
The feature is centered on two background lanes:
124
+
123
125
-**Terminal commands** — long-running terminal sessions continue in the background instead of keeping the main turn blocked by foreground waiting or polling. Empty `command/exec/write` interactions keep the terminal backgrounded, so normal chat input can be submitted while the shell process continues.
124
126
-**Subagents** — long-running agent work is tracked as background activity after spawn/wait tool calls complete, including agent nickname, role, status, and progress lines when available.
127
+
128
+
The shared interaction model is:
129
+
125
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.
126
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`.
127
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.
@@ -130,7 +135,7 @@ From recent fork-specific TUI changes:
130
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.
131
136
-**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.
132
137
133
-
This is the underlying interaction change behind the Claude Code-style behavior: background work stays visible and controllable, but it no longer blocks normal chat flow.
138
+
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.
134
139
135
140
### 8. Status line token throughput visibility (Beta)
0 commit comments