History and Rerun
Every structured interaction — raw commands through the composer and semantic requests — is recorded in history. Open the history drawer with Ctrl+H.
History item fields
Section titled “History item fields”Each entry records:
| Field | Description |
|---|---|
| User input | What you typed (command or intent) |
| Source | raw (command mode) or semantic (ask mode) |
| Generated command | The AI-generated command, if semantic |
| Executed command | What actually ran (may differ if you edited) |
| Status | success, failure, rejected, planned, interrupted |
| Exit code | Shell exit code (0 = success) |
| Duration | How long execution took |
| CWD | Working directory at execution time |
| Planner source | ollama or mock (semantic items only) |
| Workflow run ID | Links to parent workflow run, if applicable |
Browsing history
Section titled “Browsing history”The history drawer provides:
- Search — filter by text across user input, generated command, and executed command
- Session filter — view current session, all sessions, or a specific session
- Expand/collapse — click any item to see full details
Actions on history items
Section titled “Actions on history items”Click an item to expand it. The detail view shows all fields plus action buttons:
Re-executes the same command. Loads it into the composer and submits.
Copies the command to clipboard.
View Plan
Section titled “View Plan”(Semantic items only) Reopens the plan panel with the original plan details. Available when the item has a linked plan.
Save Workflow
Section titled “Save Workflow”Saves the command as a reusable workflow. Opens the workflow editor.
Workflow-linked items
Section titled “Workflow-linked items”Items that were executed as part of a workflow run show a WF badge in the metadata row. Clicking it navigates to the workflow drawer with that workflow’s run details expanded. This creates bidirectional navigation: history → workflow and workflow → history.
Persistence
Section titled “Persistence”History persists across app restarts via SQLite. The app loads the most recent 100 items on boot. Items are never automatically deleted.
What is NOT in history
Section titled “What is NOT in history”Direct terminal typing (keystrokes sent to the PTY by clicking the terminal) bypasses the composer and is not recorded in structured history. Only commands submitted through the composer are tracked.