Quickstart

recall

Recall selected project context in-flow with recall_context, plus supported Analytics recall, with visible source and applicability.

recall is how your agent pulls relevant saved context mid-task without you leaving your flow. General work uses the recall_context MCP tool. When your agent is about to draft, decide, or answer a question, it can recall selected decisions, facts, preferences, rules, and lessons from the authorized space, with source and applicability intact. Supported Analytics or CRM work has an additional specialist path through get_analysis_context.

This is the structural fix for the old "destination app" problem. You do not open a tool to look a number up; the context rides along inside claude.ai, Claude Code, Cursor, or Codex, and your agent reaches for it when it needs it.

What it returns

recall_context takes a query and optional project and purpose relevance hints. It searches the selected authorized space; those hints do not change access or silently exclude other projects. Each result carries:

an entry ID and bounded summary;
its source, including provenance and available capture metadata;
its applicability, including general or bounded scope, project references, and conditions.

Recall is read-only and in-flow. It never mutates your store; it only surfaces what is already there. Because it reads, it needs only context:read — a read-only context key can recall.

For Analytics, get_analysis_context returns definitions, schema notes, saved queries, and notes with provenance and asserted or caveat status. There is no public query-history bootstrap source or importer.

Fetch the full entry

Recall returns bounded body previews and does not inline stored SQL. For general recall, call get_context_entry with the returned entry_id when summary_truncated is true or you need complete content. For Analytics recall, use the type/name address when has_sql or has_crm_contract indicates more detail. The browser's scoped preview is separate: it does not run MCP recall or record agent use.

Who decides when to recall

Recall is a tool your agent decides to call — ClariLayer exposes it; it does not force a call. In practice you get the most value by making recall the first step of your agent's loop. For Claude Code, Cursor, or Codex, the Quickstart generates one managed-install prompt from the local client you explicitly select. Your local agent inspects only that client's canonical instruction target, asks before editing, and installs a managed range that carries the recall-first and completion-checkpoint workflow into future sessions. The browser and remote server do not inspect or edit your files. The claude.ai path connects to the production custom Connector over OAuth and does not install a local project instruction file.

That is the difference between "can recall in-flow" (always true — the tool is there) and "always recalls first" (true only when your client config or prompt makes it so).

How general recall is scoped

General recall searches the entire selected authorized space. Optional project and purpose values help relevance; they are not access controls or candidate filters. A customer- or project-bounded entry stays bounded when recalled elsewhere, and the response identifies how its applicability relates to the supplied project hint.

Ranking and delivery are bounded. A delivery record shows that context was served to the client, not that the agent used it or that the content is true.

Honest use-case scoping

This section applies to specialist Analytics get_analysis_context. use_case is a precision hint. Analytics recall prefers entries in that use case together with unscoped context. When there is no authoritative in-scope result, it can rescue a strong cross-scope match and label it use_case_mismatch instead of silently hiding it or pretending it is in scope. Inspect the additive honesty fields when present: use_case_warning, off_scope_entries, routing_confidence, and available_use_cases.

Set strict_use_case: true when the task must never use cross-scope fallback. In that mode, recall does not rescue off-scope entries.

A typical loop

Your agent calls recall_context for relevant general work, and the specialist Analytics recall when applicable.
It answers from recalled context, preserving source and applicability. Analytics answers also carry known status mismatches.
If the task confirms a durable change, it remembers it. If the suggestion still needs review, it uses propose and stops for human acceptance instead of treating proposal-only work as live context.
If a compatible recalled definition is checked or has drifted, it reconciles it through the supported warehouse actual_sample or HubSpot crm_evidence adapter.
Before reporting completion, it calls context_checkpoint with context_updated and active live entry references, or no_update_required after explicitly checking that no durable context update was needed. Proposal-only work cannot reach this completing step.

The checkpoint receipt persists the agent's bounded managed-protocol declaration and validates its referenced ClariLayer objects. It does not independently prove that an entry changed, external code deployed, a warehouse validation passed, a query is correct, or saved context is semantically equivalent to another system. update_failed and proposal-only work are non-completing outcomes.

Confirmed corrections and new notes remain available to later sessions when you or your agent explicitly save them.

Status, honestly

For specialist Analytics reconciliation, a recalled entry's status is either asserted or caveat. asserted means saved but not contradicted; caveat means reconcile found a declared-vs-actual mismatch worth treating with care. General memory is not independently reconciled. The stronger verified status remains gated and is not part of the live public result contract — see Verified vs Asserted for what that means and why.