On your computer
Thinair needs no account to run. Its logs stay on your computer for about a week, and your Native Profiles and their Files never leave it. On a Mac, the app keeps your computer’s key in the Secure Enclave.
SECURITYHOW THINAIR KEEPS YOUR WORK APART
Thinair gives your agents as much freedom as it can, and keeps that freedom inside walls you can see: every app in a VM of its own, each project’s keys in a Profile, and access that only your own click can give.
AGENTS ASKTHINAIR / 01
Inside its Profile, an agent can do anything: use its keys, change its Files, open apps, and spend. To use an app in another Profile, or to let Chrome open a port of your computer, it asks.
The request appears over the agent’s Window. You choose how wide (only this app, or every one like it in that Profile) and how long (an hour to 90 days, or on your computer until you remove it), then Allow or Deny. After a Deny, the same request waits a minute before it can ask again.
Each Profile runs in Default or YOLO, set by whoever manages it. In Default, Thinair’s own tools (workspaces, the Trash, settings) are closed to its agents. In YOLO they open, but never reach your computer itself. Crossing into another Profile and sharing a port ask in every mode. Development, your computer’s own switch, is the only mode that lets agents drive Thinair’s window, and it is off until you turn it on.
~/shop $ claude
> Check the order page with my Personal sign-in.
● Chrome in Personal is outside this Profile. Asking you.
└ tools.access.request · waiting for your answer
Terminal 2 in Work wants to control Chrome in Personal
For 1 day. Remove it from Access sooner.
Only this ChromeEvery Chrome in PersonalDenyAllowTHE WHOLE OF ITTHINAIR / 02
Every security rule in Thinair is one of these eight, or something one of them stands on. Each is built and enforced today.
Each computer’s Thinair, your personal Thinair Cloud account, and each organization are separate, and nothing crosses between them. Your own computers reach your Cloud account as you, and with Thinair Pro they reach each other.
What runs directly on your computer, such as a Terminal there, the agent in it, or the thinair command, can do anything in your computer’s Thinair that you can: every Profile, app, and File.
An app in a VM gets in only through the Thinair Files its Profile reaches, the ports you share with it, and the package sources its app declares, such as npm for a Component. VMs cannot reach each other.
Inside its Profile an agent can do anything: use its keys, change its Files, open apps, delete, and spend. To enter another Profile it asks, and someone who manages that Profile answers. Every action traces back to the messages that started it and who sent them.
Allow and Deny, levels, Window grants, folders, remote access, and modes change only by a person’s own click. Agents never set access, by any tool, in any mode. They can only ask.
A Component runs its code in a VM with no network card and no Profile, so it holds no keys and reaches no website. It gets npm’s packages only through Thinair.
Each member has one level on each shared Profile: No Access, View, Operate, or Manage. A private Profile is its maker’s alone. An organization’s apps run only in Thinair VMs, never as a computer’s own apps.
Every part of Thinair is checked against its signed record each time it starts, and updates come from a signed feed. A part that does not match does not run.
PROFILESTHINAIR / 03
A Profile holds a project’s credentials (environment variables, key and config files, a coding agent’s sign-in) and the folders of Thinair Files its apps and agents reach, each read-only or read-write. An app you open in a Profile uses those, and reaches nothing else.
Every computer starts with a Personal Profile. A Native Profile stays on its computer; a Cloud Profile is shared by all your computers. Only the apps you open in a Profile receive its secret values.
WHERE THINGS ARE KEPTTHINAIR / 04
Thinair needs no account to run. Its logs stay on your computer for about a week, and your Native Profiles and their Files never leave it. On a Mac, the app keeps your computer’s key in the Secure Enclave.
Your signed-in computers connect straight to each other when they can, encrypted end to end, or else through Thinair’s encrypted relay. Turn remote access off from any of your computers, and every connection to that computer ends at once.
Each account’s and organization’s records are walled apart in Cloud’s database. Each Profile’s secrets are sealed under its own key, and a sleeping app’s memory is encrypted before it leaves its machine.
Every rule on this page is decided in one place in Thinair’s code. Each call is stamped with who made it, from how it came in and from Thinair’s own records, never from what the caller says about itself.
Before any change ships, Thinair’s own checks try every kind of caller against every route, in every mode, and stop the change if a rule breaks.
Yes. A Terminal that runs on the computer itself runs as you, and so does an agent in it: it can do anything in your computer’s Thinair, in every Profile. To keep an agent inside one Profile, open its Terminal in Native, a Linux VM of its own.
Your agents can then act with that sign-in, as you could, and that includes Thinair Cloud’s own website. Keep the sign-ins you want to keep from an agent in a Profile it does not work in.
The Agent shows each of its Profile’s secret values as ‹secret NAME› in everything it keeps and shows. Masking catches an accidental print, not a determined attempt to reveal a secret.
No. The app keeps its logs on your computer and sends Thinair nothing about how you use it. It asks Thinair’s public update feed for updates without signing in, and downloads Google Chrome from Google.
Thinair Cloud stores what you keep there: Files, Cloud Profiles, and Cloud apps with their disks. When two of your computers connect through Cloud, rather than directly or through Thinair’s relay, Cloud reads each message it passes on in order to deliver it. Your switcher shows which way each computer is reached.
Only a person, by their own click: you on your computer, or someone who manages the Profile the agent asks to enter. An Allow lasts as long as you choose, and you can remove it from Access at any time.
REPORT A PROBLEM
Tell us what you found and how to see it happen.
YOUR FIRST TASK
Open a Terminal and start Claude Code or Codex, or open the Agent, then give it a task you can check. What it opens lands right beside it.