Sessions
Search and ask questions about coding agent session history across Claude Code, Codex...
Install
npx skills add slopus/happy --skill sessions -g -a claude-code -y- Repository
- slopus/happy24.4k
- Category
- AI and agents
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also use when the user references prior sessions, previous attempts, or past investigations, even without saying 'sessions' explicitly.
/sessions (installed from EveryInc/compound-engineering-plugin ce-sessions)
Search session history across Claude Code, Codex, and Cursor and synthesize findings about what was worked on, tried, decided, or learned in prior sessions.
Usage
/ce-sessions [question or topic]
/ce-sessions
Pre-resolved context
Git branch (pre-resolved): !git rev-parse --abbrev-ref HEAD 2>/dev/null || true
If the line above resolved to a plain branch name (like feat/my-branch), use it for branch filtering and pass it to the synthesis subagent. If it still contains a backtick command string or is empty, derive the branch at runtime instead.
Repo name (pre-resolved): !basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null || true
If the line above resolved to a plain repo folder name, use it for session discovery. Otherwise derive at runtime.
Note: 2026
The current year is 2026. Use this when interpreting session timestamps.
Guardrails
These rules apply at all times during orchestration and synthesis.
