Three editions.
One application underneath.

8 of these work in the build you can download today, and are unmarked below. The rest are marked in development: 1 is partly there already, and the row says which half runs. We would rather you knew that before paying than after.

• Chat with CortexThe full conversation surface, pointed at your own material rather than at a stranger’s.
• A Markdown vault you can searchNotes held as plain files on your disk, searched by keyword and by meaning at the same time, from the same index Cortex itself reads.
• Your choice of modelA local model through Ollama, or Anthropic, OpenAI and others on your own API key. No gate on either.
• It can write to your vault, and you approve each changeCortex can create, append to and move notes, and add a card, a task or a log line. In Secure mode each one waits on a card showing exactly which files it touches until you approve or decline it.
• Undo a write it madeEvery approved write is snapshotted first, so one control puts the touched files back to how they were before that turn.In developmentIt restores the files, not the conversation. The transcript still shows what was written.
• It remembers what you tell it toSay "remember that" and the fact is written to a durable profile that is read back into every later conversation. Say "from now on, do X" and the rule is appended to your own CORTEX.md, which Settings shows you.
• An audit log of every tool callWhat ran, when, and why, written beside the vault rather than into somebody else’s telemetry.
• The vault browserOpen, read and edit the whole thing from inside the app, or from any editor you already use.
• A model catalogue that says what each vendor does with your dataCapability scores next to a per-vendor data-handling label, so choosing a model is a decision you can make on the facts rather than on the brand.

1 of these works in the build you can download today, and is unmarked below. The rest are marked in development: 3 are partly there already, and the row says which half runs; 7 have not started, though your plan already grants them at no extra cost the day they ship. We would rather you knew that before paying than after.

• Business metricsRevenue, ad performance and channel stats pulled onto one timeline that updates itself.In developmentThe page ships and every figure currently reads empty.
• CanvasThe .canvas files in your vault, open beside the work.In developmentRead-only in this build. The app can open and read a canvas and cannot yet edit one.
• CalendarEvents the agents can read, so scheduled work knows what your week looks like.In developmentRead-only in this build. Events can be read and not yet added from the app.
• A sync serverPer-user accounts and folder-scoped permissions, so each person sees their own work and no more than that.In developmentThe server exists as a Rust service. No command in the shipping app reaches it yet.
• Role-scoped agentsFinance sees the accounting agent. Nobody sees more than their role allows.In development
• Team commsWire brings channels and email alongside the work instead of in a separate tab, with anything outbound waiting for a person rather than sending itself.In developmentNot in this build. Wire is out of the app entirely until team channels have a backend.
• A security reviewWhat the agents may reach, who may see what, and what leaves the building, checked before anything runs.In developmentThe in-app screen is a placeholder. The review itself is work we do with you, and that part is real.
• Deployment and supportThe whole thing built onto dedicated hardware inside your organisation, and kept running.
• More than one vault on one serverNamed vaults on the same deployment, so departments or clients stay separate without a second machine.In developmentPart of the sync server, which no shipping app command reaches yet.
• Clear the queue from anywhereThe approvals queue reachable over HTTP, so a pending action can be dealt with from another device rather than only from the desk it started at.In developmentWaiting on the approvals queue itself, which is not in this build.
• Backups on an intervalThe vault snapshotted on a schedule, without anybody remembering to do it.In developmentThe scheduler runs interval backups. Choosing where they land is part of a deployment rather than a setting in the app.