docs: add entity context documentation and fix MDX parsing#723
docs: add entity context documentation and fix MDX parsing#723graphite-app[bot] merged 1 commit intomainfrom
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| 🔵 In progress View logs |
supermemory-mcp | f667145 | Feb 03 2026, 03:30 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ⛔ Deployment terminated View logs |
supermemory-app | 9a0f366 | Feb 03 2026, 11:14 PM |
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. |
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
1 similar comment
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
Merge activity
|
Add entity context documentation to customization and add-memories pages, remove nav icons from Developer Platform, fix install.md parsing error Changes: - Remove icons from Developer Platform subheadings (Getting Started, Concepts, Using supermemory, Connectors and sync, Migration Guides) - Add Entity Context section to customization page with usage example and accordion for advanced API - Add entityContext parameter to add-memories Parameters table and examples accordion - Fix MDX parsing error in install.md (wrap curly braces in backticks)
graphite-app
bot
force-pushed
the
update-entitycontext-docs
branch
from
f667145 to
9a0f366
Compare
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
| <Accordion title="Update entity context only"> | ||
| Update entity context for a container tag without uploading content. | ||
|
|
||
| ```typescript | ||
| await client.containerTags.update("session_abc123", { | ||
| entityContext: `Design exploration conversation between john@acme.com and Brand.ai assistant. | ||
| Focus on John's design preferences and brand requirements.` | ||
| }); | ||
| ``` | ||
| </Accordion> |
There was a problem hiding this comment.
Bug: The documentation introduces an example using client.containerTags.update(), but this method does not exist in the SDK, which will cause runtime errors for developers following the guide.
Severity: HIGH
Suggested Fix
Remove the section of the documentation that references the non-existent client.containerTags.update() method. Alternatively, if this method is intended to exist, it must be implemented in the supermemory SDK package before being documented.
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: apps/docs/concepts/customization.mdx#L88-L97
Potential issue: The documentation added in `apps/docs/concepts/customization.mdx`
includes a code example that demonstrates usage of `client.containerTags.update()`.
However, investigation of the codebase and the imported `supermemory` SDK (version
^4.0.0) reveals that this method does not exist. Other SDK methods like
`client.documents.update()` and `client.settings.update()` are present, but
`client.containerTags.update()` is not. Developers attempting to use this documented
method will encounter a `TypeError` at runtime, as the function is not defined on the
client object.
Did we get this right? 👍 / 👎 to inform future reviews.
2 participants
Add entity context documentation to customization and add-memories pages, remove nav icons from Developer Platform, fix install.md parsing error
Changes: