Skip to content

feat(cli): Make /context and /stats commands use modal dialogs #3083

@pomelo-nwu

Description

@pomelo-nwu

name: 'Feature Request'
about: 'Suggest an idea for this project'
title: 'feat(cli): Make /context and /stats commands use modal dialogs'
labels:

  • 'type/feature-request'
  • 'status/needs-triage'

What would you like to be added?

Change the /context and /stats commands to display their output in modal dialogs (similar to /permissions, /settings, /mcp), instead of adding items to the chat history.

Why is this needed?

  1. Context pollution: Diagnostic output consumes conversation tokens — counterproductive when using /context to check context usage.

  2. Hard to trigger /context: With /context detail as a subcommand, typing /context triggers autocomplete dropdown, making it difficult for users to simply press Enter and run the main command.

  3. Consistent UX: Other management commands (/permissions, /settings, /mcp, /auth, /trust) already use modal dialogs.

Current Behavior

  • /context / /stats → Output added to chat history, consumes context tokens
  • Typing /context shows autocomplete (detail), hard to trigger main command

Proposed Behavior

  • /context / /stats → Open modal dialogs
  • Dialog content NOT stored in context
  • No subcommand autocomplete interference — clean interaction

Additional context

Discussed in PR #3042. Commands like /permissions, /settings, /mcp demonstrate the dialog pattern:

action: (): OpenDialogActionReturn => ({
  type: 'dialog',
  dialog: 'permissions',
}),

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions