Profiles
A project’s keys, sign-ins and folders, sealed under the Profile’s own key. Every app and agent in it uses them, and reaches nothing else.
FOR OPERATIONS TEAMS
Sign in to your CRM, email, and spreadsheets once, in a Profile’s Chrome.
Thinair’s Agent works there, with the keys you saved in that Profile.
You review the reports and drafts it makes, in the same Windows.
Open Thinair’s Agent in the Profile that holds your sign-ins. Ask for the work you do every week, then check what it made.
Right-click the canvas and pick the Agent. Its Window opens and asks where it runs and as whom: ThinairOS, as Revenue Ops. It runs in a small computer of its own, with that Profile’s sign-ins. If the Profile has no Claude sign-in yet, it asks you for one first.
Ask in plain words. It opens what it needs in the Profile’s Chrome, beside its own Window, and masks the Profile’s keys in everything it shows.
Its marker on a Window’s bar shows where it works. Check the result, edit it, or use the same Chrome yourself: it stays signed in.
Illustrative pipeline review with made-up accounts. Claude Code or Codex in a Thinair Terminal in the same Profile works the same way. One-click connections to services and scheduled runs are coming; for now, you ask each time.
Start your first taskSet it up once.
Give each teammate a level.
A Profile holds a project’s keys, sign-ins and folders, sealed under its own key. In an organization, each member gets No Access, View, Operate or Manage on each shared Profile, and every app opened there uses it. Organizations: Available now
One person sets it up.
› Only Manage gives a levelIt lasts until taken back One Profile. Each person’s own level.
A level says what each member, and their agents, may do there.
To the agent in a Cloud Terminal: Explain last month’s revenue decline.
August 2026 · Monthly report
Revenue change by customer segment
rev_change_last_month(segment)One Profile. Each person’s own level.
The real pieces behind the work.
Each one is a thing in Thinair today.
A project’s keys, sign-ins and folders, sealed under the Profile’s own key. Every app and agent in it uses them, and reaches nothing else.
Your Files, with every version kept and a Trash that holds them for 30 days. A Profile reaches only the folders it is given, read-only or read-write.
One React component in a .component File, live on the canvas as an agent edits it. Its small computer has no network card and gets no Profile’s secrets.
An agent asks before it uses another Profile’s app or a port of your computer. Only someone who manages that Profile answers, with their own click.
Every call an agent makes leaves an audit row, and says who sent it the work.
Thinair’s own agent: one .agent File in a Profile, on that Profile’s Claude sign-in. Everyone viewing its Window sees each turn as it streams, secrets masked.
Save the prompts, scripts and reviewed results that worked as Files in the Profile’s home folder. Everyone who reaches the Profile finds them there, every version kept.
Thinair engineers help you set up your Profiles, sign in to the tools your team uses, and run your first task with the Agent.
Bring us the spreadsheet, the handoff, or the recurring process that takes too much of your team’s time.
Map the tools, decisions, and review steps with the people doing the job.
Decide which keys and folders of Thinair Files each Profile holds, and sign in to your CRM and email once in its Chrome. For a team on Thinair Cloud, choose who gets which level on each shared Profile.
Run real work together. Measure time spent and output quality, then refine the setup.