Skip to content

Agents and access

Any coding agent in a Thinair Terminal gets Thinair's tools. It can do anything you can, as you, and never asks.

Agents in a Terminal

Start Claude Code or Codex in a Thinair Terminal. It is told it runs in Thinair, and it gets Thinair's tool server, thinair-native, beside every MCP server you already use, with the thinair command first on its path. On a computer signed in to Thinair Cloud, Claude Code also gets thinair-cloud.

The tool server has six tools: search, describe, read, act, status and connect. Search finds what Thinair offers, describe says what a tool takes, read runs a tool that reads, and act runs one that changes something. The same six work from the shell:

thinair search --input '{"queries":["open terminal"]}'
thinair describe --input '{"ids":["control-plane.app.open"]}'
thinair act --input '{"tool":"control-plane.app.open","input":{"url":"https://example.com"}}'

control-plane.app.open opens a new Chrome window at that page and answers its tab, which the agent names in every later browser call, such as chrome.browser.snapshot or chrome.browser.click. Files take one command each:

thinair files put --input '{"from":"report.pdf","path":"/Reports/report.pdf"}'
thinair files open --input '{"path":"/Reports/report.pdf"}'
thinair files get --input '{"path":"/Reports/report.pdf","to":"report-copy.pdf"}'

put saves a file into Thinair Files, open shows it in a Window in the app for its kind, and get reads it back. To edit code that lives in another app's small computer, an agent uses a mirror.

Windows open beside the agent

Every Window an agent opens appears right beside the Window it works from, linked to it: the Links menu on either Window takes you to the other. One that lands out of your view has the canvas glide to it. While an agent works in an app, that app's Window bar shows its marker, such as Claude (Personal) · typing. An agent never gets a cursor.

Your agent is you

Your agent can do anything you can, as you, and never asks. It opens apps in any of your Profiles, uses their Files and keys, and closes and deletes what you could. Three things always take your own click: changing who can access what, spending real money, and turning on your camera or microphone. An agent that tries is refused, in words that say so.

In an organization, an Agent in a team Profile acts for whoever messaged it last, and stays inside that organization.

An agent inside a small computer of its own (a Terminal in a Profile) never reaches your computer directly. One in a Terminal on your computer itself runs as you there, and can drive Thinair's window; while it does, nothing it clicks there changes access, spends money or turns on your camera or microphone.

Show a dev server in Chrome

Chrome runs in a small computer of its own, so its localhost is its own. To show a dev server that runs on your computer, share its port into a Profile in Thinair Settings ▸ Ports, by its name and port. Then https://<name>.computer.thinair.localhost in that Profile's Chrome reaches it, with HTTP/2. Each share is listed there, with Remove. Agents can't share a port: they ask you to.