Desktop App Status

No. Origin's main workflow works through Claude Code commands, MCP tools, and the origin CLI. The local daemon owns memory either way.

Use the desktop app only if you want a graphical layer on top of the same local memory system. Do not wait for the GUI to use the daily handoff loop.

The main Origin repo owns the daemon, business logic, CLI, MCP server, shared wire types, and Claude Code plugin files.

That is the runtime path documented on this website: setup, capture, recall, handoff, distill, pages, data paths, diagnostics, and releases.

The desktop app lives separately so the GUI can evolve without making the local runtime depend on a specific frontend shell.

When an issue is about memory behavior, retrieval, MCP tools, setup, service management, or the CLI, use the main Origin repo. When an issue is about the desktop UI itself, use the desktop app repo.

The desktop app should be treated as a client over the daemon, not a second source of truth. The daemon owns the database, pages, sessions, and retrieval behavior.

That boundary is what lets Claude Code, Codex, Cursor, Claude Desktop, Gemini CLI, terminal commands, and the optional GUI share the same memory layer.

The main daemon, CLI, MCP server, core, shared types, and plugin files are Apache-2.0.

The optional desktop app has its own repository and AGPL-3.0-only license boundary. Check the desktop repo before reusing app code or contributing across that boundary.