The choice should carry through.
Select a size. Add that exact variant to the bag. Show what happened.
- Make available sizes clear.
- Keep sold-out sizes disabled.
- Preserve the selection in the bag.
An illustrated SPRINT project: Codex and Claude terminals, a shoe storefront, a reusable product-card Component saved to a shadcn-compatible registry, and a system architecture diagram in one development environment.
FOR DEVELOPERS
Your terminal, agents, mockups, and running app. All in one workspace.
Design components right beside your code.
Build with your agents and save the result to your shadcn-compatible registry.
In your browser or on your Mac.
A PLACE FOR THE WHOLE PROJECT01
Move between agent terminals, running apps, and architecture on one canvas. Give direction, inspect the work, and keep the whole project in view.
Start with a conversation about the Sprint shopping flow.
Discuss the approach with your terminal agent. The architecture and a rendered Markdown plan appear beside the conversation.
GIVE THE IDEA SOMEWHERE TO GO02
Agents can render React directly on the canvas: architecture, mockups, working prototypes, and Three.js scenes. Work through the idea together before the agent starts building.
›Before we build, show me how the storefront, inventory, and bag fit together.
•I’ll make the boundaries visible and put the implementation plan beside the diagram.
4+<Storefront />5+<Inventory />6+<ShoppingBag />
•The architecture and Markdown plan are on the canvas. Review the boundaries before we build.
Select a size. Add that exact variant to the bag. Show what happened.
Map the system, name the boundaries, and work through the edge cases together. The plan stays beside the work as your agent builds.
Make the thinking visible. Diagrams and rendered plans give you something concrete to question.
Try it before you commit. A working prototype makes the missing detail easier to find.
Keep the context in place. Your agent, the plan, and the result stay together on the canvas.
ROOM FOR AGENTS. ROOM FOR YOU.03
Agents run browsers inside Linux VMs, rendered into the canvas. They click, type, and test your app there. Your Mac’s browser, cursor, and desktop stay yours.
The launch should feel simple.
Clear sizing. A quiet checkout.
A little room to breathe.
Still yours. The agent’s input stays in its browser.
SPRINT RUNNING / 001Everyday running shoe
Light on your feet. Ready for everything.
Free shipping. Easy returns.
Your bag is empty.
Codex and Claude Code can share requests, context, and results through Thinair. Agents launched through Agent Board connect automatically.
Give them direction. Let them handle the handoffs, ask each other questions, and bring the result back to you.
Scripted examples using Sprint. Browser actions and agent messages are illustrated here; the planning prototypes are interactive.
THE WORK GETS ITS OWN MACHINE04
Start with a prebuilt Machine, with your tools and dependencies ready. Run a Linux VM locally on your Mac, or let a Cloud Machine keep working when your laptop sleeps.
Launch agents on a prepared Cloud Machine and let it carry the work. No caffeinate command. No lid-left-open workaround. Come back to the canvas when you’re ready.
Give your agents their own Linux VM, prebuilt with the tools and dependencies they need. The repeatable setup you like about containers, with a complete Machine built for agent development.
❯ pnpm dev✓ Ready at localhost:3000Watching for file changes▌Reuse the software setup with a Machine Definition. Bring your accounts and credentials through a Profile.
See how to get started ↗Yes. Use Thinair as the working environment around your project: agents, terminals, browsers, files, and visual artifacts together. Focus in a Workbench with panes and tabs, or spread the work across a Workspace. Use the tools yourself and work alongside your agents.
Yes. Make your repository available on the Machine where you want to work, then use it as your agent’s working directory. Use Codex or Claude Code with a supported subscription or API key, or run other installed agents through Terminal. Your provider’s usage limits still apply.
Your agent targets a browser running inside a Linux Machine, and that browser is rendered into your canvas. Its clicks and typing stay there, so you can keep using your Mac’s own browser and desktop. Run the development server on the agent’s Machine and inspect the running app alongside its work.
Yes. Agents can render React directly on the canvas for architecture diagrams, mockups, interactive prototypes, and Three.js studies. Review a rendered Markdown plan beside the conversation, try the interface, and refine the idea together. Save reusable React source to your shadcn-compatible component registry.
Yes. Thinair’s Agent Board gives them named addresses and a shared messaging channel for requests, replies, and acknowledgments. Agents launched through Agent Board connect automatically. Existing supported terminal sessions can join by name. They can coordinate across Machines without you relaying each message.
Yes, when they run on a Cloud Machine. The work runs in the Cloud independently of your Mac, so the laptop can sleep. Local Linux VMs use your Mac’s hardware and depend on it staying awake. Choose the Machine that fits the work.
Thinair Native runs full Linux VMs on your Mac. Each Machine has its own Linux kernel, memory, and Machine Disk, with agents, terminals, browsers, and development tools inside it. Start from a prebuilt Machine Definition and reuse your setup. Profiles supply your accounts and credentials separately.
Yes. All of Thinair’s systems are exposed through CLI, MCP, and API. Use your own agents, terminals, scripts, or applications to configure environments, launch Machines, and coordinate work. Use Thinair through its interface, as infrastructure, or both.
YOUR NEXT PROJECT
A place for you, your agents, and the whole process of making something.
Read the getting-started guide