Keep what matters moving. A self-hosted, local-first personal AI runtime connecting models, agents, durable state, workflows, automations, and every surface you use. You own the data, keys, and environment.
Most chat products organize everything around one conversation. xopc gives long-running work several explicit, connected objects:
| Object | What it keeps | How it continues |
|---|---|---|
| Agent | Identity, responsibilities, model roles, tools, skills, and boundaries | Give each kind of work a deliberate capability envelope; all agents share user context |
| Session | Transcript, context, and run events | Resume from terminal, web, desktop, mobile, or a messenger |
| Project / Goal | Brief, status, blockers, next actions, and linked activity | See what needs attention without mining chat history |
| Note / Workspace | Quick inputs, attachments, and durable files | Collect source material and retain reusable context and artifacts |
| Workflow / Automation | Multi-agent execution, triggers, run state, and results | Execute complex work and run it again on time or on an event |
The point is not that “AI remembers everything automatically.” Important state has a clear home, execution and triggers are observable, and you can tell where to resume. Read The Continuous Work Model.
| Goal | Start here |
|---|---|
| I want a private AI assistant on my computer | First 5 Minutes |
| I want to understand how xopc stores state, executes work, and triggers follow-up | The Continuous Work Model |
| I want to organize long-running work with projects, goals, and notes | Projects, Goals, and Notes |
| I want to know how xopc differs from Codex, Claude Code, Qoder, and WorkBuddy | Comparison |
| I want the same assistant in Telegram, WeChat, or Feishu/Lark | Channels |
| I want scheduled reviews, reminders, and summaries | Automations |
| I want multiple agents for work, code, and personal contexts | Routing system |
| I want to extend xopc with tools, channels, or reusable skills | Skills and Extensions |