feat: add /clear and /compact slash commands#132
Draft
yamaceay wants to merge 3 commits into
Draft
Conversation
The GPUI desktop UI depends on Metal shader compilation, which requires Xcode developer tools to be installed (xcrun must find the `metal` binary). On machines without Xcode this hard-blocked every `cargo build`, even when only the terminal TUI was needed. Introduce a `gpui-ui` Cargo feature that gates all GPUI-related code: - `Cargo.toml`: `gpui`, `gpui_platform`, and `gpui-component` are now optional dependencies, activated only by `--features gpui-ui`. The gpui entry in `[dev-dependencies]` is removed (it was unused in the unit-test suite). - `src/app/mod.rs`, `src/ui/mod.rs`: `pub mod gpui` gated behind `#[cfg(feature = "gpui-ui")]`. - `src/ui/backend.rs`: The `GpuiTerminalCommandExecutor` import and its single usage site are gated; the TUI-only path falls back to `DefaultCommandExecutor` (which `GpuiTerminalCommandExecutor` itself delegates to internally). - `src/main.rs`: The `--ui` code paths (logging setup, model resolution, `app::gpui::run()`) are gated. Passing `--ui` without the feature produces a clear error message rather than a linker crash. - `src/cli.rs`: The `UiSettings::load()` call that reads the GPUI- persisted default model is gated; TUI-only builds fall through to the alphabetical-first-model fallback. Build commands: # TUI only (no Xcode required): cargo build --no-default-features # With GPUI desktop UI (requires Xcode / Metal): cargo build --features gpui-ui
Introduce a `SlashCommand` struct (name, aliases, description) and an `all_commands()` function that returns a static slice of all registered commands. This gives the rest of the codebase — in particular the upcoming autocomplete popup — a single, authoritative place to discover what slash commands exist, without needing to duplicate the match arms in `process_command`. The help text is now derived from the registry instead of being a hard- coded string, so adding a new command in one place is sufficient. No behavior change: all existing commands keep the same names, aliases, and runtime behaviour.
Adds two new slash commands to the terminal TUI:
- `/clear` — wipes the conversation message history (message nodes,
active path, plan) for the current session, then clears
the UI transcript. The session itself stays alive so the
user can continue without re-starting.
- `/compact` — placeholder that shows an informational error until a
proper summarisation implementation lands.
The data path is:
CommandProcessor (commands.rs)
→ KeyEventResult::{ClearContext,CompactContext} (input.rs)
→ BackendEvent::{ClearContext,CompactContext} (app.rs)
→ handler in handle_backend_events (backend.rs)
→ UiEvent::ClearMessages / UiEvent::DisplayError (terminal UI)
yamaceay
force-pushed
the
feat/clear-compact-commands
branch
from
b3ac43b to
73deb60
Compare
stippi
requested changes
Jun 11, 2026
| }; | ||
| if let Some(session_id) = current_session_id { | ||
| let _ = backend_event_tx | ||
| .send(BackendEvent::ClearContext { session_id }) |
Owner
There was a problem hiding this comment.
I would make /clear start a new session instead. Not actually clear the current one.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
PR 2 of 5 — slash-command autocomplete series.
Dependency / merge order:
Why
Users need a way to reset a long-running conversation without quitting the
process.
/clearis the minimal version;/compactreserves the name for afuture summarisation implementation.
What
Two new slash commands, wired end-to-end through all four layers:
/clear— wipes the active session's message history:message_nodes,active_path,next_node_id,messages, andplanon the
ChatSessionstruct.UiEvent::ClearMessagesso the TUI transcript is immediately cleared.the user can keep chatting in the same session immediately.
/compact— currently a stub:UiEvent::DisplayErrorwith "not yet implemented — use /clear to reset"until a proper summarisation implementation is added.
Files changed
commands.rsClearContext+CompactContextinCommandResult; new match arms; new entries inall_commands()input.rsClearContext+CompactContextinKeyEventResult; mapping fromCommandResultbackend.rsClearContext+CompactContextinBackendEvent; two new handler armsapp.rsTest plan
/clear→ transcript clears; new messages work normally in the same session./compact→ info/error message appears; session is unaffected./helpoutput includes both new commands with descriptions./model,/plan, etc.) are unaffected.cargo build --no-default-featurespasses.