Skip to content

feat(tui): enrich /status card with runtime context and colorized fields#673

Open
grandmaster451 wants to merge 1 commit into
MoonshotAI:mainfrom
grandmaster451:feat/rich-status-card
Open

feat(tui): enrich /status card with runtime context and colorized fields#673
grandmaster451 wants to merge 1 commit into
MoonshotAI:mainfrom
grandmaster451:feat/rich-status-card

Conversation

@grandmaster451

Copy link
Copy Markdown

Extends the /status report with additional runtime context and visual polish while keeping the existing panel layout.

Changes

  • Add swarm mode, provider/model counts, MCP server summary, and active goal to the status report.
  • Colorize permission and plan-mode values for quicker scanning.
  • Surface session title and goal status when available.
  • Update unit tests to cover the new rows.

Testing

  • pnpm vitest run apps/kimi-code/test/tui/components/messages/status-panel.test.ts
  • pnpm run typecheck in apps/kimi-code

Extends the `/status` report with additional runtime context and
visual polish while keeping the existing panel layout.

- Add swarm mode, provider/model counts, MCP server summary, and active goal
to the status report.
- Colorize permission and plan-mode values for quicker scanning.
- Surface session title and goal status when available.
- Update unit tests to cover the new rows.
@changeset-bot

changeset-bot Bot commented Jun 11, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: bbbe543

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

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

Copy link
Copy Markdown

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: bbbe543cdd

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

{ label: 'Plan mode', value: planMode ? 'on' : 'off' },
{ label: 'Permissions', value: formatPermissionMode(permission, value, errorStyle) },
{ label: 'Plan mode', value: formatPlanMode(planMode, value, muted) },
{ label: 'Swarm', value: formatSwarmMode(options.swarmMode, value, muted) },

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Read swarm mode from runtime status

When /status successfully loads runtime status it uses that snapshot for permissions, plan mode, model, and context, but the new Swarm row always reads the cached app state. In contexts where app state is stale while session.getStatus() has the current value (the SDK status includes swarmMode in packages/node-sdk/src/rpc.ts), the status card can report Swarm off even though the active session is in swarm mode. Please derive this row from options.status?.swarmMode ?? options.swarmMode, matching the other runtime-backed fields.

Useful? React with 👍 / 👎.

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