THE WORKSPACE FOR YOUR AGENTS
Every app is a Window on one canvas: Terminals, Google Chrome, your Files, live components and films written as code. Each runs on your computer, in a Linux VM of its own, or in Thinair Cloud. Start Claude Code or Codex in a Terminal, and it opens and uses the same Windows you do, right beside you.
Free on your computer, no account neededSign in
Start Claude Code in a Terminal and give it a task.
It opens what it needs right beside it.
Use the same Windows to make changes yourself.
Kind TypeScript Size 4 KB Modified Just now Where ~/create/sprint/src
01 / 05Right-click the canvas: Apps, Terminal, Dan's Mac Studio. A Terminal on your computer runs as you.
Start an agent. Open a Terminal and start Claude Code in it.
Illustrated walkthrough.
The apps, places and requests are the product’s own.
Type to the agent in its Terminal, or use its Chrome yourself. You and your agents use the same Windows, and it asks before it reaches further.
PROFILES AND PLACESTHINAIR / 02
A Profile holds the sign-ins, keys and folders of Thinair Files its apps and agents may use. Every app you open in it reaches those, and nothing else.
You choose where each app runs: on your computer itself, in a Linux VM of its own on it, or in Thinair Cloud. A VM never reaches your computer.
Sign-ins and API keys in the Profile. The folders of Thinair Files it may read or write.
Keys and folders for the storefront’s code, tests and ticket work.
/profile/sprintRead and write. Made for it as it is made./Sprint/specsRead and write/Brand/assetsRead onlyApps, then the app, then the place, then the Profile. You choose; Thinair never picks for you.
AppsPick an app and a place, then open it. Its Window lands where you right-clicked, and its app starts inside.
A Cloud app keeps running while your computer sleeps, and sleeps itself when idle.
$ bun test✓ 214 passed$ claude> keep going on the next ticketIt leaves its machine whole for Cloud’s encrypted store, so the machine can turn off.
It wakes on your next use, on any machine with room, as it was.
Your computer can sleep. The Terminal in Cloud keeps running.
Cloud apps run on prepaid credit while awake; asleep they cost nothing.
Profile Sprint: home folder /profile/sprint. Choose an app and a place, then open it.
Bring the agent you use. In Thinair it works with Thinair’s tools, as its Profile, in the place you chose, and it asks before it reaches beyond them.
Claude Code, Codex or any agent in a Thinair Terminal, with Thinair’s tools from the start. Or Thinair’s own Agent, in a VM of its own.
Your own subscription, signed in per Profile: a Profile’s Claude sign-in is its own, never a copy of your computer’s. Your provider’s limits apply.
Six tools reach every app, Window and File it may use. What it opens lands right beside it, and every call is recorded.
It acts as its Profile, never as you. Inside it, it can do anything its keys and folders allow, in the mode you set: Default or YOLO.
On your computer itself, in a Linux VM of its own, or in Thinair Cloud. A VM never reaches your computer.
To use another Profile’s app or a port of your computer, it asks, in every mode. Only your click allows it, and every action traces back to who sent it.
WHERE IT RUNSTHINAIR / 04
Each app runs where you choose: on your computer itself, in a Linux VM of its own on it, or in Thinair Cloud. Reach your other computers with Thinair Pro, and your Cloud workspaces from any browser.
Your hardware. A Linux VM for each app.
~/launch-page main
❯ bun run dev
▲ Next.js
Local localhost:3000
✓ Ready in 842ms
GET / 200 38ms
GET /api/status 200
▍
Web development
Analyze this week’s sales.
I opened your sales sheet in Chrome, beside this Window. I’m charting the totals now.
Drafting the report
A weekly sales report
2 Linux VMs on your computer
Apps that keep running while your computer sleeps.
~/storefront main
❯ claude “run the checkout tests overnight”
● Running bun test in this Terminal
✓ 128 tests passed
● Opening the report in Chrome
Report ready beside this Window.
Waiting for your next message
Tests that run overnight
SPRINT Checkout
Pace Runner 01 · Size 10
Subtotal $148
✓ Add to bag passed
✓ Shipping form passed
✓ Pay with a test card passed
Signed in, in the Engineering Profile.
Checking the storefront
2 Linux VMs in Thinair Cloud
Three parts: the app, the Profile it runs as, and where it runs. A wall around each.
A Terminal, Chrome, the File Explorer, Preview, a Component, a Video or the Agent. Each opens as a Window on the canvas.
Your agents’ sign-ins, API keys, browser sign-ins, and the folders of Thinair Files its apps reach. Nothing else.
On your computer itself, in a Linux VM of its own on your computer (Native), or in Thinair Cloud. A VM never reaches your computer.
Remote access is on by default and keeps your desktop awake on mains power. The link goes straight between your computers, end-to-end encrypted, or through Thinair’s relay when it can’t.
The same canvas, for your Cloud workspaces, in any browser.
You choose where each app runs: Apps, then the app, then the place, then the Profile. On your computer, each app in Native gets a Linux VM of its own.
HOW YOU WORKTHINAIR / 05
Arrange apps as Windows on a canvas. From your own terminal or agent, the thinair command and its MCP tools open apps, drive Terminals and Chrome, and work with your Files.
The page is open in Chrome. Beside it: a picture, a video in Preview, and two Components to explore.
An experiment in light,
material, and motion.
orbit main ❯ bun dev
VITE ready in 184 ms
› Local: http://localhost:3000
› press h + enter to show help
orbit-render.webp Pasted on the canvasClaude Code or Codex in a Terminal, working in the same Windows you do.
In a Thinair Terminal the thinair command acts for you: open Chrome at a page, show a File beside the Terminal, or call any tool your agent can.
Example output. In a Thinair Terminal, thinair is already there.~/create/sprint
❯thinair act --input '{"tool":"tools.browser.open","input":{"url":"https://example.com"}}'
{
"answer": "opened",
"profile": "Personal",
"placed": { "words": "right of your Terminal" }
}
Excerpt · a new Chrome Window, beside this Terminal❯
Start Claude Code or Codex in a Thinair Terminal and it is already connected. Anywhere else, add thinair mcp as an MCP server beside the ones you have.
Your agent discovers the tools
Thinair makes available to it.
ONE PLACE FOR THE WHOLE PROCESS.Illustrated workspace. Try the Components and switch views.
Download Thinair for macOS (Apple silicon, macOS 26 or later). It is free and works on its own, with no account. Sign up for Thinair Cloud to run apps in Cloud and reach your other computers with Thinair Pro. Your Cloud workspaces open in any browser too. Thinair for Windows is coming.
One desktop app that turns your computer into a workspace for you and your agents: a canvas where every app is a Window. Each app runs where you choose, on your computer, in a Linux VM of its own, or in Thinair Cloud, and reaches only the keys and Files of the Profile it runs in. Your agents use the same Windows you do.
Terminals, Google Chrome, the File Explorer, Preview (pictures, PDFs, videos, Mermaid diagrams), live React Components, Videos written as code, and Thinair’s own Agent. Chrome runs in a Linux VM of its own for each Profile and stays signed in.
Open a Terminal and start Claude Code or Codex in it: it gets Thinair’s tools by itself and can open Chrome, Terminals, apps and Files right beside it. Or open the Agent (Apps, Agent, Native, a Profile), Thinair’s own agent, which runs Claude Code in a VM of its own on that Profile’s Claude sign-in.
Whatever the apps do: write code and run it in Terminals, test and research in Chrome with full control of the browser, write films as code in a Video and export them to MP4, build React interfaces in a Component, and make PDFs and diagrams that Preview redraws each time they save.
Keys, sign-ins and folders. A Profile carries its environment variables and key files, its coding agents’ sign-ins, its Chrome’s sign-ins, and the folders of Thinair Files its apps may read or write. Every app you open in it uses those and reaches nothing else, and each Profile’s values are sealed under a key of its own.
Only by asking. Inside its Profile an agent can do anything its keys allow. To use another Profile’s app, or let Chrome open a port of your computer, it asks over its Window, and only your own click allows it, for as long as you pick. Agents never set access themselves.
No. The thinair command and its MCP server open apps, drive Terminals and Chrome, and work with Files from your own terminal or agent. In a Thinair Terminal, Claude Code and Codex are connected already.
Yes. Their Terminals, Chrome and Files are Windows on your canvas. Use them yourself, type to the agent in its Terminal, or take over at any point. Each Window an agent works on shows its marker on the bar.
Yes. Claude Code and Codex use your own subscriptions, and a Profile’s Claude sign-in is its own, never a copy of your computer’s. Thinair’s Agent uses that sign-in. Run any other agent in a Terminal. Thinair does not bill model use, and your provider’s limits still apply.
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.
