Skip to content

feat(tui): show tab activity detail#26476

Open
fcoury-oai wants to merge 6 commits into
fcoury/iterm-tab-status-shell-commandfrom
fcoury/iterm-tab-status-detail
Open

feat(tui): show tab activity detail#26476
fcoury-oai wants to merge 6 commits into
fcoury/iterm-tab-status-shell-commandfrom
fcoury/iterm-tab-status-detail

Conversation

@fcoury-oai
Copy link
Copy Markdown
Contributor

@fcoury-oai fcoury-oai commented Jun 4, 2026

Why

The structured status is most useful when it explains what Codex is doing or what needs user attention. This layer adds that detail while bounding terminal output and avoiding high-frequency OSC writes.

What Changed

  • show running commands, status headers, and the most recent completed activity
  • describe approval, permission, MCP, tool-suggestion, and tool-input waits
  • select concurrent command detail deterministically by start order
  • sanitize control, bidi, and invisible characters; escape OSC separators; cap detail length
  • throttle detail-only updates to 250 ms while allowing state changes immediately

How to Test

  1. Run Codex in iTerm2 and start commands, including overlapping commands.
  2. Confirm Working detail follows the newest running command and falls back to the surviving command when it completes.
  3. Open an approval or tool-input prompt and confirm Waiting detail describes the request.
  4. Complete the turn and confirm Idle shows the last activity.

Targeted tests:

  • just test -p codex-tui tab_status
  • just test -p codex-tui osc_text
  • just test -p codex-tui picks_the_latest_command_then_falls_back_to_the_survivor

The full codex-tui run passed 2,800 tests; two unrelated guardian feature-flag tests remain failing on main.

Stack

  1. #26474 base OSC 21337 tab status
  2. #26475 flattened shell command display
  3. feat(tui): show tab activity detail #26476 detailed and throttled tab activity (this PR)

Part of #25879.

@fcoury-oai fcoury-oai force-pushed the fcoury/iterm-tab-status-shell-command branch from ecf6985 to f1ad153 Compare June 5, 2026 15:21
@fcoury-oai fcoury-oai force-pushed the fcoury/iterm-tab-status-detail branch from 07736d1 to d04ac5c Compare June 5, 2026 15:21
@fcoury-oai fcoury-oai force-pushed the fcoury/iterm-tab-status-shell-command branch from f1ad153 to 14e20be Compare June 5, 2026 16:26
@fcoury-oai fcoury-oai force-pushed the fcoury/iterm-tab-status-detail branch 2 times, most recently from e839871 to bd8bcd9 Compare June 5, 2026 16:39
@fcoury-oai fcoury-oai marked this pull request as ready for review June 5, 2026 16:56
Copy link
Copy Markdown
Contributor

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bd8bcd9624

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread codex-rs/tui/src/bottom_pane/tab_status_state.rs
Comment thread codex-rs/tui/src/bottom_pane/mod.rs Outdated
Comment thread codex-rs/tui/src/tab_status.rs
@fcoury-oai fcoury-oai force-pushed the fcoury/iterm-tab-status-detail branch from bd8bcd9 to ef38cb7 Compare June 5, 2026 17:25
@fcoury-oai
Copy link
Copy Markdown
Contributor Author

@codex review

Copy link
Copy Markdown
Contributor

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ef38cb7e47

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread codex-rs/tui/src/bottom_pane/mod.rs
Comment thread codex-rs/tui/src/bottom_pane/approval_overlay.rs Outdated
Comment thread codex-rs/tui/src/tab_status.rs Outdated
@fcoury-oai
Copy link
Copy Markdown
Contributor Author

@codex review

1 similar comment
@fcoury-oai
Copy link
Copy Markdown
Contributor Author

@codex review

Copy link
Copy Markdown
Contributor

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f6d85dedf0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread codex-rs/tui/src/bottom_pane/mod.rs
@fcoury-oai
Copy link
Copy Markdown
Contributor Author

@codex review

Copy link
Copy Markdown
Contributor

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 620df376c1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

//! OSC 21337 is an iTerm2 extension; other terminals ignore it. The payload
//! is a semicolon-separated list of `key=value` pairs. We emit `status`
//! (label), `indicator` (dot color), and `status-color` (text color).
//! Formats bounded activity detail and owns the low-level terminal write path.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3 Badge Split complex tab-status detail change

This commit is 799 changed lines across 22 files and is not mechanical: it combines OSC detail formatting/sanitization and throttling, bottom-pane waiting-detail plumbing, command/activity tracking, and test updates. The change-size guidance says complex logic changes should stay under 500 lines and, when larger, identify a staged split (AGENTS.md lines 114-120); a reviewable split would be to land the bounded OSC/detail formatting and throttle state with tests first, then wire command/activity and modal detail providers in a follow-up.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reduced this layer from 799 to 749 changed lines by moving the shared OSC sanitizer and terminal-title reuse into PR1, where it is independently tested. This PR remains the third layer of the explicitly requested three-PR stack; splitting the remaining detail plumbing would require a fourth PR. I am leaving this thread open for maintainer visibility.

Comment thread codex-rs/tui/src/bottom_pane/tab_status_detail.rs
Comment thread codex-rs/tui/src/bottom_pane/tab_status_state.rs
Comment thread codex-rs/tui/src/chatwidget/command_lifecycle.rs Outdated
@fcoury-oai fcoury-oai force-pushed the fcoury/iterm-tab-status-shell-command branch from 27d665c to 8da1e5c Compare June 5, 2026 18:15
@fcoury-oai fcoury-oai force-pushed the fcoury/iterm-tab-status-detail branch from 620df37 to 94bceb2 Compare June 5, 2026 18:30
@fcoury-oai
Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown
Contributor

Security review completed. No security issues were found in this pull request.

View security finding report

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@chatgpt-codex-connector
Copy link
Copy Markdown
Contributor

Codex Review: Didn't find any major issues. Delightful!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant