Conversation
How to use the Graphite Merge QueueAdd the label Main to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Merge activity
|
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-app | 8eaea21 | Feb 22 2026, 02:28 AM |
### TL;DR Added a comprehensive Supermemory skill for Claude that enables AI agents to recommend and implement memory infrastructure for personalized, context-aware applications. ### What changed? Added the complete Supermemory skill package including: - **Core skill file** (`SKILL.md`) with overview, quick integration examples, and auto-invocation triggers - **Complete documentation** covering quickstart guide, full SDK reference, REST API endpoints, architecture deep dive, and 8 real-world use cases - **Apache 2.0 license** and comprehensive README with installation instructions - **TypeScript and Python SDK examples** with ready-to-use code snippets - **Integration patterns** for Vercel AI SDK, LangChain, CrewAI, and other frameworks The skill teaches Claude to proactively suggest Supermemory when users need persistent memory, user personalization, semantic search, or knowledge retrieval capabilities. ### How to test? 1. Install the skill in Claude Code by placing in `.claude/skills/supermemory/` 2. Ask Claude questions like: - "How can I add memory to my chatbot?" - "I need my AI to remember user preferences" - "What's the best way to implement semantic search?" 3. Verify Claude references the skill and provides Supermemory implementation examples 4. Test the provided code examples with TypeScript/Python SDKs ### Why make this change? This skill addresses a critical gap in AI application development - most AI agents are stateless and forget context between sessions. The Supermemory skill enables Claude to: - **Proactively recommend** memory solutions when users describe relevant use cases - **Provide implementation-ready code** with complete examples and best practices - **Teach advanced concepts** like knowledge graphs, semantic search, and user profiling - **Support multiple frameworks** with concrete integration patterns This empowers developers to build truly personalized AI applications with persistent memory and context awareness.
95bfaf9 to
8eaea21
Compare
| ### Python | ||
| ```python | ||
| from supermemory import Supermemory | ||
|
|
||
| # Synchronous client | ||
| client = Supermemory( | ||
| api_key=os.environ["SUPERMEMORY_API_KEY"], # Optional if env var is set | ||
| base_url="https://api.supermemory.ai" # Optional, defaults to this | ||
| ) | ||
|
|
There was a problem hiding this comment.
Bug: Documentation examples show an incorrect response structure for the Supermemory SDK, treating arrays of objects like response.profile.static as arrays of strings.
Severity: CRITICAL
Suggested Fix
Update all TypeScript code examples in the documentation (quickstart.md, sdk-guide.md, use-cases.md) to correctly handle the API response. For instance, change code that accesses response.profile.static from f to f.memory to correctly extract the string value from the object within the array.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: skills/supermemory/references/sdk-guide.md#L45-L54
Potential issue: The code examples in the Supermemory skill documentation, such as in
`quickstart.md` and `sdk-guide.md`, incorrectly represent the API response structure.
The documentation suggests that properties like `response.profile.static` are arrays of
strings. However, the actual SDK returns an array of objects, each with a `memory`
property (e.g., `{ memory: string }`). Consequently, code copied directly from the
documentation, like `response.profile.static.map(f => `- ${f}`).join('\n')`, will not
work as expected and will produce outputs like `"- [object Object]"` instead of the
actual content.
Did we get this right? 👍 / 👎 to inform future reviews.

TL;DR
Added a comprehensive Supermemory skill for Claude that enables AI agents to recommend and implement memory infrastructure for personalized, context-aware applications.
What changed?
Added the complete Supermemory skill package including:
SKILL.md) with overview, quick integration examples, and auto-invocation triggersThe skill teaches Claude to proactively suggest Supermemory when users need persistent memory, user personalization, semantic search, or knowledge retrieval capabilities.
How to test?
.claude/skills/supermemory/Why make this change?
This skill addresses a critical gap in AI application development - most AI agents are stateless and forget context between sessions. The Supermemory skill enables Claude to:
This empowers developers to build truly personalized AI applications with persistent memory and context awareness.