Snipararepo context sync
Menu
Product
Start Work BriefWhat changed before you codePR Answer PacksSourced review contextContext AuthoritySource, freshness, confidenceAvoid OverlapCollision and stale warningsManifestoMemory belongs to the workspace
Developers
GitHub AppRepository and PR workflowsMCPAgent client integrationAPIProgrammatic context accessSandboxAdvanced execution layerOrchestratorAdvanced proof gatesDocsGuides and reference
VisionPricingDocs
Sign inStart Free

Shared Context

Shared Context Collections are reusable documentation packages that can be linked to one or more projects. Use them for technical standards, operating notes, API conventions, review rules, and other source-backed context that should not be copied into every project.

Recommended Model

  • Code Context: short workspace-wide engineering rules that should apply broadly.
  • Project files: repository docs, diagrams, attachments, and current source material tied to one project.
  • Shared collections: reusable technical documents linked deliberately to the projects that need them.

Workflow

  1. Create a collection for reusable technical material.
  2. Link the collection only to projects where that context should influence retrieval.
  3. Set priority and token budget so source-specific project files keep authority.
  4. Use Code Context for simple workspace-wide engineering rules.

Helvabase Boundary

Business-facing RFP, proposal, and client dossier workflows belong in Helvabase. Snipara documentation focuses on developer context, project retrieval, memory, and MCP integration.