Resume a project decision

Before you start

Choose one decision worth carrying into another session. Include the reason and a source that can be checked later. Avoid copying the whole transcript; a useful record is small enough to review and specific enough to challenge.

Record a decision with its evidence

Use project knowledge for a finding intended to outlive the current task:

{"name":"ctx_knowledge","arguments":{"action":"remember","category":"decision","content":"Use the existing authentication middleware for new protected routes. Verify against the current routing configuration before implementation."}}

Replace the example with your actual decision and source reference. Do not include credentials, personal data or unrelated conversation history.

Use session state for current progress: what is done, what remains and which files were involved. Session state, knowledge and read caches have different jobs.

Resume in the same project

Check the active project before recalling knowledge. Query the subject of the decision:

{"name":"ctx_knowledge","arguments":{"action":"recall","query":"authentication middleware"}}

Inspect the returned candidates and the available session state. A compact startup briefing depends on integration and configuration; it is not access to every prior host conversation.

Recheck the source

Open the current routing configuration in this example. If the middleware changed, the previous decision is evidence of earlier reasoning, not current truth.

Update or remove obsolete knowledge. Keep an unresolved disagreement visible until you have enough source evidence to settle it.

Continue from a clear boundary

Give the next task the verified decision, relevant references and the next open question. The receiving session still needs source access. A shared reference does not broaden its permissions.

Use versioned SDK workspaces, checkpoints and handoffs for portable state. The agent bus exchanges information; bounded WorkGraph execution separately manages dependencies, ownership, concurrency and budgets. Neither a handoff nor a claim grants new source permissions.

Check the result

A new session can explain why the decision was made, verify whether it still applies and identify the next action without reconstructing the entire investigation.

See memory and knowledge for storage and export boundaries, and session tools for exact operations.

Sources & versions6 references · Reviewed 17 Sept 2026

• mod.rsrust/src/tools/ctx_knowledge/mod.rsGitHub
• remember.rsrust/src/tools/ctx_knowledge/remember.rsGitHub
• linked.rsrust/src/tools/ctx_knowledge/linked.rsReviewed checkout
• project_cmd.rsrust/src/cli/project_cmd.rsReviewed checkout
• state.rsrust/src/core/session/state.rsGitHub
• 03-memory-and-knowledge.mddocs/reference/03-memory-and-knowledge.mdGitHub

Core checkout

0ce2207ee4

Reviewed runtime

3.10.2

SDK release

1.1.0

Separate baselines for source, CLI/configuration and SDK contracts. Review does not certify every platform or integration.

Versions & compatibility