An illustrated SPRINT project on Thinair’s canvas: Codex and Claude Code in Terminals, the shoe storefront in Chrome in a small computer of its own, a product card drawn live by a Component, and a system architecture diagram shown flat by Preview.
CodexDan's Mac StudioAccess
• Explored
└ Read size-selector.tsx
• Edited src/size-selector.tsx (+3 −1)
24 − bag.add({ product });
24 + if (!size) return;
25 + bag.add({ product, size });
26 + setBagOpen(true);
• Ran pnpm test -- storefront
└ 4 passed · 0 failed
Worked for 18s
Size selection is ready. Choose your size, then add the Pace 01 to your bag.
›Keep the selected size in the bag
gpt-6-astra · xhigh~/sprint/storefront
Claude CodeDan's Mac StudioAccess
● Read(src/size-selector.tsx)
└ Read 88 lines
● Update(src/size-selector.tsx)
└ Added the selected size to the bag
The bag shows the Pace 01, your selected size, and the correct quantity.
Run Codex and Claude Code beside your terminal and browser.
Keep your agent, files, terminal, and browser in one workspace.
Start Claude Code or Codex in a Thinair Terminal and it opens Chrome, Terminals and Files right beside it. Each app runs on your computer or in ThinairOS, a small Linux computer of its own.
Free on your computer, no account needed · macOS 26 or later · Apple silicon · Windows coming
YOUR DEVELOPMENT TOOLS01
Agents, terminals, browsers, and files on one canvas.
Start Claude Code or Codex in a Thinair Terminal and it can open Chrome, Terminals and Files right beside it. Give direction, inspect the work, and keep the whole project in view.
01 / 04
Plan
Start with a conversation about the Sprint shopping flow.
Codex · storefrontDan's Mac StudioAccess
OpenAI Codex ~/sprint/storefront
› Let’s plan size selection and Add to Bag for the Pace 01. Keep the selected size all the way through.
› Give your agent direction
Codex · highspr-214/product-sizing
100%
Talk it through. Put the plan on the canvas.
Discuss the approach with Codex in a Thinair Terminal. It puts the architecture and a PDF of the plan beside the conversation, and Preview redraws the plan each time the agent saves it.
Looping product tour with example tasks. Plan, execute, test, and orchestrate.
DIAGRAMS AND PROTOTYPES02
Review diagrams and prototypes before coding.
Your agent can put a diagram or a PDF of the plan beside its Terminal, and build live React Components on the canvas: mockups, charts, working prototypes. Work through the idea together before the agent starts building.
LIVE ON THE CANVAS
SPRINT / PLANNING A SHARED PLACE TO THINK
Codex · plan with meDan's Mac StudioAccess
›Before we build, show me how the storefront, inventory, and bag fit together.
•I’ll draw the boundaries as a diagram and put the plan beside it as a PDF.
•Explored
└ Read README.md, package.json
•Editeddocs/sprint-architecture.svg
4+</g>
5+<g id="server">
6+<CommerceApi /> <Inventory />
•Ranthinair files put /Sprint/sprint-architecture.svg
└ Saved into Thinair Files
•Ranthinair files open /Sprint/sprint-architecture.svg
└ Preview shows it beside this Terminal
•Ranthinair files open /Sprint/SPR-214 plan.pdf
└ Opened beside the diagram
Worked for 28s
•The diagram and the plan are beside us. Review the boundaries before we build.
› Ask Codex to do anything
tab to queue message82% context left
gpt-6-astra high·~/sprint·Plan ready
sprint-architecture.svg
SPR-214 plan.pdfLinks 1Access
SPRINT · SPR-214
The choice should carry through.
Select a size. Add that exact variant to the bag.
Approach
Inventory owns availability. The bag keeps the variant the shopper chose.
Implementation
Make available sizes clear.
Keep sold-out sizes disabled.
Preserve the selection in the bag.
Browser checks
□ Size 12 stays sold out.
Conversation → a File → live on the canvasSPRINT / EXAMPLE STUDIES
See the decisions before they become code.
Map the system, name the boundaries, and work through the edge cases together. Preview redraws the diagram and the plan each time your agent saves them, and they stay beside the work as it builds.
01
Make the thinking visible. Diagrams and plans give you something concrete to question.
02
Try it before you commit. A working prototype makes the missing detail easier to find.
03
Keep the context in place. Your agent, the plan, and the result stay together on the canvas.
BROWSER TESTING03
Your agent tests. You keep working.
Chrome runs in a small computer of its own, one per Profile, as a Window on your canvas. Your agent clicks, types, and tests your app in its own tab there. Your computer’s browser, cursor, and desktop stay yours.
01 / YOUR COMPUTERYour work carries on.
Sprint / Launch notes
FRIDAY / PRODUCT NOTES
One thing at a time.
The launch should feel simple.
Clear sizing. A quiet checkout. A little room to breathe.
Keep the focus here.
You
Still yours. The agent’s input stays in its browser.
02 / CHROME · PERSONAL, IN ITS OWN LINUX COMPUTER A Window on your canvas
Codex · in a Terminal beside itTest the size selector and Add to Bag.
READY
SPRINT / Pace 01ThinairOSPersonalLinks 1Access
SPRINT · Pace 01+
‹ › ↻localhost:3000/products/pace-01
SPRINT®
New releasesRunningEveryday
FOR THE EVERYDAY ATHLETE. GO FIND YOUR NEXT.
SPRINT RUNNING / 001
MAKE YOUR MOVE.Built for your everyday miles.
01 — 03
JUST LANDED
Pace 01
$145
Everyday running shoe
Light on your feet. Ready for everything.
Chalk / Lime
Free shipping. Easy returns.
Your bag is empty.
·Open https://localhost:3000·Select US 9·Add to Bag·Verify size, quantity, and subtotal
Your cursor stays yours. The agent works in its own tab.
Your agent drives Chrome through Thinair’s browser tools, in the tab it opened. Its work shows as a marker on the Window’s bar, never as a pointer.
Scripted examples using Sprint. Browser actions are illustrated here; the planning prototypes are interactive.
EACH APP GETS ITS OWN COMPUTER04
Run agents in Linux on your computer or in Cloud.
Each app gets its own small Linux computer, on yours or in Thinair Cloud. Run your agents there, or in a Terminal on your computer, and let Cloud keep working when your laptop sleeps.
Open a Terminal or Chrome in Thinair Cloud, each in a small computer of its own in a Cloud Profile, and run Codex there. A Cloud app idle for 30 minutes sleeps with its memory and scrollback kept, costs nothing asleep, and wakes as it was.
Codex · storefrontCloudPersonalAccess
personal@thinair-cloud:~/storefront$ codex• Edited src/checkout.tsx (+12 −3)• Ran pnpm test -- checkout 6 passed› Working on the next task
THE SAME TERMINAL, ON YOUR CANVAS
esc◌☼▦⌕◐◖◂▷▸◀◁▷◉
`1234567890−=delete
tabQWERTYUIOP[]\
capsASDFGHJKL;'return
shiftZXCVBNM,./shift
fn⌃⌥⌘⌘⌥◂▴▸
Thinair⌁ ▰
SPRINT / WORKSPACE Terminal · Cloud · Personal
Laptop awake. The Cloud Terminal is a Window on your canvas.
A small Linux computer for each app. Right on your computer.
Each app you open in ThinairOS runs in a small Linux computer of its own, booting Thinair’s own kernel. A Terminal there comes with git, ripgrep and curl, keeps its data disk, and takes whatever else you install. None reaches your computer, and one reaches another only through a port you share.
YOUR COMPUTERThinairOS: a small computer per app
TerminalPersonal
git · ripgrep · curl
ChromePersonal
localhost:3000, shared by you
ComponentNO PROFILE
No network card · npm through Thinair
It never reaches your computer. Only Thinair Files, ports you share, and the package sources its app declares get in.
Bring your accounts and credentials through a Profile. Every app you open in it reaches only that Profile’s keys and folders, and an agent working there asks you before it uses another Profile.
Yes. Use Thinair as the working environment around your project: agents, Terminals, Chrome, Files, and diagrams together on a workspace. Use the same apps yourself and work alongside your agents.
Can I bring my existing repository and agent?
Yes. Open a Terminal where your repository is: on your computer, or clone it into a Terminal in ThinairOS, a small Linux computer of its own. Start Claude Code or Codex there and it gets Thinair’s tools by itself, beside the MCP servers you already use; any other agent can run the thinair command. Use your own subscription or API key. Your provider’s usage limits still apply.
Will browser testing take over my computer?
No. Your agent drives Chrome running in a small computer of its own, shown as a Window on your canvas. Its clicks and typing stay in the tab it opened, so you keep using your computer’s own browser and desktop. Run the development server on your computer, and the first time, Thinair asks you to share its port with Chrome; then your agent opens https://localhost:3000 there.
Can agents show me the plan before they build?
Yes. Your agent can put a diagram or a PDF of the plan beside its Terminal, and Preview redraws it each time the agent saves it. It can also build a live React Component on the canvas, from shadcn parts and Tailwind, so you can try the interface first. The Component is saved as a .component File you can open again.
Can my agents keep working when I close my laptop?
Yes, two ways. Thinair Cloud runs a Terminal or Chrome in a small computer of its own there, so your laptop can sleep; a Cloud app idle for 30 minutes sleeps too, with everything kept, and wakes as it was. With Thinair Pro, your other computers reach each other, and a desktop with remote access on stays awake on mains power, so you can keep working in its workspace from your laptop. Apps in ThinairOS use your computer’s hardware and need it awake.
What is the local sandbox?
Open an app in ThinairOS and Thinair runs it in a small Linux computer of its own inside yours, booting Thinair’s own kernel, with memory given as it is used. A Terminal there comes with git, ripgrep and curl, and keeps its data disk across restarts. It never reaches your computer: only Thinair Files, ports you share, and the package sources its app declares get in. Profiles supply your accounts and credentials separately.
Can I work through CLI, MCP, or API?
Yes. The thinair command and Thinair’s MCP server let you and your agents open apps, drive Chrome and Terminals, and show Files on the canvas. Claude Code and Codex in a Thinair Terminal are connected already. Every call is recorded.
YOUR NEXT PROJECT
Start a task with Codex or Claude Code.
Open a Terminal, start Codex or Claude Code in your repository, and ask for a change you can test and review.