Ships with octo. Installing the plugin gets this command.
⚡ How it fires
How this command gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/history
👁️ Context preview
What this command does when you run it.
[advanced] Query past workflow results — filter by workflow type, date, or provider
📊 Stats
Stars3,869
Forks362
LanguageShell
LicenseMIT
📦 Ships with octo
</> Command definition
history.md
---command: history
description: "[advanced] Query past workflow results — filter by workflow type, date, or provider"
allowed-tools: Bash, Read, Grep
---# Workflow History (/octo:history)
**Your first output line MUST be:** `🐙 Octopus History`
Query structured records of past Claude Octopus workflow runs.
## EXECUTION CONTRACT (Mandatory)
When the user invokes `/octo:history`, follow these steps in order.
### STEP 1: Locate Run Store
Check for the run store file:
```bash
RUN_STORE="${HOME}/.claude-octopus/runs/run-log.jsonl"
if [[ -f "$RUN_STORE" ]]; then
TOTAL=$(wc -l < "$RUN_STORE" | tr -d ' ')
echo "Run store: $TOTAL entries"
else
echo "No run store found at $RUN_STORE"
echo ""
echo "The run store records results from multi-AI workflows:"
echo " /octo:discover - Multi-AI research"
echo " /octo:develop - Multi-AI implementation"
echo " /octo:review - Multi-AI code review"
echo " /octo:debate - Multi-AI deliberation"
echo " /octo:embrace - Full 4-phase lifecycle"
echo ""
