View and manage your terminal command history directly in the VS Code Explorer outline view.
- 📝 Command History - Automatically captures every command and its output
- 🟢/🔴/🟡 Status Indicators - Shows success, failure, or running status
- 🔧 Actions - Rerun commands, copy output, clear history
- 🤖 Agent Skill - Ships an Agent Skills package so pi, Copilot Chat, and Claude Code can auto-record their activity alongside your shell commands (v1.3.0)
- 🔒 Security - Detects and redacts passwords, API keys, and tokens (v0.4.0)
- 📊 Privacy Dashboard - View and manage your security settings
- 🎨 Clean Display - Strips ANSI codes and shows clean output
- 💾 Persistent - History survives VS Code restarts
Terminal Velocity exposes a small local HTTP endpoint (POST http://127.0.0.1:8765/history) and ships an Agent Skills-format package inside the VSIX. Compatible harnesses can auto-record commands, prompt-response pairs, and tool results into the same Terminal History view.
Supported agents: pi, GitHub Copilot Chat, Claude Code, and any harness that follows the Agent Skills spec.
The skill is bundled in this extension at resources/skills/terminal-velocity-history/. After installing the extension, copy that directory into your harness's skill path:
# pi (global)
cp -r "$(code --user-data-dir)/extensions/CoreyHamren.terminal-history-outline-1.3.0/resources/skills/terminal-velocity-history" \
~/.pi/agent/skills/
# Claude Code
cp -r "$(code --user-data-dir)/extensions/CoreyHamren.terminal-history-outline-1.3.0/resources/skills/terminal-velocity-history" \
~/.claude/skills/
# Project-scoped (any harness, in this repo)
cp -r resources/skills/terminal-velocity-history .pi/skills/- Open VS Code Settings.
- Search for
terminal history agentand check Terminal Velocity: Agent: Enabled. - Click the Activate Agent Endpoint button in the Terminal History view title bar.
The endpoint binds to 127.0.0.1:8765 by default. Host, port, and an optional bearer token are all configurable under terminalHistory.agent.*.
# After a bash tool call
~/.pi/agent/skills/terminal-velocity-history/scripts/record.sh \
"npm test" "All 12 tests passed" "terminal" "/workspace/project" "myagent" "0"
# After producing a final response to a user prompt
~/.pi/agent/skills/terminal-velocity-history/scripts/record-chat.sh \
"What does this error mean?" "It means the lock file is stale."See the Agent Skill Guide for the full install walkthrough, configuration reference, and troubleshooting tips.
- Frequestly Asked Questions
- Installation
- Current and Future Features
- Agent Skill Guide — install & use the Terminal Velocity history skill with pi, Claude Code, etc.
- Open a terminal (
Ctrl+`) - Run any command - it appears in the Terminal History view (Explorer sidebar)
- Click a command to see its output
- Hover over history items for actions: Rerun, Copy Command and/or output, Delete Entry
- Search command and output history
| Setting | Values | Description |
|---|---|---|
detectionEnabled |
true/false | Enable/disable sensitive data detection |
redactionLevel |
off/warn/redact/block | How to handle sensitive data |
warnOnDetection |
true/false | Show warning when sensitive data is detected |
customPatterns |
string[] | Custom regex patterns for detection |
excludedCommands |
string[] | Commands to never save (regex supported) |
| Command | Description | When to Use |
|---|---|---|
npm test |
Run all unit tests | During development |
npm run precommit |
Check uncommitted changes | Before committing |
npm run prepush |
Full validation | Before pushing |
To test GitHub Actions locally:
- Ubuntu/Debian:
curl -s https://raw.githubusercontent.com/nektos/act/master/install.sh | sudo bash - macOS:
brew install act - Windows:
choco install act - More info: https://github.com/nektos/act
- VS Code 1.93+
- Shell Integration enabled (default: on)
MIT © chamren86
Enjoy tracking your terminal history! 🚀
