feat(memory): open existing inline session references - #12
Open
KinomotoMio wants to merge 6 commits into
Open
Conversation
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.
What this opens up
When a Memory already contains a session ID in inline code, Obelisk can now turn that existing trace into a direct reading path. For example,
codex:<uuid>becomes interactive only when the local database confirms that the exact session exists.There is no new Markdown syntax and nothing for agents to learn or rewrite.
What changed
sessionstable.session-linkstyling and icon from the Memory header.Boundary
After discussing the ownership boundary, this PR deliberately does not introduce an
obelisk://protocol or document a new agent-facing convention. Core and the published Obelisk skill are unchanged.The App does not parse UUIDs or assume a Codex-specific shape. A value becomes interactive only when it exactly matches a real
sessions.id, which keeps the behavior provider-neutral and avoids accidental format rules.Existing Memory files are not migrated or edited.
Validation
Passed:
npm test— 298 testsnpm run typechecknpm run lint— no errors; 4 pre-existing unused-variable warningscd app && npm run test:electron:memory-linkscd app && npm run test:electronThe Electron Memory test exercises the production renderer build and confirms exact DB resolution, title-first labels, UUID hover text, untitled fallbacks, accessible labels, provider-neutral IDs, unknown and ordinary inline code, fenced-code exclusion, reused styling, and in-App navigation.
Closes #10