Build Something in Five Minutes
The quickest way to see what Circuitry does is to ask for something and watch it appear: one sentence, and a working page opens beside the chat.
What you'll do
Ask an agent to build a small game, then play it. The agent writes the files, opens the result in a browser tab next to your chat, and — if something doesn't work — clicks through the page itself to find out why.
1. Create a project
Choose File → New Project and pick a folder. This is where the agent will write its files, so everything it builds is real work on your disk rather than something trapped in a chat window.
2. Open the agent chat
Click Agent Chat in the header. On a phone, tap Agent in the bottom bar.
The chat opens in its own panel beside your documents, so whatever the agent builds appears next to the conversation rather than replacing it.
3. Choose an agent
The first time you open the chat, a short setup asks which agent you want to use. There is no wrong answer here — you can change it later — but the choices fall into three groups.
- Free to start — Gemini CLI and Qwen Code both include a free daily allowance and need no card. Good if you just want to see this work.
- A subscription you already have — Claude Code or Codex CLI. These appear when the tool is installed on your computer, and they use the plan you already pay for.
- Your own key, or your own machine — OpenRouter takes one key and gives you a model picker covering many providers, including free options. Ollama or LM Studio run models privately on your own computer, also with a model picker showing whatever you have pulled.
In the desktop app this just works. On iPhone, iPad, Android or in a web browser, you need Circuit installed on your computer — that computer is where your files live and where builds and coding agents actually run. Circuitry reaches it from whichever device you happen to be on.
4. Ask for something
Type what you want. For example:
Build me a simple side-scrolling game in JavaScript where I tap to fly through gaps in pipes. Then open it so I can play.
Then watch. The agent will:
- Write the files — an HTML page, and whatever script and styles it needs.
- Open it in a browser tab right beside the chat, so you can see the result immediately.
- Play it, if you ask it to — clicking and pressing keys on the page to check the game actually runs.
5. Play it, then ask for changes
The page is live and yours. Play it, then say what you want different:
Too hard — make the gaps bigger and slow it down a bit.
Add a score in the corner and a game-over screen.
The agent edits the files and reloads the tab. You keep playing.
What just happened
Three things worth knowing, because they apply to everything else you'll do here.
The result opened where you can see it. Circuitry has its own browser tab, so a page the agent builds lands in your workspace beside the work it came from — not in a window somewhere else that you have to go and find. The tab stays open afterwards, so you can come back to it.
The agent can use that tab too. It isn't just a viewer. The agent can click buttons, type into fields, scroll, read what the page printed to its console, and see which network requests failed. That's how it checks its own work instead of asking you whether it worked. See Testing in the browser.
You can watch, and stop it. While the agent is using a page, the edges of that tab glow, a pointer moves to each thing it clicks, and a bar names what it's doing — with a Stop button. Nothing happens out of sight.
Where to go next
- Testing in the browser — everything the agent can do with a page, including checking phone layouts.
- Your first workflow — when you want something to run repeatedly, on a schedule or from a webhook, rather than once in a chat.
- The coding agent — plan approval, diffs, and working with your own repository.
- The smart whiteboard — when it's easier to draw what you mean than describe it.