Circuitry Changelog

Components version independently: the Desktop app, Circuit (tray / CLI / Docker), and the web editor each have their own version. When a change requires you to update your Circuit or MCP to keep working, the note says so and Circuitry will prompt you.

Desktop app

1.8.3 — 2026-09-02

• Nothing you type into a remote terminal is lost any more. Every keystroke is confirmed by the computer it is typed at; anything unconfirmed shows underlined where you typed it and is sent the moment the connection returns — even across a Circuit restart. Requires Circuit 1.8.3; with an older Circuit the previous behaviour is kept.
• Dropped connections hand your terminals to the replacement link in well under a second, instead of tearing them down and rebuilding them.
• On a phone, the workflow editor's bottom toolbar now spans the full width of the screen with bigger touch targets, and gains a Fit button.

1.8.1 — 2026-08-29

• Your agents can reach your phone from the desktop app too. When an agent rings its bell — it has a question, a plan for your review, or it finished — and no window is there to see it, the desktop app now sends the notification to your iPhone, and a paired Apple Watch shows it while your phone is locked. Requires Home Circuit and the latest iPhone app.
• Cmd+T in a terminal tab opens another terminal, the way it already worked in chats.
• This update is a one-time manual download. Circuitry is now signed with our new Apple developer identity, and your installed copy can only verify updates from the old one — so this once, the app won't update itself. Download Circuitry from circuitry.dev/download and install it over your current copy; your projects, settings and sign-in all stay. Updates are automatic again from then on.

1.8.0 — 2026-08-28

• Added Vim mode support in terminals.

1.7.1 — 2026-08-26

• Terminals, file changes and agent chats work again on your phone and iPad. On the same wifi as your computer the file list would load but a terminal stayed blank — the text side of the connection was being blocked before it ever reached your machine. Your device still talks to your computer directly over your own network, so nothing is routed through us and nothing is charged.
• Home Circuit connects on mobile networks. Away from home it often failed to connect at all and simply kept retrying.
• The connection light tells the truth. It stayed green after you had left the house, so the app looked healthy while nothing worked. It now turns blue as soon as you are away and back to green the moment you are home — green means your own network, blue means Home Circuit, so you can always see which one you are on.
• Reconnecting looks like reconnecting. A terminal that loses its connection now says so in the middle of the screen, with a Try again button, instead of printing warnings into your session that stayed in the scrollback afterwards.
• Dark Theme is always available. With only a terminal or browser tab open the option was greyed out, leaving no way to change the theme back.

1.7.0 — 2026-08-21

• Home Circuit: your computer, from anywhere. Your terminals, your coding agents and your files — reachable from any device, wherever you are. It isn't screen sharing: Circuitry talks to your machine directly, so everything is native on the device in your hand while the work runs on your computer's full power. Open the server menu, choose Home Circuit, and the setup walks you through three steps, ticking each off as it's done. On your home network Circuitry connects directly; when you leave, it switches to Home Circuit on its own and the server menu says so — and it switches back when you return. Right-click your computer in the server menu to choose the path yourself. Available on paid plans.
• Secured by pairing in person. A new device introduces itself by scanning the QR code from the server menu, on your local network. Pairing exchanges keys directly between your devices — we never see them — and every connection must be signed by a device you paired. Everything travels end-to-end encrypted between your devices; your computer never opens a port to the internet, nothing is reachable until you turn on Allow Remote Connections on the computer itself, and you can revoke any machine at any time. A "How is this secured?" explainer in the Home Circuit screen spells all of this out.
• Your sessions are one list, machine-wide. Terminals and agent chats started on one device now show up on all of them. The desktop app connects to your computer's Circuit on its own; a session's name follows it everywhere; an agent running elsewhere opens in the chat panel as a live view; and closing asks whether you're closing your view or ending the session. A chat closed by accident comes back with Cmd/Ctrl+Z.
• One chat is one agent session, across devices. Opening the same conversation's terminal on a second device now joins the session that's already running instead of starting a second agent wearing the first one's history.

1.6.1 — 2026-08-11

• Quitting with a terminal open no longer reports a crash. Circuitry shuts down the programs your terminals are running before it closes, and it now waits for them to finish going before it exits — previously it could get out of the door first, which macOS reported as a crash even though everything had closed properly.

1.6.0 — 2026-08-10

• Code files now tell you what things are. Hovering a variable, function or type in a code file shows what it is, what it returns and the note the author wrote above it — and where it used to sit there saying "Loading…" forever, it now answers. This was quietly missing everywhere: nothing in any code editor could report a type, an error, or a definition. Errors now underline as you type, and JSON and stylesheets are checked as well.
• Install language support for Python, Go, Rust and C/C++. With a Circuit connected, the language name at the bottom of a code file offers to install proper support for it. Circuitry downloads it, checks it against a published fingerprint, and keeps it in its own folder — no administrator rights, and removing it later is deleting a folder. Once installed you get real type information, documentation on hover, and jump-to-definition for languages that previously only had colouring.
• Toolchains and language support have a home in Settings, with what's installed, what version, and a way to add or remove each one. The build prompt used to send you to a settings page that had nothing on it.
• Installing build tools now works on Windows. Go and Zig could never install there.

1.5.0 — 2026-08-09

• Pick an assistant and Circuitry sets it up. Opening chat with no coding agent installed now offers the choices in one place — a free cloud agent (free tier with a Google account), agents that use a subscription you already have, private local models on your own computer, or one API key for hundreds of models. Circuitry installs your pick, connects it to your documents, tells you which sign-in option is the free one, and opens the chat.
• Local models are first-class assistants. A wizard finds models running on your computer, says which are big enough for real work and which can edit documents versus chat only, and the chat opens on your pick. Claude Code can also run on your local model — the full agent experience with nothing leaving your machine.
• Your account lives inside the app. The menu's Account opens plan, billing and usage in an overlay with a close button, instead of navigating the app away with no way back.
• Buying a plan completes without leaving the app. Checkout still opens in your browser, and the app now waits, notices the purchase, and unlocks everything in place — and the browser lands on a simple "payment complete" page instead of a sign-in screen.
• Choose your chat layout. A ⋮ menu in the chat header switches between the full chat interface and a clean terminals-only layout — automatic by default, based on the assistants you actually have.
• Fixed: quitting could leave the app running invisibly, and terminals could leave their programs running after quit.
• Fixed: the Space add-node menu could open underneath the chat panel.
• Fixed: another account's cloud server could remain listed after switching accounts on the same computer.

1.4.2 — 2026-08-08

• The desktop app is a free local IDE on every plan. Projects, files, terminals, command-line coding agents and running work on this computer no longer need a paid plan. Circuitry documents still save to the cloud on Personal and above.
• A simpler way in. The app can open straight onto a project and your chosen coding agent, with the chat pinned beside it, instead of the full studio.
• Pair programming and live collaboration are invite-first, and plans without them see what they'd get rather than an invite form that refuses when you click it.
• AI completions step aside quietly. When your plan has no cloud AI the toggle shows off and offers the upgrade; if your balance runs out, completions stop without a message on every keystroke, and your setting is remembered for when you top up.
• Fixed: on macOS the window's close, minimise and zoom buttons could sit oddly or lose their glyphs.

1.4.1 — 2026-08-08

• The top bar can be made shorter. Settings → Appearance → Header Density offers three heights on the desktop app and iPad. The height you have today is the largest of the three, and the buttons keep their full-size icons as the bar shrinks, so they stay easy to find and press.
• The server button shows where your work runs. Grey for this computer, green when another computer or a cloud server is connected, and a cloud when it is a cloud machine. A single cloud machine now shows whether it is awake.
• Fixed: the server menu stayed open when you clicked the canvas.
• Fixed: the desktop app could offer to move your project to a cloud server as though this computer had been lost.

1.4.0 — 2026-08-07

• Your project can follow you between computers. When the connection to your computer drops with a project open, the files panel offers a choice: reconnect, or hand over to your Circuitry cloud server and carry on there. The first time, Circuitry walks you through setting the project up on that machine — open a terminal on it, git clone your repository, choose the folder — and after that, switching between your machines is automatic, with a note telling you which machine you are looking at. Sync your work between locations the way you already do: commit and push before you move, pull when you arrive.
• A lost server connection is noticed in seconds, not minutes. Stopping or quitting your server tells Circuitry immediately, and an unreachable server now reads as a calm "Offline" rather than a red error with advice you can't act on.
• Cloud servers sleep on your schedule. Sleep-when-idle is now a setting (10 minutes, 30 minutes, or 1 hour) — and a busy server no longer dozes off mid-task: real activity on the machine (terminals, files, code runs) keeps it awake, and true idleness lets it sleep so it stops spending your credits.
• Cloud server addresses are one click away. Hover a running cloud server in Settings to copy its server and app web addresses — handy when you're testing something you built on it.
• Cloud servers always come with Python ready, verified at creation.

1.3.0 — 2026-08-05

• The chat and the terminal are two views of one conversation. Switching between the assistant chat and the terminal beside it used to start a second, separate assistant that knew nothing about the first — two histories, neither aware of the other. They are now the same conversation: carry on in the terminal, come back to the chat, and everything you said in either is there.
• Say something while the assistant is working and it hears you now. A message sent mid-task is delivered into the work in progress instead of waiting for the whole task to finish, so you can redirect an assistant that has set off in the wrong direction rather than watching it finish and starting again.
• You can watch the work as it happens. What the assistant is doing appears in the conversation as it goes, in its own block, rather than arriving all at once at the end.
• Attachments land where your cursor is. Attaching an image inserts a marker at the caret, so you can write about a specific picture in the middle of a sentence and the assistant knows which one you mean. Removing one renumbers the rest.
• A connection that drops now says so. If the connection to your server is lost part-way through a reply, the chat says the connection dropped instead of quietly presenting the half it received as the finished answer.
• Assistants can draw joined-up diagrams. Ask for a system diagram and you get properly labelled boxes with arrows that connect them, sized and weighted to what they join — and it can be turned into a working flow with the "To Nodes" button, which previously did nothing on a diagram an assistant had drawn.
• Thick arrows leaving a drawn card render correctly, instead of occasionally drawing a large white oval over the diagram.
• A chat carries on where it left off after a reload. If Circuitry restarts while an assistant is working — a crash, a refresh, or a restart you asked for — the chat now rejoins the work in progress instead of being left with half an answer. Chats that are still working show their spinner in the tab and in the open-chats list, and their replies keep streaming in.
• Nothing you had typed is lost. A half-written message, the files staged beside it, and any messages queued behind a working assistant all come back after a reload, and the conversation reopens where you were reading rather than jumping somewhere else.
• Scrolling up to read no longer pulls you back down. While a reply streams in you can scroll back through the conversation and stay there; the chat resumes following along when you return to the end.
• Terminals come back showing what happened while you were away. A terminal running a coding assistant used to reappear blank after Circuitry restarted, even though the work had carried on. It now reconnects and shows the output it missed, so you can see where the task got to.

1.2.1 — 2026-08-04

• Attach files to any chat, with or without a project folder open. Attaching an image to a chat backed by a coding assistant used to fail with an error unless a project folder was open — now it just works everywhere.
• Word, PowerPoint, Excel and OpenDocument files are now readable in chat. Attach a .docx, .pptx, .xlsx, .odt, .odp or .ods and every model — cloud, local, or coding assistant — can read its contents and answer in one turn.
• "What's this?" beside an attachment is now understood as being about the attachment, not about whichever document happens to be open in the editor.
• Chats without a project folder no longer change files on your computer. The assistant can still read the files you attach, but if you ask it to create or edit files it will ask you to open a project folder first.
• Very large images are resized automatically so they can always be sent, and attachment copies made for the models are tidied up automatically after a week.

1.2.0 — 2026-08-02

• You can now speak your messages instead of typing them. Hold the spacebar in the chat box, say what you want, and let go — the words appear where your cursor was. There is a microphone button next to Send, and Cmd/Ctrl+Shift+Space turns dictation on hands-free so you can talk without holding a key. Nothing is ever sent automatically: you read what was heard, fix anything it got wrong, and send it yourself.
• On a Mac, your voice never leaves your computer. Speech is turned into text on the machine itself, so it works with no connection and nothing is uploaded.
• On Windows and Linux, dictation opens a small listening window in Chrome or Edge, which closes when you stop. One of those browsers needs to be installed.
• You can see that it is hearing you. A small level bar appears where your next word will land and moves with your voice, so a silent microphone is obvious immediately rather than after you have said a whole sentence.
• Say "scratch that" to undo the last thing you said, "new line", "full stop", or "stop dictation" to finish. A command only counts when you say it on its own, so ordinary sentences are unaffected.
• Dictation switches itself off after a pause, or after three minutes, so a microphone is never left listening by accident.
• Choose which engine to use under Settings → General, where more than one is available.

1.1.2 — 2026-08-01

• Coding agents can now see your document when you use the app on its own. Claude Code and the other coding-agent tools reach your open document through a small connection inside Circuitry. On a machine running only the desktop app — with no separate Circuit installed — that connection refused every request, so an agent could talk to you but could not read the workflow, design or notepad you were asking about. It now works the same way it does with Circuit installed. A tool you start yourself from a terminal asks your permission first, as it always has; one started by your own chat message does not ask twice.
• Agents read the document you are actually looking at. With more than one Circuitry window open, an agent could be pointed at the wrong one and report an empty document. It now follows the window whose chat you are using.
• Fixed the app hanging on quit. Closing Circuitry could leave it sitting there without finishing, if a coding agent's connection was still open.

1.1.1 — 2026-07-30

• The app now updates itself on Windows and Linux, as well as macOS. Previously a new release had to be downloaded and installed by hand on every platform. Circuitry now checks on startup, downloads in the background, and installs when you quit.
• Coding-agent tools now work on Windows. Claude Code, Gemini CLI and Codex CLI installed through npm were being found but could not be started, so the model appeared in the list and then failed the moment you sent a message.
• Fixed a coding-agent chat that could not send its first message. Chats set to start a fresh session per message — rather than keeping one open — failed immediately with Claude Code. Affected every platform.

1.1.0 — 2026-07-29

• Out of beta. Circuitry is now a 1.x release. Nothing you have built changes; the version number simply reflects that the core is stable.
• Code steps in five compiled languages. Go, Rust, C, C++ and Zig, alongside JavaScript and Python. The desktop app builds them on your own machine — it installs the compiler each one needs, on request, into its own folder, with no administrator rights and nothing else on your system touched. Every download is checked against the publisher's own fingerprint first.
• Once built, a step runs anywhere — including in a deployed webhook, with no compiler needed at the far end, because the build travels with your workflow.

1.0.0-beta.5 — 2026-07-28

• Double-click a file and it opens in Circuitry. The desktop app now handles the file types it can edit — Circuitry documents (.circuitry, .canvas, .notepad, .sheet), Markdown, text and source code, configuration files, web files, CSV/TSV and Excel spreadsheets, PDFs, images, Word documents and video — so opening one from Finder, File Explorer or your file manager brings it up as a tab. Edit it and save, and it is written straight back to where it came from. Opening files this way works whether the app is already running or not, and selecting several at once opens them all.
• Spreadsheets opened from a file save back to that file. A CSV, TSV or Excel file opened from disk now saves over itself, keeping your column names and storing the formulas you typed rather than their last calculated values. Previously saving one asked where to put it and never touched the original. Saving a multi-tab workbook to CSV or TSV tells you how many tabs could not fit.

1.0.0-beta.4 — 2026-07-03

• Coding-agent chats in the desktop app now match the web experience. Chatting with Claude Code shows a live step-by-step transcript (thinking, tools, results), streams replies word by word, honors the effort and model selectors, starts faster (the session is prepared while you type), and the Stop button reliably interrupts the agent. Previously the desktop app returned the whole reply in one block with no progress shown.

1.0.0-beta.3 — 2026-06-23

• The close button always closes the app now. The red window button (and Quit) reliably closes Circuitry, including when you have unsaved changes — choosing “Don’t Save” now quits as expected — and when you’re still on the sign-in screen. Previously the window could refuse to close in those cases.

1.0.0-beta.1 — 2026-06-04

• First public beta of the Circuitry desktop app for Windows, macOS, and Linux (Intel & ARM).
• Circuitry now tells you when a newer app, Circuit, or CLI is available, and warns you (or stops a run) if your Circuit is too old to work with the current editor.

Circuit (tray / CLI / Docker)

1.8.4 — 2026-09-03

• Preview a dev server from your phone or iPad, wherever you are. When an agent builds something and serves it on the computer running Circuit, the in-app browser now works out how to reach it from the device in your hand: on your home network it goes straight to the computer; when a firewall is in the way, or you are connected through Home Circuit from elsewhere, the page travels through Circuit itself. Addresses like localhost — which used to point at the wrong device and show a blank page — are corrected automatically. Update Circuit to get the through-Circuit route; with an older Circuit, direct connections still work as before.

1.8.3 — 2026-09-02

• Nothing you type into a terminal is lost any more — not even while Circuit restarts. Every keystroke is now individually confirmed by the computer it is typed at. Anything not yet confirmed shows underlined where you typed it, and is sent the moment the connection returns — including the first few characters typed while a connection only looked healthy, which used to vanish without a trace. Update Circuit to get this; with an older Circuit the app keeps its previous behaviour.

1.8.2 — 2026-09-02

• Working away from home no longer drops the connection every half minute. Circuit and your device now share a single channel for their requests instead of opening a fresh one for every request. The old way was tearing down the entire connection from time to time — terminals, chats and all — and rebuilding it, which is what the stalls and the "reconnecting" flashes were. Update Circuit to get this; the app keeps working with an older one, it just keeps dropping.
• Large files and busy terminals no longer choke the connection they travel over. Circuit now paces what it sends when you are away, so reading a big file cannot flood the link and take your terminals down with it.

1.8.1 — 2026-08-29

• Your agents can reach your phone even when every screen is off. When an agent running on this computer rings its bell or finishes what you asked — and no device is connected to see it — Circuit sends the notification to your iPhone itself, and a paired Apple Watch shows it while your phone is locked. The notification says what the agent actually wants — "has a question for you" with the question itself, "has a plan for your review", or simply that it finished. Requires Home Circuit to be set up (that is what lets this computer act for your account) and the latest iPhone app.

1.8.0 — 2026-08-28

• Added Vim mode support in terminals.

1.7.6 — 2026-08-27

• Your chats keep their names. Opening Circuitry on a second device — a phone alongside your computer — could rename conversations on both to "New Chat", several at a time. A device that has simply picked up a conversation calls it "New Chat" until something names it there, and on starting up it was telling your computer that was its name. "New Chat" now means what it always meant — this one hasn't been named yet — and can never replace a name a conversation already has, whichever device says it. A chat held with a coding agent will also give itself its name back from the agent's own record of the conversation the next time you open it.
• "Open chats" keeps the order you were working in, on every device. The list puts the conversation you last worked in at the top, and it now follows you between machines: send a message on your phone and that chat is at the top of the list on your desktop too. Your computer now records only the turns you take — sending a message, or pressing Enter in a chat's terminal. Before, anything that touched a conversation counted, so reloading the page marked every chat as just-used at once and the order was lost exactly when you wanted it, and a chat whose agent was working away in the background could climb above the one you were sitting in. Without this update the list still orders itself on each device from what that device saw; it just doesn't follow you from one to another.

1.7.5 — 2026-08-26

• A chat you open on another computer comes back as itself. Pick up a conversation you started elsewhere and it opens the way you left it: one you were holding with a coding agent in a terminal opens in the terminal, with the same agent, instead of switching you to the chat panel; and the model shown at the top is the one the conversation has actually been using, rather than whatever that device happened to have chosen last. Previously a new device would open every conversation in the chat panel under its own default model, so an agent conversation could quietly continue with something else answering — and, because a coding agent keeps its own record of the conversation, carry on somewhere its history wasn't. Each device still remembers how you were using a chat on it, so a chat you deliberately moved to the chat panel stays there, and a phone with no project open shows the chat panel as it always has. Without this update the chat still opens; it just opens as the wrong thing.

• Your computer stays one device in the list. If a browser or phone lost the key that identifies it — Safari clears it after about a week of not visiting — it used to be recorded as a brand-new device with the same name, so one Mac could appear four or five times and your own chats started showing up under "On your other devices" badged with the name of the machine you were sitting at. Pairing again now updates the device you already have instead of adding another. Devices already in your list are unaffected, and re-pairing still asks for the same in-person QR step it always did.

1.7.4 — 2026-08-25

• Coding agents in a terminal can now reach your work without any setup. Open a terminal in Circuitry, run Claude Code, Gemini CLI, Qwen Code or Codex, and it can see the document you have open straight away — no install step and nothing to configure. If an agent still can't reach Circuitry, the terminal now says so along the bottom and offers to fix it in one click, with a "Why?" explaining what that gives the agent. Previously an agent could sign in to the wrong copy of Circuitry, or be refused for a saved sign-in that had expired, and the only clue was the agent reporting that it lacked permission.
• Pages your agent builds now open in the Browser tab. Ask your agent for something you can look at — a game, a chart, a page — and it now opens it in the Browser tab instead of leaving you a file to find. The page is served by this computer, so links, images and stylesheets inside it work and a whole small site opens, not just one page. Only the folder your project is in is ever served, and only to the app that asked. Without this update the agent can still build the page but cannot show it to you, and it will say so rather than pretending it worked.

1.7.3 — 2026-08-23

• The tray app is now called Circuit. Same app, same install, new name — nothing to redo and no need to pair your devices again. It was "Circuitry Server" (and "EServer" in older notes), which said more about servers than about what it does: bring a computer into Circuitry so your iPad, laptop or phone can work on its files, terminals and Python. The tray menu, its Preferences, Logs and Activity windows, the command-line tools and the installer all say Circuit now. It joins names you already know — Home Circuit for reaching your computer from outside your network, and Cloud Circuits for a machine we run for you.
• Because the name is on the installer, the download is now Circuit-<version> rather than Circuitry EServer-<version>. It installs over the copy you already have.

1.7.2 — 2026-08-22

• Archived chats follow you. A chat you archive on one device is archived on all of them, and the Archived list is the same wherever you open Circuitry. Deleting one removes it everywhere. Without this update archiving still works, but the shelf stays on the device that made it.
• A device you just paired shows up straight away. Pairing a phone or tablet with the QR code added it to the list in Preferences, but the window didn't notice until you closed and reopened it — so it looked as though the pairing hadn't taken.

1.7.1 — 2026-08-22

• "On your other devices" now means open, not remembered. The server keeps a record of every chat it has ever seen, and the chat list was reading that record — so a phone showed every conversation the desktop had ever started, even ones closed weeks ago. The server now reports which devices actually have a chat open right now, so the list shows the handful you could walk over to, each badged with the device holding it. Until you update the server, the chat list behaves as it did before.
• Closing a chat updates your other devices straight away. A chat you close — whether it was an assistant chat or a coding-agent terminal — leaves the other devices' lists at once instead of lingering for a few seconds, and a device that goes to sleep or loses its connection stops counting as having chats open. If a reply was running when a window disappeared, the other devices no longer sit showing "working" for a chat nobody has open.

1.7.0 — 2026-08-21

• Home Circuit lands in the server. This update is what makes your computer reachable from anywhere: the tray gains Allow Remote Connections — nothing is reachable until you turn it on — and pairing by QR code now exchanges keys between your devices directly, so only a device you paired in person can connect. Connections are end-to-end encrypted and travel between your devices without passing through our servers; your computer never opens a port to the internet. Revoking a machine from the Home Circuit screen cuts it off within seconds.
• The server keeps the machine's one session list. Terminals and coding-agent sessions now live with the server rather than with whichever window started them, so every connected device sees the same work, names given anywhere travel with the session, and a session survives the window that opened it. Existing setups keep working without updating — updating is what switches Home Circuit and shared sessions on for this machine.
• Your chats follow you between devices. A conversation you start on your phone now shows up on your desktop under On your other devices in the chat list — tap it and you carry straight on, with the history already there. Terminals have worked this way for a while; chats do now too, over the same server, so nothing goes near the cloud. Messages sync as they are sent and received rather than keystroke by keystroke, which keeps it quick on a patchy mobile connection.
• Coding-agent chats hand over cleanly. A chat backed by a coding agent can only be driven from one device at a time — two would write over each other's conversation. The chat says Active on <device> when it's being used elsewhere, and Continue here takes it over deliberately, so it never moves out from under you. Closing the window hands it back straight away.
• Renaming or recolouring a chat, and rewinding a conversation, now reach your other devices too.
• Requires the matching editor update; your existing chats are untouched and stay on your device until you connect a server.

1.6.0 — 2026-08-10

• Your server can now run language support for your code. Install Python, Go, Rust or C/C++ support and the editor gains real type information, documentation on hover and jump-to-definition for those files. Everything runs on your own machine; nothing about your code is sent anywhere.
• New tools arrive without updating the server. The list of available build tools and language support now comes from Circuitry, so new languages and version updates appear on the server you already have.
• Fixed: installing the Go or Zig build tools failed on Windows.
• Fixed: build tools that need the GNU C library are no longer offered on systems that cannot run them, instead of installing and then failing to start.
• Fixed: a tool you just installed could still show as missing until the server was restarted.
• Language support processes are now shut down with the server, instead of being left running.
• Updating is recommended so language support in the editor lights up, but not required.

1.5.0 — 2026-08-09

• Coding agents on your own machine connect without a permission prompt. A tool running on the same computer as your Circuit is your own software — it now connects automatically, while connections from other machines still ask first.
• The server can set up your coding agents. Circuitry's assistant setup — installing an agent, connecting it to your documents, finding local models — now works through a connected server too, so the web and iPad apps get the same one-click setup as the desktop app.
• Fixed: with several Circuitry windows open, a connection request could be answered by a background window before you saw it.
• Updating is recommended so the newest features in the editor light up, but not required.

1.4.0 — 2026-08-07

• Stopping or quitting tells Circuitry immediately. Connected windows see the server go Offline within seconds, instead of discovering it up to a minute later.
• Stop, then Start, works reliably. The server now fully releases its network port when it stops, so starting it again no longer fails with the port still in use.
• The server remembers your open project across restarts. This is the foundation of project handover: any of your devices can ask a server which project lives on it — including a cloud server that has just woken up.
• It knows when it is really being used. The server tracks genuine activity — terminal keystrokes and output, file operations, code runs — so a Circuitry cloud server can stay awake while a long task runs and sleep only when truly idle. Routine status checks don't count, so an idle machine still sleeps on schedule.
• Updating is recommended but not required — previous versions keep working without the faster offline detection and project memory.

1.3.0 — 2026-08-05

• Stopping is now something you say, not something guessed from a dropped connection. The server could not tell "the user pressed Stop" apart from "that window reloaded", so a reload killed whatever the assistant was doing mid-task. Stop is now sent explicitly, and a task whose window merely went away runs to completion and is waiting when you come back.
• A message sent mid-task reaches the assistant while it works, rather than being held until the task ends.
• One conversation across the chat and the terminal. The server now hands the same assistant session between the two surfaces instead of running one behind each.
• Work in progress survives Circuitry restarting. The server now keeps a short recording of whatever an assistant is doing, so a Circuitry window that reloads mid-task can pick the task back up — including everything that happened while it was away. Previously that work continued but was invisible, and the chat was left showing an answer that never finished.
• A task that fails now says why. If an assistant's process stops unexpectedly, the reason is held long enough for the chat to report it rather than simply freezing.
• Terminal output is kept for a client that comes back. The server now holds recent terminal output per session, so a Circuitry window that restarts reconnects and catches up instead of showing an empty terminal for a task that is still running. Updating is recommended but not required — the previous version keeps working, but the chat improvements in this release are the ones it cannot do, so a reload will still end a task and a message sent mid-task will still wait until the end.

1.2.1 — 2026-08-04

• Fixed chat attachments failing without a project folder. Attaching an image to a chat backed by a coding assistant no longer errors when no project folder is open — attachments are handed over privately on your own machine, and the copies are cleaned up automatically after a week.
• Chats without a project folder no longer change files on your computer. The assistant can read what you attach, but file creation and editing now ask you to open a project folder first. Updating is recommended but not required — the previous version keeps working.

1.2.0 — 2026-08-02

• No changes for Circuit in this release. Its version moves with the desktop app so the two stay easy to talk about; there is nothing you need to do, and 1.1.2 keeps working.

1.1.2 — 2026-08-01

• Fixed coding agents reporting a permission problem that was really an expired key. The connection a coding agent uses to read your document signs in with an access key of its own. If that key had been reset — which happens when Circuit re-encrypts its keys — every request failed, and the agent was told its connection had not been approved. It would then ask again, and again, each attempt costing you a full reply. Chats now hand the agent a key that cannot go stale, and nothing has to be set up by hand.
• Agents read the document you are actually looking at. With more than one Circuitry window or tab open, an agent could be pointed at a different one and answer as though your document were empty. It now follows the window whose chat you are using.

1.1.1 — 2026-07-30

• Coding-agent tools now work on Windows. Claude Code, Gemini CLI and Codex CLI installed through npm were being found but could not actually be started, so the model appeared in the list and then failed the moment you sent a message. They now launch correctly, whichever way the tool was installed.
• A tool that cannot run is no longer offered. On Windows, anything Circuit cannot actually start is reported as not installed, rather than appearing as an available model that fails on first use.
• Fixed a coding-agent chat that could not send its first message. Chats set to start a fresh session for each message — rather than keeping one open — failed immediately with Claude Code. Affected every platform.

1.1.0 — 2026-07-29

• Four more languages for code steps. Alongside Go you can now write a step in Rust, C, C++ or Zig, and all of them run the same way — on your own computer, or in the cloud using the build saved with your workflow. Rust and Zig steps build to very small programs (tens of kilobytes), so they start instantly.
• Reading JSON is built in for every one of them. Rust, C and C++ have no JSON in their standard libraries and no package manager here, so Circuitry provides the type for you — you do not add a dependency, and you should not try to. Zig uses its own standard-library JSON.
• Circuitry installs the compiler each language needs, on request, into its own folder — no administrator rights, and nothing else on your system is touched. Every download is checked against the publisher's own fingerprint before it is used. C and C++ share one install.
• Your code is now a file of its own. Previously Circuitry placed your snippet underneath its own supporting code, which quietly meant you could only use the handful of packages Circuitry happened to bring in, and you could not add an import of your own at all. Now you write ordinary Go or Rust: import anything from the language's standard library exactly as you would in any other project.
• Compile errors point at your line. They used to be offset by the length of Circuitry's supporting code, so the marker landed past the end of what you had written.
• If you have existing Go steps, add the imports they use — for example import "fmt" if the step prints. The editor marks the exact line. Nothing else about them changes.
• Building needs a computer of your own connected — the desktop app, or a machine running Circuit. Building in the cloud is not available yet, so a tablet on its own cannot build a compiled step; once built, it runs anywhere, including deployed webhooks.
• Building needs this version. An older Circuit cannot build steps written the new way, so Circuitry asks you to update rather than showing a compiler error you did not cause. Everything else about an older server keeps working.

1.0.0-beta.5 — 2026-07-09

• Connecting a tablet or phone by QR code works again. Scanning the QR code from Circuitry Server failed with “Unauthorized”, because pairing asked the device for the access key that pairing itself is supposed to hand out. Scan the code and the device pairs; the QR window now confirms which device connected and tells you it's safe to close.
• Circuit in Docker is reachable on the port you publish. The container ignored its configuration file and only listened inside itself, so every connection from outside was refused — while the container still reported itself healthy.
• Your access keys are better protected. They're now encrypted with a secret unique to your install rather than one shared by every copy of Circuit, and they can no longer be read back over the network without authenticating first.
• You now pair a browser deliberately. Because of the change above, a browser that finds Circuit on your machine no longer configures itself with a key it fetched from the server. Connect by scanning the QR code, or paste an access key under Settings → Developer → Circuit. Devices you have already paired keep working.
• A server left running for weeks now hears about new versions. Circuit used to check for updates only when it started, so one that had been running a long time could sit on an old build indefinitely. Circuitry now tells it when a newer version is published, and the tray shows a notification once — not a dialog, and not again for the same version. Older servers are unaffected and keep checking at startup as before.

1.0.0-beta.4 — 2026-07-03

• Coding-agent chats are faster and far more transparent. When you chat with Claude Code through Circuitry, the chat now shows a live step-by-step transcript (what the agent is thinking, which tools it runs, and their results), streams its replies word by word, and starts noticeably faster — the agent session is prepared while you're still typing. Long quiet spells now say why ("waiting on the model") instead of looking stuck, and Stop always stops. Update your Circuit to get these in the web and iPad editors; older servers keep working with the previous chat behavior.
• Per-chat effort and backing-model controls now reach the agent. The effort selector under the chat input controls how deeply the agent thinks (off = fastest), and the model selector picks which Claude model the session runs on.

1.0.0-beta.2 — 2026-06-06

• Webhook listen mode. When you arm “Listen for request” on a webhook in the editor, your self-hosted Circuit now captures the next incoming request and shows you its payload — without running the workflow — so you can see the exact shape of the data before wiring up the rest. Update your Circuit to use Listen on self-hosted webhooks; older Circuits keep working for everything else.

1.0.0-beta.1 — 2026-06-04

• First public beta of Circuit.
• The tray app now has a Check for Updates… option and notifies you on startup when a newer version is available.
• The command line (eserver update) now reports versions correctly and shows an update notice when you start the server (turn it off with CIRCUITRY_ESERVER_NO_UPDATE_CHECK=1).

MCP server (@circuitry-ide/mcp-server)

2.3.0 — 2026-08-25

• "Open it in the browser" now means Circuitry's browser. Ask your coding agent to open, preview or show you a page — or to check a dev server you're running — and it opens a Browser tab in Circuitry, beside the work it relates to, where you can watch what it does and keep the page afterwards. Previously an agent with a browser extension of its own would quietly use that instead, putting the page in a window you weren't looking at. Ask for Chrome, or "my real browser", and it still uses that.
• A slow call no longer looks like a failed one. When Circuitry takes too long to answer, the agent is now told the work may have gone through and to check before trying again — so a slow request can't leave you with two of everything.
• Agents are pointed at the how-to guides. Circuitry's built-in guides are announced when the agent connects, so it reads the right one before its first attempt at something unfamiliar rather than after getting it wrong.

2.1.0 — 2026-07-02

• Picks up new tools automatically. The MCP server now fetches its tool catalog from your running Circuitry when it connects, so new Circuitry features appear in Claude Code and other coding agents without updating the MCP server. If a future Circuitry ever does need a newer server, it will tell you at connect time.
• Canvas screenshots arrive as images. Any tool that captures your canvas or screens now delivers a real image to the coding agent (not raw data), so agents that understand images can see your sketches and designs.
• New document tools. Coding agents can now inspect the active document (doc.describe, doc.query, doc.selection), see the canvas (doc.screenshot), draw and rearrange content (doc.patch — shapes, text, SVG art, align/distribute, grouping), and pull how-to guides on demand (skills.list / skills.get).

Web editor

2026-09-03

• Local pages open on the right machine now. When an agent opens a page like localhost:5173 and you are on a phone, iPad, or another computer, the browser tab now points itself at the computer actually running the page instead of the device in your hand — which used to show a blank screen. If that computer can't be reached directly (a firewall, or a Home Circuit connection from elsewhere), the page is delivered through Circuit instead; that route needs Circuit 1.8.4 or later.

2026-09-01

• The keyboard stays up when your phone changes network. Moving between wifi and mobile data used to rebuild the terminal underneath you, which put the keyboard away mid-sentence and left you tapping to get back in. Circuitry now hands the cursor back to the terminal you were typing in, so a network change no longer interrupts you.
• A terminal that loses its connection keeps its scrollback. Leaving and returning to a terminal during a dropout no longer starts it over with an empty screen and a "Circuit not connected" message — your session, its history and its running program are all still there when the connection comes back.
• Typing works again after leaving Circuitry and coming back. On a phone, returning to a terminal that had lost its connection while you were in another app could leave it accepting no input at all until you closed the tab.

2026-08-30

• Typing in a terminal never freezes and never loses a word, even when your connection drops. Keystrokes now appear the instant you press them — including in Claude Code and the other CLI agents, where in-flight characters show underlined until the agent confirms them — and anything typed while you're disconnected is kept and delivered the moment the connection returns. Press Enter while offline and Circuitry tells you your message is queued, then confirms when it's sent. A brief network blip is now a non-event: no flashing, no dimming, no lost characters. Only an outage that persists calmly dims the terminal, and one that can't recover offers a retry — never an error over your work.
• Home Circuit connects reliably on cellular networks. Connections that reached your computer but couldn't carry traffic on some mobile and café networks now switch to the relay automatically, and the credentials for it are kept on your device so the switch works even at the moment the network changes. Terminals reconnect on their own after an outage and catch up on everything that happened while you were away.
• On the phone, an agent showing you its work brings you back when it's done. When an agent opens a document to work in it, the screen returns to your conversation a few seconds after the work finishes — unless you've started looking around yourself.

2026-08-29

• Your Apple Watch and iPhone can now tap you when an agent needs you. When an agent finishes and rings its bell — it has a question, a plan for you to approve, or a permission to grant — Circuitry sends a notification to your iPhone, and a paired Apple Watch shows it the moment your phone is locked. Tap it to land on the exact chat that's waiting. Works whenever any of your Circuitry windows is open next to the agent, even if your phone is in your pocket across the house. Requires the latest iPhone app and notification permission. With Home Circuit set up, the next Circuit update takes this further: your computer sends the notification itself, so it works even with no Circuitry window open anywhere.
• Vim mode in terminals now speaks the full editing grammar. Change, delete and yank work with all the usual motions and text objects — words, quotes, brackets and the rest — p and P paste at the spot you are pointing, and yy copies the command you are typing rather than the row on screen. Entering it always seats you on your input line, even while a program is drawing a spinner.
• Press and hold in a terminal picks out what's under your finger — a link you can open, a file path, or text to select — instead of leaving you to fish for it with a text cursor.
• Text selected from a terminal now reads as prose. The selection view reflows an agent's output into real paragraphs instead of screen-width fragments, so copying its answer gives you something you can paste anywhere.
• Workflows fit a phone properly. Nodes draw compact on a small screen, and opening a node's details or settings fills the screen instead of squeezing into a corner.
• Integration nodes were swept against the services they talk to — corrected well over a hundred out-of-date operations across more than 40 integrations, so requests match what each service expects today.
• Fixed the file browser getting stuck on a folder that no longer exists — it now opens the nearest folder that still does.

2026-08-28

• Vim mode in the terminal is steadier. Entering insert mode now lands the cursor where you expect, even across wrapped lines, and / search finds text while you are mid-edit.
• Code editing on a phone got smoother. The editor reclaims its side gutter for your code, and pinch-to-zoom now scales the code font instead of the whole page.
• Fixed a cursor that drifted while typing in code editors on iPhone and iPad.
• Fixed a crash when opening a large file on a phone.

2026-08-27

• Opening Circuitry with a lot of chats open is calm again. Every open chat used to reconnect the moment the app loaded — with thirty of them that meant thirty conversations all reaching for your computer at once, every spinner in the list going, and on a phone a burst of downloading at the exact moment you opened the app. The chat you are looking at now connects immediately, the few you are most likely to want next follow once it has finished, one at a time, and the rest connect when you actually switch to them. On a phone, or when you are away from home and going through Home Circuit, nothing loads in the background at all — on a cell connection the chat you are looking at should have it to itself. Nothing is lost by waiting: the agent keeps working on your computer either way, and its terminal fills in completely when you open it. This also fixes terminals that came up blank until you clicked or typed in them.
• Your chats keep their names. With a phone open alongside your computer, conversations could be renamed to "New Chat" on both at once — most often right after a reload. A device that has simply picked up a conversation calls it "New Chat" until something names it there, and it was publishing that as though it were the name. "New Chat" now means what it always meant — this one hasn't been named yet — and can never replace a name a conversation already has. A chat held with a coding agent gives itself its name back from the agent's own record of the conversation the next time you open it.
• The chat you were last working in sits at the top of "Open chats". With several agents on the go the list used to render in the order the tabs were opened, so finding the one you were just in meant reading every label. It is now ordered by when you last worked in a chat — sending a message, or pressing Enter in a chat's terminal — and it follows you across devices, so a conversation you drove on your phone is at the top on your desktop. Simply switching between chats doesn't reorder anything (the list would move under your finger), and neither does an agent talking to itself in the background, so the order always reflects what you were doing. Reloading the page keeps it. The tabs across the top deliberately stay in the order you opened them.

2026-08-26

• The phone and iPad apps stop asking you to sign in every time you open them. With Remember me ticked, the app now signs you in from the password already saved on your device and takes you straight to your work, the way the desktop app does. Signing out still means signed out — it won't sign you back in the next time you open it.
• Terminals, file changes and agent chats work again on your phone and iPad. When your device was on the same wifi as your computer, these had stopped arriving — the list of files would load but a terminal stayed blank and never caught up. They now come through reliably, and your device still talks to your computer directly over your own network, so nothing is routed through us and nothing is charged.
• Home Circuit connects on mobile networks. Reaching your computer from 4G or 5G would often fail to connect at all, retry, and fail again. It now connects on the first try in most places.
• The connection light tells the truth. It stayed green — "connected to your home network" — after you had left the house, so the app looked healthy while nothing worked. It now turns blue as soon as you are away and back to green the moment you are home, and it changes the instant the connection does rather than a few seconds later. Blue means Home Circuit is carrying your work; green means your own network is, at no cost.
• Resetting a forgotten password works wherever you open the email. The reset link only worked in the browser you had asked from — open it from your mail app, your phone, or a different browser and it said the link was invalid or expired. It now works wherever you open it, and it never asks for the password you have forgotten. If a link really has expired, the page says so instead.
• Changing your password now asks for your current one. If you are signed in and change your password, Circuitry asks for the password you have now before setting the new one, so someone who reaches your open session cannot lock you out of your own account. This is only for a deliberate change while you are signed in — resetting a forgotten password by email never asks for one.
• Dark Theme is always available. With only a terminal or a browser tab open, the View → Dark Theme option was greyed out and there was no way to change the theme back. It now applies to the app itself when the open tab has no theme of its own. Terminals stay dark either way, which is what command-line tools expect.

2026-08-23

• Write workflow steps in TypeScript. Pick TypeScript in a code node — or in a CodeBook cell — and write it the way you would anywhere else: interfaces, type annotations, generics. The types are removed when the step runs, so it goes at the same speed as JavaScript, works offline, needs nothing installed and is on every plan. Breakpoints work too, and they pause on the lines you actually wrote.
• "Execution Server" is now "Circuits". The Settings section where you connect your own computers is called Circuits, and everywhere the editor used to say "Circuitry Server" or "EServer" it now says Circuit — the same name the tray app itself uses. Your connections, keys and paired devices are untouched. The handbook pages moved to match: /docs/circuit, /docs/circuit-cli, /docs/circuit-docker, /docs/circuit-cross-device and /docs/multi-circuit-support. Old links still work and land in the right place.
• The phone key bar swipes for more keys. The strip above the keyboard used to hold Esc, Tab, the modifiers and the cursor keys. Swipe it sideways and it turns to the characters your phone keyboard makes you leave the letters to find. First the punctuation you write sentences with — . , ? ! ' " ( ) : ; - — because describing something to an agent or quoting a line back shouldn't cost a trip through the 123 key. Swipe again for the coding set: ` ~ | \ / - _ { } [ ], then the operators < > = + * & ^ % # @ $, then Home/End/PageUp/PageDown/Delete, then F1–F12. Dots along the top show where you are, and the name of the set flashes as it turns. The key that puts the keyboard away is on every page, and Ctrl or ⌘ stays armed while you swipe — so Ctrl-C still works from wherever you've landed. Swiping never types the key you started the swipe on.
• Your coding agent can use the Browser tab. Open a Browser tab from the + menu and the agent can work in it with you: open a page, look at what's on it, click and type and scroll, and read back what happened. Ask it to check the site you just built and it opens your dev server, clicks through the thing you changed, reads the browser's console for errors, and tells you what it found — rather than reading your code and guessing. It never opens a browser tab on its own: it uses the ones already open, or opens one when you ask, so your workspace stays yours. Two tabs at once works too, which is how you compare staging against live.
• You can watch it work. While the agent is driving a page you see its pointer move to each thing before it clicks, and a bar across the top of the page says what it's doing with a Stop button. On a phone, where the page usually isn't on screen, the Docs button in the bottom bar wears a pulsing blue dot — tap it to watch.
• Browser console and network, on tap. The agent can read the page's console messages and the requests it made, filtered to just errors or just the ones you care about. This is what turns "the button doesn't work" into "the button throws, here's the line".
• On a computer, the desktop app drives pages fully — real clicks and typing, drag-and-drop, and screenshots. In the web app, pages you browse through your own computer can be read and driven too; a page opened without your Circuit connected can be viewed but not driven, and the agent will say so rather than pretending. Needs Circuit 1.7.2.

2026-08-22

• Archive a chat instead of closing it. Right-click a chat — its tab, or its row in Open chats — and choose Archive. The chat closes and moves to a new Archived section at the foot of the Open chats list, so you can clear your workspace without losing anything. Click an archived chat to pick it straight back up; right-click one to delete it for good. Your archive is the same on every device, so what you shelve at your desk is waiting on your phone.
• Fixed: on a phone or tablet, a coding-agent terminal could stop scrolling — you could still type, but dragging did nothing. It happens when the coding agent takes over the pointer for one of its interactive prompts; on a computer the scroll wheel still reaches it, but a finger had nowhere to go. Dragging now scrolls again in both cases.
• Fixed: a chat reopened from Archived or Chat History now comes back on the surface you left it on — a coding-agent chat you were running in the terminal reopens as the terminal, not as an ordinary chat. Each of your devices remembers this separately, since a phone has no coding agent to open.
• Fixed: the chat list's On your other devices section now lists only the chats your other devices genuinely have open, badged with the device holding each one, instead of everything those devices had ever started. Closing a chat anywhere clears it from your other devices immediately, and a chat whose window vanished mid-reply no longer stays stuck as "working". Needs Circuit 1.7.1.
• See which sessions are working, and stop any of them from anywhere. A coding-agent session now shows a spinner while it's producing output — in the chat list, on your own device and on your others — so you can tell at a glance whether the agent on your desk is mid-task or waiting for you. Right-click any session in the cross-device lists to End session: your computer runs them all, so you can stop one from your phone without walking back to the machine that started it. Needs Circuit 1.7.1.
• Fixed: closing a coding-agent chat's tab now ends its session, unless another of your devices still has that conversation open — in which case it keeps running there. Sessions used to outlive every tab that showed them and pile up as agents nobody was watching.
• Fixed: a coding-agent chat you started on another device now shows up as that device's chat — under On your other devices, badged "iPhone" — instead of dropping to the bottom of the list labelled with the computer running it. Chats you use only in the terminal now appear on your other devices at all, and every terminal and agent session is now labelled with the device it was started on rather than the computer hosting it. Needs Circuit 1.7.1.

2026-08-21

• See where your month is going. A new Usage item in the menu (and under Help) opens a single screen for your credits: how many are left of this month's allowance, what's already gone, and a breakdown of what spent them — AI, cloud servers, cloud server disk, cloud automation, Home Circuit and data transfer — so a surprising month has an answer instead of a number. Disk is its own line because it keeps billing while a machine is switched off. It also shows roughly how much longer your balance lasts at the rate you've been working, and how much of your cloud storage is in use. On the Free plan the same screen explains what credits are for and what each category covers. Credits reset on the 1st, and the screen counts down to it.
• Fixed: on a phone, creating a new document now switches to it instead of leaving you looking at the agent chat.
• Fixed: a conversation opened on another device no longer shows the assistant's background instructions inside your own messages — you see what you typed.
• Fixed: a whiteboard stays a whiteboard. Its tab and the phone's document button now wear the pen icon and keep the name "Whiteboard" until you add the first node — at which point it becomes a workflow and says so. Previously a whiteboard came back from a reload renamed "Untitled Workflow".
• On a phone, the document button in the bottom bar is now labelled "Docs", and the bottom bar's five icons are all the same size with their labels on one line.
• Draw with your finger. On a phone, a finger now draws whenever a drawing tool is active — no stylus needed. Two fingers still pan and pinch to move around the canvas. On a tablet this is the Draw with finger setting, which until now only changed how a finger navigated: the pens, shapes, eraser and text tool still quietly refused anything but a pencil or a mouse, so turning it on never actually let you draw. It does now. If you use a pencil on a device, Circuitry hands drawing back to the pencil and gives your finger the canvas again, so one finger pans and zooms — drawing with a finger is there for devices without a pencil. You can still turn it back on in Settings.

2026-08-19

• The assistant knows which document you mean — splits included. Ask about "this" and it reads the document you're actually focused on, in any pane of a split (the bottom row included), and code files count as much as workflows and designs — it answers with the file and its path instead of guessing at some other open tab. Text you select in a code file, a preview or a PDF reaches the assistant too, so "what does this selected part do?" works even after you've clicked into the chat to type — and when nothing is selected, it says so and still names the document it looked at.
• Splitting to the bottom keeps your tabs. Dragging a tab to the bottom half of the screen used to empty the top tab bar into a "Drop tabs here" placeholder; the remaining tabs now stay where they were, with the right one highlighted.
• A file tab tells you where the file lives. Hovering a tab shows the full path, and right-clicking offers "Show in Files" to reveal it, selected, in the file browser.
• Fixed: opening the Help tab always brings up the documentation list, not an empty panel.
• Fixed: opening a file that is already open switches to its tab instead of opening a copy.

2026-08-17

• Suggestions as you type are now off until you switch them on. Everything else the AI does here happens because you asked — you run a step, you press Cmd+K, you send a message. Suggestions were the one thing that started on their own, and on a paid model that meant spending while you were still deciding what to write. Switch them on in Settings → Inline AI, from the switch in a code editor's status bar, or by ticking "AI suggestions while typing" in a Code or Agent step's settings. If you already had them on and never changed the setting, they're now off — turn them back on and it stays. Cmd+K is unchanged: it only ever runs when you press it.
• Suggestions in an Agent prompt are now off unless you ask for them. An Agent prompt is writing rather than code, and it's the one place you might sit typing for several minutes without running anything — so suggestions fired constantly, guessed at what you meant, and on a cloud model cost something every time you paused. Turn them back on under Settings → Inline AI. Code editors are unchanged.
• Every Code and Agent step can turn suggestions off on its own. Open the step's settings and untick "AI suggestions while typing". Steps on the canvas have no status bar to put the switch in, which is why there was no way to do this before.
• Suggestions now use your default model — including a local or command-line one. They used to run on a model we picked, which meant being charged for suggestions you could have had for nothing if you already had a model on your own machine. Now they follow whatever you've set as your default: if that's a local endpoint, a command-line tool or Apple Intelligence, they run on your machine, never pass through us, and cost nothing on any plan. The separate "use my own model" switch is gone — there's nothing left to opt into. Platform models are charged as before, and shown as "Code completion" in Usage & charges.
• Typing on doesn't buy another suggestion. Circuitry now waits for the answer it already asked for and shortens it as you type, instead of abandoning it and asking again — so a burst of typing costs one suggestion rather than several, and the one it costs actually appears. Suggestions that used to be paid for and then thrown away for arriving a moment late are now shown. Coming back to somewhere it has already looked reuses that answer rather than paying for it twice.
• Fixed: opening a step's settings and closing it again switched suggestions off for every other step of the same language on the canvas, with no way to get them back but a reload.
• Fixed: a step could offer suggestions based on the data feeding a different step.
• Fixed: typing in a Code step still stuttered when a lot of data was feeding into it.
• Fixed: Settings → Inline AI said "Enabled" on the Free plan while nothing could happen. It now says the plan doesn't include it — and points out that a model running on your own machine works on every plan.

2026-08-15

• Code completion is now listed separately in Usage & charges. Suggestions that appear as you type were counted as ordinary AI text, so an afternoon's typing filled the list with near-identical entries and buried the things you actually asked for. They now have their own "Code completion" category.
• Cmd+K uses your own model too, and is listed separately. The inline prompt now runs on a local or command-line model when that's what you've selected, instead of asking for a paid plan you don't need for it, and its charges show as "Inline edit" rather than as ordinary AI text. Unlike completion as you type, it isn't hidden behind a setting — you asked for it, and the answer arrives as a change you can accept or reject.
• Completion on your own model is yours to switch on. If you've picked a local, command-line or on-device model, completion as you type is now off until you enable it under Settings → Inline AI — a smaller model tends to guess badly mid-line, and an unhelpful suggestion interrupts more than no suggestion does. It runs on your own machine either way, so it costs nothing to try and nothing to leave on.
• Fixed: signing in with Google in the desktop app did nothing — you were signed in on the web page that opened, while the app kept waiting. The page it returns to now tells you you're signed in and that the tab can be closed, instead of being left loading forever.
• Fixed: choosing Upgrade plan closed the app.
• Fixed: running Python in a Code step froze everything until it finished. Python now runs out of the way of the interface, so you can keep working while it does.
• Fixed: typing a prompt could stutter and lose characters while a suggestion was being prepared, and a suggestion that arrived late could land in the wrong place.
• Fixed: a Website block reported "no handler registered" instead of running.
• Fixed: editing text on a drawing could stop the page responding.

2026-08-11

• A React file now shows you the component, not just the code. Open a .jsx or .tsx file and it opens the way an HTML file does — the code on the left, the component actually running on the right — and it keeps up as you type. Hovering the code highlights the matching part of the render, and clicking a part of the render jumps the cursor to the line that made it. Your project's own styles, fonts and providers are used, so what you see is what the page looks like. Switch between code, preview and split from the View menu.

2026-08-09

• Auto top-up now tells you what happened. When your balance runs low and we charge your saved card, you get an email confirming the amount and how much of your monthly top-up limit you've used. If the card is refused we tell you that too, back off instead of retrying every minute, and switch auto top-up off after repeated failures rather than trying forever. Reaching your own monthly limit is announced once, not on every run.
• A low balance recharges whatever you were doing. Auto top-up used to be checked only before workflows and chats; credits spent through the wizards and vector search could empty a balance without ever triggering a recharge.
• Fixed: with auto top-up switched on, the run that emptied your balance was refused anyway — and sent a "credits depleted" email — seconds before the card was successfully charged. It now waits for the top-up and carries on.
• Fixed: two things running at once could both charge your card for the same top-up.

2026-08-08

• The desktop app is now a free download for everyone. The download page no longer asks you to sign in or hold a paid plan — anyone can install the app and use it as a full code IDE: their own projects and files, terminals, and their own command-line coding agent. Paid plans add cloud AI, workflows that run in the cloud, saving Circuitry documents to your own disk, connecting your other machines, collaboration, and the iPad app.

2026-08-01

• Coding-agent replies start sooner, and stay quick as a conversation grows. Every message to a coding agent was preparing a large block of background information that the agent never receives, and re-sending the whole conversation to a tool that already remembers it — so a chat got steadily heavier the longer you talked. Both are gone: the material sent with each message now stays the same size from your first question to your fiftieth.
• No more pause before a coding agent starts. On a workflow, each message first asked a separate cloud model to work out which part of the canvas you meant — several seconds of waiting before your own agent was even given the message. Coding agents work this out themselves, so the wait has been removed. Chats using a cloud model are unchanged.

2026-07-26

• Turn text into editable letter shapes. Edit → Convert Text to Paths replaces a text object with a group of shapes, one per letter, with the counters — the hole in an 'o', the two in a 'B' — kept as real holes. Ungroup it and you can reshape a single serif point by point, colour half a word differently, or hand artwork to someone who doesn't have your font. Colour, opacity, effects, position, size, stretch and rotation all carry over, so the shapes land exactly where the letters were. It's one-way — undo restores the text — and text flowed along a curve has to be detached from the curve first.
• Text now takes part in combining and masking, with nothing to prepare. Select a word and a shape and choose any boolean operation: the letters are outlined for you behind the scenes. The Combine button used to refuse a selection containing text.
• Fixed: "Convert to Outlines" did nothing. The right-click item on a text object reported no error and made no change. It now works, and it's the lighter-touch alternative to Convert to Paths — the words stay fully editable and their outlines are recorded alongside, which is what lets an SVG export match your screen on a machine without your font installed.
• Clearer icons for the boolean operations. Unite, Subtract Front, Subtract Back, Intersect, Exclude Overlap and Divide now show the two-overlapping-squares picture used across design tools, with the part you'll keep filled in — so you can tell them apart without reading the labels. Help pages show the same icons.
• Stroke options — dashes, ends and corners. Select a shape, a line, or a path and the Style panel now has a Line Style section: dashed, dotted, dash-dot or long-dash patterns with a spacing control; flat, round or square line ends; and sharp, round or bevelled corners (with a sharpness limit for very tight angles). Dash lengths follow the line's thickness, so a pattern still reads as dashed whether the line is a hairline or a heavy band. Everything you set is kept when you export to SVG. Freehand pen strokes don't have these — they're drawn as ink, not as a line with a width.
• A help page for the Style panel. The panel that holds thickness, colour, fill, opacity, effects and now line style had never been documented. There's now a full page covering where to find it in each editor, what every row does, and how it behaves with several objects selected or with a group.
• Type exact sizes and positions. With something selected, Edit → Transform… opens a small panel with X, Y, width, height, and rotation. Type a value and the object changes as you type, so you can nudge a shape onto a precise size or line two things up to the pixel without hunting with a handle. The link button between width and height keeps the proportions, and rotation turns the selection by the number of degrees you enter, around its own centre.
• The panel stays out of your way. It opens beside whatever you selected rather than on top of it, and it doesn't dim, blur, or block the canvas — you can watch the object change while you type. Drag it by its title bar if it's still in the way. Available on the whiteboard, in notepads, in workflows, and in the Designer.
• Fixed: undo didn't undo. Resizing an object, clipping an image's transparent edges, or combining shapes could leave you unable to undo the change — and a single Transform edit could need several presses. One edit is now one press of Undo, everywhere.

2026-07-25

• Combine shapes (boolean operations). Select two or more objects and combine them into a single new shape: Unite, Subtract Front, Subtract Back, Intersect, Exclude Overlap, and Divide. If you know these as boolean or pathfinder operations, that's what they are — they are labelled both ways. Unlike grouping, which keeps your objects and moves them together, combining replaces them with real new geometry you can carry on editing point by point, and holes are genuine holes: cut a circle out of a square and you get a ring that keeps its hole when you move it.
• Subtract works in both directions. Which shape survives is decided by what's in front of what, so if the result comes out the wrong way round you don't need to restack anything — Subtract Front keeps the shape underneath, Subtract Back keeps the one on top.
• Reach it three ways on the same selection: the Combine (Boolean) button on the toolbar above the canvas, Edit → Combine Shapes (Boolean) in the menu, or the right-click menu. Available on the whiteboard, in notepads, in workflows, and in the Designer.
• Icons and vector images are converted for you — stamp a star icon over a rectangle, choose Subtract Front, and you get a star-shaped bite without converting anything by hand first. Pen and brush strokes combine by the line you actually see. Photos and editable text are left alone. The combined shape keeps the front object's colours and stays where it was in the stack.
• Fixed: Copy, Copy as Image, Save as Image, and Paste did nothing in the Designer. All four silently ignored your selection. Clipping an image's transparent edges in the Designer also reported success while discarding the result.
• Fixed: opening the File or Edit menu could crash the editor on some documents when objects were selected.
• Fixed: menu items with a submenu were unresponsive in the desktop app and on iPad.
• Vector export. Your artwork can now leave Circuitry as SVG, so it opens in any other design tool at any size. File → Export Screens… in the Designer offers SVG alongside PNG, JPEG, WEBP, and HTML — for the current artboard, all of them, or a hand-picked set — and can save to your downloads, a connected Circuit, or a folder on this computer. The Designer's toolbar also has a one-click vector button that opens straight to SVG.
• Export just a selection. Pick a few objects and press SVG in the toolbar above the canvas to download only those, cropped to their own edges — handy for handing a single logo or icon to someone. On the whiteboard and in notepads, File → Export Selection as SVG… does the same thing; these editors could not export vectors at all before.
• What comes across: shapes stay real shapes, pen and brush strokes keep the pressure and taper you drew, gradients and shadows carry over, pictures are embedded so the file stands alone, and text stays editable text (convert type to outlines first if you need it to look identical on a machine without the font). Objects with 3D depth export as their flat outline, since vector files have no notion of depth.
• Fixed: the Designer's "Export as SVG" button did nothing. It was a placeholder that silently no-opped. It now works.
• Sharper drawings in exported web pages. When a design is exported as HTML, the drawn artwork embedded in the page is now rendered properly — previously most objects came out as thin hairline outlines that lost their shape, fill, and thickness.
• Help updated. Every editor tour now documents the toolbar that appears when you select something on the canvas, which the tours had never covered, plus the new export routes.

2026-07-18

• Stronger sign-up protection. Creating a free account now includes a quick automatic human-verification check (invisible for almost everyone), and the sign-up form no longer accepts throwaway variations of an email address that already has an account. This stops the automated fake sign-ups that were sending unwanted verification emails to real people's addresses.

2026-07-16

• Editor tours in the help. A new "Editors" section in the docs gives every editor a guided tour — Whiteboard, Workflow, Designer, Code IDE, Notepad, Chat, CodeBook, Spreadsheet, Web pages, 3D scenes, Terminal, and Browser — each showing the real screen, every control with the exact icon it wears in the app (including the pen tray's actual implements), verified keyboard shortcuts, and what each editor is best at. A companion "Selection Toolbar" page explains the button row that appears above the canvas whenever something is selected. The Workflow tour walks five real scenes: a batch image pipeline run, Python nodes with breakpoint debugging, input-aware node wizards, the Plugins Library, and AI-drawn flowcharts.
• Help fixes. The keyboard-shortcuts reference was rewritten to match the app exactly (temporary pan is Hold Shift — Space opens the node picker; many missing shortcuts added), the iPad gestures page no longer lists gestures that don't exist, and the getting-started guides now agree on how nodes connect (from any edge, with automatic routing).
• Keyboard navigation for tabs and split-screen panes. Cycle editor tabs with Cmd+Option+Right / Left (Mac) / Ctrl+Alt+Right / Left (Windows / Linux) and move focus between split-screen panes with Cmd+Shift+Option+Arrow (Mac) / Ctrl+Shift+Alt+Arrow (Windows / Linux) — both also in the View menu. Together with the existing arrow-key node navigation (arrows move between connected nodes, Enter edits, Esc steps out), the whole workspace is now reachable without the mouse.
• Menu keyboard shortcuts work again. Shortcuts shown next to View-menu items (Full Screen and others) quietly did nothing when pressed; the menu click always worked. Fixed — pressing the shown combination now triggers the menu action.
• Vim mode. Turn on Vim keybindings for every code editor in the app — code files, workflow node editors (Code, Agent, Data Viz, Code File, Params, Database, Web), docked side panels, notebook cells, page-source editors, and 3D scene code. Enable it in Settings → Code Editing or toggle from anywhere with Cmd/Ctrl+Shift+V. A slim status bar in each editor shows the current mode and follows the editor's light/dark theme. In workflow nodes, Esc is mode-aware: it leaves insert/visual mode first, and only exits the editor when pressed again in normal mode. Off by default. See the Vim Mode guide.

2026-07-11

• Pinch-zoom on the workflow canvas is smooth again on iPad. A recent change to touch handling made pinch-zoom process far more updates than the screen could show, so zooming a busy canvas stuttered badly (while panning stayed smooth). Pinch now updates once per frame, restoring full speed — including on Designer, Notepad, and chat flows.
• Panning a large canvas no longer re-loads nodes that scroll off-screen. Code and image nodes used to reset when they left the view and came back; they now stay put for normal-sized canvases.

2026-06-11

• Resolve import placeholders automatically. Placeholder nodes left by an import can now be converted into working nodes: Circuitry matches them against its Integrations Gallery (one click swaps in the matching operation with settings pre-filled), and an AI pass rebuilds the rest using a model you pick — including local and CLI models. Use Open & Resolve right after an import, or right-click a placeholder → Resolve Placeholder…. Everything resolved is flagged for review before you run.
• Import your work from other tools. A new File → Import… dialog converts files exported elsewhere into native Circuitry documents: n8n workflows, Make (Integromat) blueprints, Node-RED flows, Langflow flows, and Flowise chatflows become workflows; Excalidraw scenes become notepad drawings; Jupyter notebooks (.ipynb) become CodeBooks; and SVG files or Figma files (via file link + personal access token) become Designer screens. Imports are best-effort: steps without a Circuitry equivalent become clearly marked placeholder nodes that keep their original settings and wiring, and an import report shows what mapped cleanly, what needs review, and which service connections to set up again. See the Import guide.

2026-06-08

• Scheduled (timer) workflows now run in the cloud. A workflow with a Schedule start node set to cloud hosting now fires automatically on its timer — no need for an always-on Circuit. Set it up with a friendly picker (every few minutes, daily at a time, weekly on chosen days, monthly on a day) instead of writing cron by hand, pick your timezone, and see the next few run times before you deploy. There's also a Run on schedule now button to test the flow immediately. Advanced users can still enter a raw cron expression.
• Updated Terms of Service (v1.3). We've clarified that Circuitry and its outputs may not be used to train competing AI models or build a competing product, that automated scraping of the app isn't permitted, and that third-party names and logos shown on integrations belong to their owners and don't imply any partnership. You'll be asked to review and accept the updated terms next time you sign in.

2026-06-06

• Inspect incoming webhook requests. Webhook start nodes now have a Listen for request button (and right-click menu item). Arm it, trigger your webhook from your other app, and the node lights up and captures the request’s payload so you can see its structure and build the rest of your flow against real data. The workflow itself doesn’t run while you’re just listening.
• The webhook URL now matches where you’ve chosen to host it — pick a Circuit and you’ll see that server’s address instead of the cloud URL.

1.0.0-beta.1 — 2026-06-04

• The editor now checks that a connected Circuit is compatible: it shows a banner when an update is available and blocks running workflows on a Circuit that's too old, with a clear prompt to update.