---
description: Use Snipara Hosted MCP for project context and reviewed memory.
alwaysApply: true
---

# Snipara Agent Workflow

This workspace uses Snipara Hosted MCP for current project context, business/client context, and reviewed memory.

- Check the configured Snipara MCP server before answering project-specific questions.
- Use `snipara_recall` for durable decisions, preferences, and validated learnings.
- Use `snipara_context_query` for docs, business context, current client/project truth, and narrative source material.
- When `snipara_context_query` returns `answer_pack`, use its facts, caveats, source map, and verification checklist before drafting claims.
- Use `snipara_get_chunk` before relying on exact cited wording from reference-based results.
- Use `snipara_code_callers`, `snipara_code_imports`, `snipara_code_neighbors`, or `snipara_code_shortest_path` for structural code questions.
- On paid Context plans, use `snipara_code_symbol_card` before editing important symbols and `snipara_code_impact` before risky multi-file changes or PR reviews.
- Use `snipara_plan` or `snipara_decompose` only for complex work and only when available.
- Use local file reads and tests for exact code edits and current working-tree state.
- When `snipara-companion` is installed and the LLM has a visible multi-phase plan, keep the machine plan in JSON, use `snipara-companion workflow start`, `phase-start`, and `phase-commit` per phase, and after `workflow resume` rerun `workflow phase-start` before editing again.
- Use Snipara Sandbox only when sandboxed execution or repeatable validation materially helps. For runtime-bound phases, capture compact rehydratable state with `workflow runtime-checkpoint <phase_id> --summary "<state>" --rehydrate-file <state.json>`. Then `workflow resume` restores workflow and memory continuity plus the recorded Sandbox binding and prints a reattach or rehydrate plan. It does not snapshot or exactly restore a live Snipara Sandbox or REPL process.
- End substantial work with `snipara_end_of_task_commit` when available; for managed workflows, end every phase with `snipara-companion workflow phase-commit` and the task with `snipara-companion final-commit`. Use `snipara_remember_if_novel` or `snipara_remember` only for narrow durable memories. Never store secrets.