recall
Recall — Restore Developer Memory
When to Use
Call mcp__goldfish__recall to restore context from previous sessions. Recall runs automatically at session start, but users can also invoke /recall for targeted queries (search, cross-project, specific time ranges).
mcp__goldfish__recall({})
Default parameters (last 5 checkpoints, no date window) cover most cases.
Common Scenarios
- New session, need prior context —
recall()with defaults - After context compaction — recall to restore lost state
- Searching for past work —
recall({ search: "auth refactor", full: true }) - Cross-project standup —
recall({ workspace: "all", days: 1 }) - Just need the plan —
recall({ limit: 0 })
More from anortham/goldfish
plan
Create and manage persistent plans in Goldfish memory — use when starting multi-session work, making architectural decisions, or when the user discusses project direction, roadmaps, or design decisions that need to persist across sessions
13plan-status
Assess progress against the active Goldfish plan using checkpoints and plan data — use when the user asks about project progress, how things are going, what's been accomplished, or wants a status check against their plan
12checkpoint
Save developer context to Goldfish memory — checkpoint at meaningful milestones, not after every action
12standup
Generate a standup report from Goldfish memory across all projects — use when the user asks for a standup, daily update, progress summary, what they've been working on, or needs a report for a team sync
11session-memory
Automatically restore session context from persistent memory at the start of every coding session. Use this skill IMMEDIATELY when starting work to recall previous checkpoints, active plans, and git context. MANDATORY for context restoration.
2progress-tracking
Proactively checkpoint work progress at key moments without asking permission. Use when completing tasks, fixing bugs, making discoveries, or reaching milestones. Builds persistent memory across sessions.
2