Remember / Save Context
bridge_save_contextSave key decisions, preferences, and insights across all Claude surfaces for persistent recall in future conversations.
Instructions
Remember something for later. Use this when the user says things like "remember this", "save this", "note this", "keep this for later", "don't forget", or when an important decision, preference, or insight comes up that should persist across conversations. This saves context that will be available in ALL Claude surfaces (Chat, Code, Cowork) — even in future sessions. Use proactively when you recognize something worth remembering: a decision made, a user preference expressed, a lesson learned, a key file identified, or a workflow established.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Short labels for categorization. Examples: ['frontend', 'react'], ['deploy', 'ci-cd'], ['auth']. Helps with filtering later. | |
| type | Yes | Classify the context: "decision" when the user chose between options (e.g. "let's use PostgreSQL", "we'll go with REST not GraphQL"). "preference" when the user expresses how they like things done (e.g. "I prefer tabs", "use French for conversation", "keep responses short"). "insight" when a fact or lesson is discovered (e.g. "the API rate-limits at 100 req/s", "that bug was caused by timezone handling"). "file_ref" when a key file is identified (e.g. "src/auth.ts handles all JWT logic"). "workflow" for processes (e.g. "deploy flow: merge → CI → staging → prod"). "note" for anything else worth remembering. | |
| content | Yes | What to remember. Write it clearly so it will be useful when retrieved later by any Claude surface. | |
| project | No | Project name if this context is project-specific. Use the same name consistently (e.g. "acme-site", "payments-api"). Omit for personal preferences or general notes. | |
| source_surface | Yes | Where this conversation is happening. "chat" for Claude.ai chat, "code" for Claude Code (terminal/IDE), "cowork" for Claude Cowork sessions. | |
| response_format | No | Response format: json or markdown | markdown |