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: codex-rs/tui/docs.md
+5-7Lines changed: 5 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ The auto-worktree startup flow branches on the `AutoWorktree` enum (see `@/codex
39
39
|`Ask`| After TUI init, in `run_ratatui_app()`| Sets `pending_worktree_ask = true`, deferred to a TUI popup shown after onboarding but before `App::run()`|
40
40
|`Off`| N/A | Skips worktree creation entirely |
41
41
42
-
The `Ask` popup is implemented by `nori::worktree_ask::run_worktree_ask_popup()`, a standalone mini-app screen (same pattern as `update_prompt.rs`) that runs its own eventloop before the main `App`. It presents two options ("Yes, create a worktree" / "No, continue without a worktree") and returns a boolean. If the user confirms, `setup_auto_worktree()` is called and config is reloaded with the new cwd via `load_config_or_exit()`. Ctrl-C, Escape, and the "No" option all skip worktree creation. On failure, the TUI continues with the original cwd.
42
+
The `Ask` popup is implemented by `nori::worktree_ask::run_worktree_ask_popup()`, a standalone mini-app screen using the same pre-`App`event-loop pattern as `nori::update_prompt` in release builds. It presents two options ("Yes, create a worktree" / "No, continue without a worktree") and returns a boolean. If the user confirms, `setup_auto_worktree()` is called and config is reloaded with the new cwd via `load_config_or_exit()`. Ctrl-C, Escape, and the "No" option all skip worktree creation. On failure, the TUI continues with the original cwd.
43
43
44
44
The main event loop in `app/mod.rs` processes:
45
45
@@ -390,8 +390,6 @@ The fork context flows through `ChatWidgetInit.fork_context` -> `spawn_agent()`
390
390
391
391
**Session context injection:** Both `spawn_acp_agent()` and `spawn_acp_agent_resume()` in `chatwidget/agent.rs` set `AcpBackendConfig.session_context` to the contents of `@/codex-rs/tui/session_context.md` (loaded at compile time via `include_str!`). This tells the ACP agent that it is running inside the nori CLI and provides a source-code URL for self-referential questions. The context is prepended (without `SUMMARY_PREFIX` framing) to the first user prompt only and then consumed (see `@/codex-rs/acp/docs.md` for the hook context injection mechanism).
392
392
393
-
Debug-only commands (not shown in help): `/rollout`, `/test-approval`
394
-
395
393
The `/logout` command is only available when the `login` feature is enabled. The `/config` command requires the `nori-config` feature.
396
394
397
395
@@ -847,10 +845,10 @@ The `--dangerously-bypass-approvals-and-sandbox` flag (alias: `--yolo`) works in
847
845
848
846
**Update Checking:**
849
847
850
-
The TUI uses Nori-specific update checking via files in `@/codex-rs/tui/src/nori/`:
851
-
-`update_action.rs`: Update action handling
852
-
-`updates.rs`: Version checking against GitHub releases
853
-
-`update_prompt.rs`: User prompting for updates
848
+
The TUI uses Nori-specific update checking via the modules in `@/codex-rs/tui/src/nori/`:
849
+
-`nori/update_action.rs`: Update action handling
850
+
-`nori/updates.rs`: Version checking against GitHub releases
851
+
-`nori/update_prompt.rs`: User prompting for updates
0 commit comments