Repository navigation
feat(memory-graph): add opt-in stacked nodes and emphasized connections - #1792
Merged
Merged
Conversation
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-mcp | 0cce18d | Oct 11 2026, 04:08 AM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-app | 0cce18d | Commit Preview URL Branch Preview URL |
Oct 11 2026, 04:07 AM |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add configurable rendering in the original package so the console can stop carrying a Bun patch. Existing consumers keep icon-based document nodes, existing edge styling and callback-only document opening unless they opt in.
GraphAppearanceand acceptappearance.documentNodes: "icons" | "stacked"andappearance.connections: "default" | "emphasized"onMemoryGraphandGraphCanvas. The options are independent. Stacks preserve the existing node box and anchors; emphasized connections recover from a quiet overview with semantic relations stronger than neutral, glow-free document sources.MemoryGraph.openDocumentOnEnter, defaulting to false. With a callback, it enables a focus-scoped Enter action for a selected persisted document or one confirmed memory source. Invalid or ambiguous sources suppress opening; typing, modifiers, repeat and composition are ignored. Routing and authorization remain the consumer's responsibility. Callback-free consumers receive no new focus/opening behavior.edgeDocument, retain the explicit upstream document edge type and document the options. Prepare version 0.2.5 and its workspace lock metadata.The console migration in mono#3495 depends on the published release. Merging this version bump triggers the existing main-branch npm publishing workflow. Nothing has been merged or published, and the mono patch must not be removed before the release is available.
Verification
check-types, all 197/197 unchanged tests, build and scoped Biome checks pass. Existing source-wide Biome warnings remain; no test files changed.npm packartifact loads via ESM and CJS in an isolated clean install and frozen install. Hosted console types/lint/build and self-hosted browser types/build pass against that exact artifact. Playground and MCP/widget types/build pass.Default pixel parity is against current upstream main (
552803c0), not the older npm 0.2.4 artifact. The release also includes the already-merged document/source-edge separation from #1701; this PR retains that data model rather than reverting it. A registry 0.2.4-to-0.2.5 upgrade is not claimed to be pixel-identical.The accepted unselected stack is preserved. The revised selected treatment still needs visual acceptance; passing checks are not whole-PR approval.