1.62.0

Added
Memory with the message. The app's local HTTP endpoint gains /context.
What happens: on a prompt event of Claude Code or Codex (UserPromptSubmit) or Gemini CLI (BeforeAgent), aura-bridge hook asks the app for memory relevant to the user's message, then hands it to the model as the hook's additionalContext.
What the app controls: it decides what to give through serve_http's new context_for argument.
When nothing is given: if nothing arrives within 3 seconds, the bridge prints nothing.
Why: in our tests agents called a memory tool on only 20–40% of real tasks, while memory given with the prompt reached 80–100% of the work.
RecallScope::exclude_session leaves out records captured in the current conversation, which the agent already has.
A map of what memory holds. The app's MCP server tells each connected app, in its instructions and in recall's description, which projects and topics memory holds, with note counts and the latest dates. It is built from metadata only and limited to what that app may see. In our tests agents told what memory holds gave the right (newer) value in 80% of tasks instead of 47%, made fewer needless memory calls, and cost 7–12% less per task.