What's built today
Phase 1 is the first release of Cora AI: this documentation site, the public website and the console. This page says what the console does today. Each point describes how it works now. Things that are not built yet are listed under Not built yet. Do not rely on them.
Built today
Section titled “Built today”Your organisation and its people
Section titled “Your organisation and its people”- Accounts and roles. Sign in with email and password. Org admins invite people by email and choose the roles they start in. Only an org admin can start someone as an org admin or in an admin role. See roles.
- Where data lives. Stored data is kept in Sydney. Model calls go to the Anthropic API, in the United States, and then to Amazon Bedrock on global profiles, which may run in any AWS region (D0031). See security and privacy.
- Missions. Each piece of work is a mission, with its own members, objectives, messages and documents. Cora is the mission coordinator. Only the members of a mission can see it.
Working with Cora
Section titled “Working with Cora”- The mission dialogue. One shared chat for each mission, where the team and Cora talk. Tag someone with @, and see new messages as they arrive. Cora posts cards in it: a document, a question, an approval, an email or a hero’s answer. See the mission dialogue.
- Your private chat with Cora. A chat for you alone. It is never stored: its turns live only in your browser while it is open (D0114, D0128). See your private chat with Cora.
- Polish with Cora. Ask Cora to tidy a message before you send it. See polishing a message.
- Files shared in the dialogue. Add a file to a message and it is kept with the mission, seen only by its members and served only as a download (D0548). See files shared in the dialogue.
- Documents. Cora writes documents for a mission, and every version is kept. The team opens them from the mission’s Artifacts tab. See documents.
- Cora’s memory. Cora keeps short notes for each mission, and only she writes them. The organisation has its own memory, which Cora reads at the start of every run. The organisation’s admins and the platform super admin change it, and Cora never writes it (D0855). See Cora’s memory.
- Heroes. A mission can become a hero that other missions call on for help. See the hero world.
Tools and connections
Section titled “Tools and connections”- MCP servers and connectors. An org admin can add hosted MCP servers, which are off until an org admin switches them on. A server that wants you to sign in, such as Notion, connects through the general sign-in flow on the service’s own page, so Cora never sees your password. Notion is not one of the ready-made connectors. See connecting an MCP server and connecting with the service’s sign-in.
- Approvals. Each group of tools is set to Off, Ask first or Allowed: by an org admin on an organisation connection, by the owner on a personal one. Ask first puts an approval card in the mission, and nothing happens until a person approves it (D0716).
- Web access and the browser. Cora can search and read the web, and drive a browser to look at a page. See web access and the browser.
- The mission vault. Keys for other services, which Cora uses by name without ever seeing the value. See the mission vault.
- The team sandbox. Each organisation has its own cloud sandbox and team folder, in Sydney, where Cora runs commands and keeps working files. See the team sandbox.
Running on its own
Section titled “Running on its own”- Schedules. Ask Cora to do something at a set time or on a repeat, no more often than every 15 minutes. A schedule pauses itself when nobody has written in the mission for 5 runs. See schedules.
- Mission metrics. Cora records a number, such as a score or a count, when she measures it in a piece of work and records it with her metrics tool,
record_metric. Nothing is recorded on its own. Mission details shows the trend. See mission metrics. - Email notices. Cora AI emails a person when something needs them, with a link to the console. See email from Cora.
Plans and payments
Section titled “Plans and payments”- Every plan has every feature (D0860). Plans differ only in AI usage, people, missions in the trial and support.
- The free trial lasts 14 days, with no card and a capped amount of AI usage. Each paid plan has a monthly cap, and Cora pauses when it is reached.
- Card payments go through Stripe, which holds the card details. See pricing and the free trial.
Maintenance jobs
Section titled “Maintenance jobs”Two jobs run on a timer. Neither calls a model (D0119). The work Cora does for a schedule is done by Cora herself, when the sweep wakes her.
| Job | When it runs | What it does |
|---|---|---|
| The sweep | Every 5 minutes | Expires approvals that waited too long, resends work whose first send failed, starts schedules that are due, ends trials past their 14 days or their AI usage, ends hero tasks past their deadline and runs that stopped, deletes files that were added but never sent, removes sign-in attempts that were never finished, and sets up each organisation’s sandbox and team folder. |
| The worker backstop | Every minute | Starts Cora’s worker when work is waiting and no worker is running. |
Not built yet
Section titled “Not built yet”These are not built yet. Do not rely on them.
- A daily digest email. Each notice is its own email for now.
- Single sign-on (signing in through your company’s own identity system) and Google sign-in (D0046).
- Choosing where your data is stored. Stored data is always in Sydney.
- A malware scan of shared files (D0562).
- A screen to read the audit trail. The trail is written, but there is no page in the console for it yet.
- Pooled credits shared across an organisation.
- Translation of messages for each reader, and meetings and deciding together (D0135).
- The SEO and GEO programme, which waits for its skill files (D0149).
After phase 1
Section titled “After phase 1”The later phases run in the order set in D0135: language first, then deciding together and meetings, then skill packs for digital marketing, then commercial readiness. Some of that work has already come forward: files shared in the dialogue, card payments and the first marketing connectors are built today.
Decisions: D0031, D0046, D0114, D0119, D0128, D0135, D0149, D0548, D0562, D0716, D0855, D0860.