The Workspace first, folder and bulk deletes, and fullscreen
Opening a brain now goes straight to the Workspace: the tree, the page and the backlinks. The separate landing page with a flat list of pages is gone; the tree is that list. In the tree, hover a folder to delete it with everything under it, or press Select to tick pages and folders and delete them together. Each confirmation lists what goes, asks you to type a word above ten pages, and reports anything it could not delete and why; version history is kept as ever. And the Workspace has a fullscreen button (or Ctrl or Cmd+Shift+F): the app chrome goes, the editor grows to the window, Esc brings it back, and the choice is remembered. The editor bar’s inactive “WYSIWYG” toggle has been removed until the live-preview editor it promised exists.
Your brain is the default, and the agent knows which one that is
With several brains on one connection, saving goes to your own brain unless you name another. Your brain is now marked as yours in the list your agent sees, so the rule no longer rests on a brain’s name. A team or client brain is written only when you say so, the agent confirms the first time in a conversation, and if nothing is marked it asks before writing. A brain you created yourself can be marked as yours from the command line. See using multiple brains.
Claude on the web and desktop can connect
Adding Cortex as a custom connector in Claude works from the workspace connection URL on any brain’s Connect page: Claude registers itself with Cortex’s sign-in service, each member signs in through the browser, and Claude reaches exactly the brains that member can. Before this, hosted clients that keep a secret were turned away at registration and Claude reported that it could not register. Claude Code and other native agents are unchanged. See connecting Claude.
Brains that grow with use, and a fuller Personal template
Your brain’s structure is whatever you actually use, not only what the template said. A page saved to a new folder creates that folder, and from now on your agent sees every folder that holds pages, described in the settings or not, beside the intended structure, so it files into the folders you have rather than inventing new ones. When nothing fits it creates one, names it plainly, and tells you so you can describe it in Settings. And the Personal template now has a home for companies and meetings alongside people, projects, daily notes, notes, ideas and reference, which is what a working brain fills up with. Existing brains keep their structure; the change applies to brains created from now on.
Manage a brain's members from the API
Onboarding can now be scripted. The public API lists a brain’s members and grants, changes or revokes access by email or user id, with the same rules as the Members page: Admin or Owner on the brain to manage it, workspace members only, one grant per person, and the last Owner stays. A service credential counts with the role it was issued, so a read-and-write credential cannot widen access. This is deliberately not something an agent can do from inside a conversation. See the API reference.
Ingest sources on the Settings page
Webhook sources now have a screen: Settings > Ingest sources on any brain you administer. Create a source with its label, authentication mode, guard rules, target folder, client pin and default filing skill, and copy the secret, the delivery URL, the headers and a ready-made
curl example from the one-time reveal panel. Edit a source’s rules and hints later without re-issuing the secret, and delete one by typing its label; what it already delivered stays put. The block is not the Sources archive in the side navigation, and says so. See receiving webhooks.Name the filing skill and skip the triage check
Every way into the inbox can now say what the item is: a “File as” choice on the web upload, a
skill field on the API and your agent’s upload tool, an X-Ingest-Skill header on webhooks, and a standing default on a webhook source. When you name the skill, the automatic filer skips its “is this worth filing” check for that item, spends nothing on it, and files with the skill you chose; the item’s log says so. Leave it unset and ambient captures are checked exactly as before. A name that is not a skill is refused with the list. See uploading files, the API reference and webhooks.Adding to a page, what changed, the graph tools, moves, and one search tool
Agents and integrations can now add to one part of a page instead of replacing it: a timeline line at the top of a section, a topic or todo under a heading, a note at the end, or a frontmatter key, with everything else on the page left exactly as it was. If the page changed under them, the edit is refused and they retry. A changes feed tells an agent what was created, updated or deleted since it last looked, with the inbox counts, so a morning briefing reads only what is new. Four graph and timeline tools join the connection: who links to a page, the pages within a few hops of it, a page’s timeline as dated entries, and a check that the names an agent is about to link actually exist (with near misses when they do not), plus a one-call way to add a dated timeline line. Moving or renaming a page now keeps the graph whole: every page that linked to the old name is rewritten, and a move never overwrites. And search is one tool with a mode: exact for names, ids and phrases, semantic for meaning, hybrid for both; the separate exact-search tool is retired. The operating manual (1.7.0) explains all of it. See the API reference.
Service credentials in the audit trail, and connection lifetimes
A page written with a service credential now shows up in the brain’s audit trail as that credential, by its id and label, instead of with no author. Nothing changes for the credential itself. And how long a connection lasts is now a stated rule rather than a library default: an agent stays connected while it is used at least once every 90 days, and is asked to approve again if it sits idle longer. See how connections work.
Where a document lives, and revisions
Every inbox item can now say where its document lives: a link to the original on SharePoint, OneDrive, Google Drive, Confluence or anywhere on the web, with the provider, its id and the version at the time. The source record shows the copy that was read beside a link to the live document, and page citations carry both. Your agent can send the file itself over its connection rather than a text conversion, so the archived original is the document. And when a newer version of a known document arrives it is kept as a revision: linked to the earlier item, which is marked superseded, with a line diff of what changed handed to whoever files it. Nothing is filed automatically because a document changed; the brain’s filing mode applies as for any new item.
Partitions: one brain, many clients
A brain can now be partitioned: one folder per client (or site, or matter) with a hub page, email domains and other names, managed on a new Clients page with CSV import. Nothing files under a client that does not exist, and every arriving item is matched to its client from the sender’s address, the attendee emails or the title, or waits as “needs a client” with one-click assignment that remembers the domain. Search, the page index and your agent’s tools narrow to one client. Archive keeps a finished client readable; purge, for owners and only after archiving, removes it with every version. The Client template ships partitioned, the API covers all of it, and a reference Granola pusher shows the transcript route end to end.
Review proposals, manual filing and the transcript format
The review queue grew up. Parked items now carry a full proposal: the drafted pages themselves, editable and acceptable in one click from the web, from your agent, or automatically at high confidence. You can also file any inbox item entirely by hand, no agent needed. Waiting items surface as badges in the app, as counts your agent sees, and as a morning email digest once they have waited a day.Meeting capture moved to a push-only transcript format: any tool that can POST a file can feed a brain, with attendee emails driving people-matching and safe re-delivery built in. The Granola polling source is retired; ingest URLs now accept a folder hint (
?path=).Documentation launch
The Cortex documentation is live: getting started, brains, capturing information, filing and recall, connecting your AI, teams, and account and security.