Session-start briefing for the current project. Pass the absolute workspace/repo root in project_path so project and branch attribution stay correct across projects. Call this FIRST at every session start.

Smart memory retrieval: keyword search ranked by relevance x recency x confidence, packed into a context budget. Searches team (+personal by default, scope='team'|'personal'|'all'). Prefer this over raw search when answering questions.

Raw faceted search across crew memory. Filters: kind (note|decision|solution|gotcha|pattern|handoff), tags, author, file (path substring), project. Empty query with filters lists matches. Use recall() for smart ranking instead.

List newest memories (optionally filter kind or an exact project name; default all projects).

Automatic index of everything in memory: counts by type, author, lifecycle status, project and top tags.

Save durable knowledge (conventions, environment quirks, how-to) to shared memory and push instantly. files=[] links related repo paths (enables PR review + decay tracking). scope='personal' keeps it private on this machine. NEVER store secrets.

Record an architecture/tooling decision: what the situation was, what was decided, why, and which files it affects. Pushed instantly; teammates' agents will consult it.

Record a problem that was hit and its fix (build failures, weird bugs, env issues), optionally with raw error output, so nobody debugs it twice.

Save a small trap that cost time ('X breaks when Y', 'always Z before W'). Short and punchy.

Save a recurring codebase/project pattern others should follow ('how we add an endpoint', error-handling style...).

Write a session handoff: what was done, exact next steps, current blockers and open questions. The next session or teammate starts from this instead of zero.

Get the most recent handoff document (anyone's, or filter by author). Ideal first read when continuing someone's work.

Get a formatted commit log + changed-files summary of base..head from YOUR CODE repo, ready to summarize into a note/decision with save_note/log_decision. The AI writes the actual summary.

Full text of one memory by id (unique prefix ok) including confidence score and lifecycle status.

Delete your own memory entry. For other people's entries use mark_superseded instead.

Mark a memory as verified (you checked it is still true). Verified memories rank higher and decay slower.

Mark an outdated memory as superseded (optionally pointing to the newer replacement id). It stops appearing in recall but stays in history.

Flag a memory as stale (probably wrong now, needs re-check). Stale entries are down-ranked heavily.

Detect duplicate/overlapping memories (similar titles or same linked files) so they can be consolidated.

Provenance: every git commit that touched this memory — who changed it, when, and why (commit messages).

Time travel: read crew memory AS OF a specific commit SHA, tag or branch of the memory repo. Great for 'what did we know back then'.

Manual sync with GitHub: direction='pull'|'push'|'both'. Useful after working offline (writes made offline are queued locally and pushed here).

Announce what you're working on for the whole team: task description, optional progress percent, optional blockers list. Call at session start and whenever the task changes. Teammates see it instantly.

See everyone's current task, progress %, blockers and staleness. Read-only.

Timeline of crew memory activity: statuses, saves, lifecycle changes — newest first, optionally per author.

Create/update YOUR member profile (role like 'backend dev', timezone, free-text about). Git identity is auto-included when available.

Read a member profile (default: yours). Includes role, timezone, git identity, about.

'Why does this code/file exist?' Lookup across decisions/solutions/gotchas/patterns linked to a path (or mentioning it). Answers come from crew memory, ranked.

Review the CURRENT branch diff against base_ref through the lens of crew memory: finds memories touching changed files, flags decisions/verified knowledge likely made obsolete by this PR, so the AI can supersede/update them.

Git blame a line range in YOUR code repo, then cross-reference team memories about that file/authors — answers 'who wrote this and did anyone leave notes about it?'.