Repository navigation
Memory: a shared wiki about the user, and a switch for what each app may do with it - #1
Merged
Merged
Conversation
…may do with it LaunchX now keeps one memory for the user: Markdown pages (profile, preferences, schedule, resume, projects, people) that their apps and agents read and write together. The user sets Off, Read or Read & write for each app, on its card, in the page's new Memory view, or with `lx memory access <id> <level>`. Everything starts off, and the launcher checks the switch on every request. It follows the components of agent memory: a log of every write (memory/log.jsonl), linked pages (memory/pages/), and a short index of one line per page for an app or agent to load at the start of a session. Updates name the revision they read, so a stale write is refused with the current page instead of silently undoing someone else's change. The version each write replaces is kept, and the page can show and restore it. Each managed service gets LAUNCHX_MEMORY_URL and its own LAUNCHX_MEMORY_TOKEN, which opens /api/memory and nothing else and is never handed to dependents, so writes are logged under the caller's id. A manifest may ask for access with [service.<id>.memory] wants/reason. Agents learn about memory from a generated launchx-memory skill, while the user allows it. `lx memory` (ls, show, write, append, rm, history, log, search, lint, index, access, open) works with or without a running launcher. SPEC.md §12 is the contract. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
LaunchX now keeps one shared memory for the user: a small wiki of Markdown pages (profile, preferences, schedule, resume, projects, people) that their apps and agents read and write together, so the person doesn't have to tell every app the same things.
The user decides, per app, whether it may read memory, read and write it, or neither: on the app's card, in the page's new Memory tab, or with
lx memory access <id> none|read|write. Everything starts off, and the launcher checks the switch on every request. Agents get their own row, which controls whether alaunchx-memoryskill is published to them.Design
Built from the components of agent memory:
memory/log.jsonl: every write, by whom, whymemory/pages/<page>.md, linked with[[page]]GET /api/memory/index: one line per page, at most 200 lines / 25 KBlx memory lint,logandhistorybase); a stale write gets409with the current page to merge. The page's editor handles this too, showing the other writer's version.LAUNCHX_MEMORY_URLand their ownLAUNCHX_MEMORY_TOKEN. That token opens/api/memoryand nothing else, and is never handed to dependents, so no service can write under another's name.[service.<id>.memory] wants = "read"|"write"plus areason, shown next to the switch. A manifest can't grant itself access.~/.launchx/memory, andlx memoryworks with or without a running launcher (writes are serialised withflock).The contract is in
SPEC.md§12. §11 (security model) gains rows for memory access, impersonation and lost updates, plus notes on same-user processes and prompt injection.CLI
lx memoryls | show | write | append | rm | history | log | search | lint | index | access | openTesting
cargo test: 13 unit tests (5 new inmemory.rs) and the end-to-end test, extended. A fixture service reads and writes memory with its own token at each access level. The test also covers: stale writes refused; an app's HTTP token rejected by memory; a memory token rejected everywhere else; the page's switch needing its own Origin; the memory skill appearing, following page changes, and being withdrawn; andlx memoryworking with the launcher stopped.Companion
Schedule Everything is the first app to use it: AutoPhd-org/schedule-everything#21 (merged).
Not in this PR
schedulebut notresume).GET /api/memoryand compare itsrev).🤖 Generated with Claude Code