StackUnderflow

Use when the user wants to RESUME or CONTINUE prior coding-agent work — "resume my codex session", "continue where I left off in <project>", "what sessions ran in this folder", "pick up that grok conversation", or any ask for session/resume ids across agents (Claude Code, Codex, Grok, Cursor Agent, …). Surfaces every agent's recent sessions under a path with the exact resume command for each.

Search local coding-agent session history before acting. Use BEFORE an Edit or Write to a file, BEFORE a non-trivial Bash command (a build, migration, or destructive/long-running command), and whenever the user references a past decision ("what did we decide about X", "why is this done this way", "didn't we agree to Y"), a specific file, or "what worked last time" — cases where a prior session on this machine may already hold the decision, the failure mode, or the exact working command. Queries the local `stax memory` CLI (StackUnderflow) across every past Claude Code / Codex / Cursor session so you do not re-derive an answer, contradict an earlier choice, or repeat a known failure. Local and read-only; nothing leaves the machine.

Use BEFORE starting any non-trivial coding task in an existing project — feature work, refactors, bugfixes, or "look at this codebase" requests. Triggers when the user asks to add/change/fix something inside a repo (e.g. "add X to the dashboard", "refactor the auth flow", "fix the bug in cost calculation", "why is this slow"). Surfaces recent prior sessions in the same project so the agent isn't redoing work or contradicting decisions made in past sessions.

Use when the user references a SPECIFIC FILE in a coding task — "fix the bug in routes/cost.py", "what was that change to api.ts about", "refactor stackunderflow/store/queries.py", or any request that names a path. Surfaces past sessions that read or wrote that file so the work is grounded in prior context (recent edits, why the file is shaped that way, half-finished refactors).

Use when the user references a PAST DECISION, choice, or rationale — "what did we decide about caching?", "why is X done this way?", "didn't we agree to use Y?", "remind me how we handled Z before". Searches indexed message history across all prior sessions to find the conversation where the decision was made and surfaces the matching excerpt with timestamp.