MMyst
How it thinksEvidenceTrustPlans
Log inCreate your workspace
Personal AI operating system

Your work, your machine, your model.

Myst keeps your projects, notes and history in one workspace you own, and decides what any model is allowed to see. It never writes a file, and never reaches for the cloud, without telling you.

Create your workspaceSee how it thinks

How Myst thinks

Myst is not a model with a chat box in front of it. It is the layer that decides what a model gets to see — and keeps what it knows in your workspace, not in a provider's.

MystcontextChatProjectsKnowledgeSkillsAgentsModelsApprovals
  1. Chat

    Where you ask. Every answer names the sources it used and the model that produced it.

  2. Projects

    Your real repositories and their Git state — read as they are on disk, not as a snapshot from last week.

  3. Knowledge

    Your notes and vault, searched alongside the code rather than in a separate app.

  4. Skills

    Named procedures Myst can follow. You can read one before it runs, because it is a file, not a prompt nobody can see.

  5. Agents

    Scoped workers for longer jobs. Each is given a narrow slice of the above, never the whole workspace.

  6. Models

    Providers, not memories. A model is handed the context Myst assembled; changing model changes who answers, not what is known.

  7. Approvals

    The gate before anything is written. Myst drafts; you approve; only then does a file change.

What it looks like when Myst has nothing to give you

Any product can show you its good day. These are the three moments where a system that wanted to look good would round up — and what Myst does instead.

A worker that is off

Example
surface-pro
offline
last seen
6 hours ago
models
unknown while offline

Requests that needed this worker are waiting. Nothing was sent to a cloud provider to cover for it.

Off is not slow, and it is not empty. Myst says which machine, when it was last seen, and what it means for you right now — then keeps working without it.

An answer, with its sources

Example

The balance update is not atomic — economy_service.py reads and writes in two statements, so two concurrent purchases can both succeed.

A personal operating system, not another chat app

Five parts, in the order you meet them on an ordinary day.

  1. Daily brief

    One page that knows what happened while you were away

    What moved in your projects, what is waiting on you, what failed overnight. Assembled from your own workspace — not a feed, and not a summary of the internet.

  2. Second brain

    Your notes, finally searchable next to your code

    The vault you already keep, read in place. Ask a question and the answer can cite a note from two years ago and the file it describes, in the same breath.

  3. Projects

    Real repositories, read as they are right now

    Branch, diff, history and the actual files on disk. Myst does not work from a stale copy it indexed once, and it does not write to any of it without asking.

Read-only until you say otherwise

Three promises the software keeps mechanically, and one setting that decides how much of your work is allowed to leave the building.

The privacy boundary is a boundary

Your projects, vault and workspace live on your machine. When local compute is unavailable, Myst tells you — it does not quietly send private context to a cloud provider to cover the gap.

You control every worker

Each compute worker is a machine you registered, and you can pause or remove it at any time. A worker that is offline is reported offline, never as slow or empty.

Nothing is written without approval

Myst drafts a change and shows the exact diff. Approving and applying are separate steps, a rejected proposal is not the same thing as a failed one, and Myst never commits or pushes on its own.

Choose how much leaves your machine

Two settings, changeable at any time: the routing policy in your account preferences, and the cloud-fallback switch that decides whether local-first is allowed to reach out at all.

What each routing mode does with your requests and your data.
BehaviourLocal-onlyLocal-firstCloud-enabled

Usage that stays visible

Every request is metered from an append-only usage ledger — see your balance, what you used today, and what a heavier request will cost before you send it. Credits are an internal quota, not a subscription charge; there's no payment provider in the loop.

Standard

Default

1x credit rate

Standard credit cost — 1 credit per token unit, no markup.

MMyst

A personal AI operating system. Your projects and notes stay on your machine unless you choose a cloud model — and Myst tells you every time one answers.

Served from ai.serenity.rip

Account

  • Log in
  • Create a workspace
  • Forgot your password

Support

  • Open a support ticket (sign in first)
  • Privacy and data policy
  • What Myst does with your files

© 2026 Myst. Independently built and operated.

Self-hosted on a single server. No advertising, no third-party analytics, no resale of anything you store here.

  • economy_service.py:114–131
  • vault / bot-architecture.md
  • local · qwen2.5-coder
    Every answer names what it read and which model produced it. An answer with nothing behind it says so rather than sounding confident.

    A change that has not happened yet

    Example

    Apply fix to economy_service.py?

    1 file. Nothing changes until you confirm.

    - balance += amount+ balance = await update_balance_atomic(user_id, amount)
    RejectApprove and apply
    Myst drafts, you approve. The diff is the whole proposal — no file is touched before you confirm, and Myst never commits or pushes on its own.
  • Agents

    Long jobs that keep going without you watching

    Give one a task and a narrow slice of the workspace. It reports what it did and what it wants to change; changing anything still needs you.

  • Compute workers

    The spare machine in the other room, doing the work

    A desktop, a laptop, a friend's PC with a good graphics card. Myst hands work to whichever is awake, and tells you which one answered. When none are, it says so.

  • A local model handles the requestyesyesyes
    A cloud provider is ever contactednoOnly when the local model is unreachable, and only if you turned fallback onyes
    Anything leaves your machinenoOnly the requests that fall backyes
    What happens when the local model is downThe request fails and says soFalls back, or fails if you did not allow itA cloud provider answers
    Routing policy this matchesmanual / privacy_firstlocal_firstfastest / cheapest / best_quality / custom