Skip to content

Scope

Project Scope

What Origin is for, what it deliberately avoids, and how to decide whether it fits your AI work.

Qi-Xuan LuUpdated 5 min read

At a glance

01

Origin focuses on AI work context that spans sessions, projects, tools, and weeks.

02

It deliberately avoids becoming a life OS, broad workflow suite, hosted memory SDK, or transcript archive.

01

What Origin is for

Origin is for serious AI work where decisions, lessons, gotchas, project constraints, and handoffs need to survive beyond one chat.

The product shape is narrow on purpose: one local daemon, shared memory across MCP clients, source-backed pages, review before trust, and readable local artifacts.

02

Not a life OS

Origin does not try to own habits, calendars, journaling, personal planning, or a full life-management system.

Those domains can produce useful memories, but Origin's scope is the AI work artifact: what an agent needs to continue work correctly.

03

Not a workflow suite

Origin is not trying to bundle dozens of agents, research loops, and productivity workflows. It is the memory layer those workflows can use.

That tradeoff keeps the product easier to understand: capture, recall, handoff, distill, inspect, and continue.

04

Not a memory SDK

Origin exposes a local daemon and MCP connector, but it is not positioned as backend infrastructure for other apps to add cloud memory features.

The intended user is someone using AI tools daily who wants local, inspectable, shared work context.

05

Not for one-off chats

If a conversation is disposable, Origin may add more ceremony than value. The product starts paying off when work crosses sessions, tools, people, or weeks.

A simple test: if the next agent should know it without you explaining it again, it probably belongs in Origin.

Next

Build from Source

Build the Origin daemon, CLI, MCP server, shared types, core crate, and plugin from the public repository.

Read next