Before it exists

No. There is no download, no beta, no TestFlight and no link we are keeping from you. It runs on our own machines every day. That is how this site can be specific, and it is not the same as something you can install.

The waitlist is all there is to sign up for. Leave an email and you get one message when there is something to open. Everything below describes the day it opens, and some of it will have changed by then.

The parts described on this site work. Messages arrive, the Mac answers, files get written, connections hold. What is missing is the release itself, and the last round of decisions about plans and limits.

Some of this is still moving. Features will be added, a few cut or renamed, and the plan ladder is not final. It is a snapshot of a build in progress, not a spec sheet.

A Mac you own, that is usually on. There is no Windows or Linux build and none is planned, and nothing runs without a machine of your own. That is the design, not a limitation we mean to remove.

The version will matter in two places. Turning a recording into text needs macOS 26. So do the free on-device answers, which also need Apple Silicon. Below that Cory still works, but every message draws on the monthly allowance instead of being answered locally for nothing. Worth checking which Mac you have before the plans go live.

No. Your plan covers it. An earlier version of this page said otherwise, which was wrong, and is worth correcting out loud.

Whoever you decide. As the owner of the Mac you get everything: files, commands, your full message history.

Everyone else in a conversation gets a deliberately smaller version. They can ask questions and get answers in the thread. They cannot run commands, cannot reach your files, never receive one as an attachment, and are handed none of your connected services at all. Your friends can ask Cory things. They cannot touch your computer.

If somebody asks for something only you can authorise, Cory does not refuse quietly. It holds the request and asks you in your own messages to yourself, and waits there until you reply. So their question reaches you, and nothing happens unless you answer. If it has nowhere to ask, it declines rather than guessing.

Over iMessage, nothing you send touches our servers. The request leaves your Mac and the answer comes back to the same thread. The one time something goes through us is when Cory reaches an app you connected, such as Notion or Gmail: that request passes through our relay and through Composio, which executes it, and neither keeps it.

Over WhatsApp it is different, and worth knowing before you choose that route. A message passes through Meta and then through us for a moment on the way to your Mac, and we delete it as soon as your Mac answers. The work still happens on your machine; the words take a longer road to get there.

Either way, replies carry a little recent conversation for context. Messages other people sent in the thread go along with your request, even though they were never addressed to Cory.

Yes, if you ask it to. It reads, writes, moves and deletes as your user account, with the reach that account has. Nothing is confined to a project folder and nothing is copied into a sandbox first. That reach is the point, and the reason for the next paragraph.

In the build as it stands, nothing sits between the sentence and the action. A confirmation step for destructive changes is on the list and we would rather ship it before the release than after. Either way, keep backups.

It sits in a table until there is something to announce, and then you get one message. That is all from the waitlist: no sequence, and it goes to nobody else. The footer has a separate signup for occasional notes, if you want them. Reply to anything asking to be removed and you will be.