Skip to main content
Available on hosted HTTP MCP and stdio MCP. crystal_wake accepts optional channel and agentId.

When to use

Use wake at the start of a session to get a brief orientation. Follow with recall for a focused task or recent for more transcript context. A wake call reads context; it does not create a checkpoint. The HTTP briefing selects up to five goals from prospective-store or goal-category memories and up to five decision-category memories. It does not promise an active-status filter or fixed seven-day window. The HTTP handler does not require query embedding. The stdio API-key formatter expects goal and decision arrays that the HTTP response does not supply. Those arrays can therefore be empty even when the briefing includes goals and decisions. The authenticated key selects your account. Omitting channel still applies bounded message visibility; it does not expose every private conversation.

Parameters

Examples

Examples use placeholder IDs. Replace them with IDs returned by your account. MCP examples show the JSON tool arguments and the JSON inside the tool result, not the outer MCP envelope.

Resume work

Request:
Hosted MCP response (selected fields; other fields omitted):

Resume in an explicit scope

Request:
Hosted MCP response (selected fields; other fields omitted):

Read the briefing

Treat the briefing as an orientation, then verify any decision you act on with a focused lookup. A null checkpoint is normal when none is available. The recent-memory and message arrays are bounded; they do not describe the whole account.

Errors and common mistakes

Do not infer that goals are complete or active from their presence here. Stdio empty goal/decision arrays can reflect its formatter rather than an empty account. Use the supplied briefing and a focused recall to investigate. Check account and scope when a session looks unfamiliar.