sessions

# /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. - **Never read entire session files into context.** Session files can be 1-7MB. Always use the extraction scripts to filter first, then reason over the filtered output. - **Never extract or reproduce tool call inputs/outputs verbatim.** Summarize what was attempted and what happened. - **Never include thinking or reasoning block content.** Claude Code thinking blocks are internal reasoning; Codex reasoning blocks are encrypted. Neither is act...