Files
Kilo-Org_kilo/packages/kilo-vscode/docs/chat-ui-features/command-execution.md
T
Mark IJbema 3a07f45e15 docs: rewrite migration plan as feature parity tracker, add feature docs from GitHub project issues
- Rewrite opencode-migration-plan.md as a comprehensive feature parity tracker
- Add new chat-ui-features: kilo-themed-chat-session, task-header, toggle-thinking
- Add new non-agent-features: cloud-task-support, kilo-gateway, mode-switcher,
  model-switcher, provider-configuration, repository-initialization,
  rules-and-workflows, settings-ui, task-history
- Format existing feature docs with prettier
2026-02-10 13:56:19 +01:00

1.4 KiB
Raw Blame History

Command Execution

Interactive terminal output rendering and approval controls for executed commands.

Location

Interactions

  • Expand/collapse terminal output (chevron down icon)
  • Abort button to kill running processes (shows PID)
  • Exit status indicator - color-coded dot (green=success, red=failure) with tooltip
  • Command pattern selector:
    • Allow/deny command patterns
    • Updates auto-approval settings
  • Real-time output streaming - shows live command output as it executes
  • Syntax highlighting for shell commands

Suggested migration

Reimplement? Partial.

  • With Kilo CLI executing tools server-side, “abort” should map to Kilo CLIs session abort semantics (see Phase 2 in docs/opencode-core/opencode-migration-plan.md) rather than killing a local PID.
  • If Kilo CLI does not expose the underlying process PID, the UI may need to degrade gracefully (hide PID, keep “Abort current run”).
  • Kilo CLI UI reference: command/tool output is rendered as markdown/code in packages/ui/src/components/message-part.tsx.
  • Streaming output should be sourced from Kilo CLI SSE events (adapter work), but the webview rendering can remain.