An Obsidian-style view of what Möbius knows about you. Memory renders the agent's knowledge graph as a force-directed view: each node is a small markdown note or a map-of-content, and the links between them are the connections the agent drew as it learned. Tap any node to read the note behind it.
The graph starts from Memory's small seed map and fills in over time — Möbius writes a note when it learns something durable about you, your apps, or how you like to work, and links it into the web. Memory is both the window onto that knowledge and the app that owns scheduled graph maintenance.
Open the App Store mini-app in Möbius, find Memory, tap Install.
In the App Store, choose Install from URL and paste:
https://raw.githubusercontent.com/mobius-os/app-memory/main/mobius.json
Möbius will fetch the manifest, show you the requested permissions and schedule, and install with one tap.
- The graph — notes and maps-of-content as nodes, sized by how often they're touched;
moclinks (a note belongs to a map) andlinklinks (one note references another) as edges. - Node detail — tap a node to read its markdown (frontmatter + body), rendered safely.
- Health hints — dangling links, orphans, and other graph problems surface so the agent (and you) can see where the graph needs tidying.
Memory reads .ready from shared storage, then reads graph.json and individual notes from that exact Git commit through Möbius’s confined shared-Git endpoint. The visible app is a read-only viewer; its scheduled job defaults to 05:30 and can be rescheduled from Memory’s Maintenance settings.
On first install, the job publishes a complete deterministic seed graph before it starts the background-agent review. It then tries Möbius’s configured Background agents in order, consolidates chat notes, rebuilds graph.json, commits changed files, and appends a maintenance record under shared/memory/app-state/update-log/. The agents use confined text-only Claude and Codex adapters. Unchanged maintenance runs do not create commits.
The latest operational outcome is written atomically to app-state/run-status.json, with append-only history under app-state/run-log/. If no provider is usable, the run reports a degraded outcome and leaves the initial seed readable without proposed agent changes.
Analysts cite short, closed-set source handles; trusted runner code expands them to canonical chat IDs before applying the same strict provenance check. A semantically invalid primary result is recorded with a safe rejection code and does not suppress a configured fallback. Chats observed by a failed run—or deferred by the prompt-size bound—remain in a bounded FIFO retry queue until a successful analyst run actually receives them, so recovery does not depend on those chats remaining in tomorrow's latest-results window.
On upgrade from the retired generation-directory format, Memory validates the complete shape of every legacy generation, imports each one as a Git commit, puts the formerly published generation at the branch tip, atomically switches .ready, and then removes the redundant full-copy directory tree. If validation or import fails, the pointer and legacy copies remain untouched.
The repository is shared/memory/repository. Standard Git history is available for inspection. To roll the published graph back without rewriting history, run python3 memory_store.py rollback <commit> from the installed Memory source; this creates a new commit with the selected historical tree and atomically advances .ready. Consolidation also refuses to demote a surviving, specifically filed node into the generated Unfiled fallback.
Installing Memory also contributes a small system-prompt fragment and graph skill. Möbius captures installed system-app fragments once when a chat starts; that immutable chat prompt activates an app-local, prompt-scoped reader. The chat agent states what prior context it needs, a read-only background agent traverses the graph, and the result comes back with verified markdown file pointers. The graph is never injected wholesale. Installing or uninstalling Memory changes future chats, while an already-started chat retains the prompt it began with. Uninstalling also removes Memory's schedule while preserving the owner's shared Git repository for recovery/reinstall. The deterministic graph indexer and Git publisher are app-owned.
That split keeps the responsibility clear: Memory reads, writes, and consolidates its graph without depending on another app.
MIT