August 2026
Everything that changed in NoClick in August 2026.
Improvements and fixes1
A node's Credentials tab no longer opens a QR code when you already have a WhatsApp connection to pick. It offers a Connect a different WhatsApp number button instead, so a spare code does not invite a re-scan you did not need. A code still appears on its own when you have no WhatsApp credential yet, or when the one attached to the node has dropped and the scan will reconnect it.
Run results read as a story
The popup that opens when a run finishes now walks through the run in reading order instead of listing node outputs one at a time. What came in shows the event that started the run in its own app's frame, so a WhatsApp message looks like a WhatsApp message and an invoice looks like an invoice. What the agent did lists the agent's tool calls with the time each one took and the detail that matters on the row, such as the channel a message went to, and any row opens to show what it was Called with and what it Returned. What went out frames each message the agent sent the way its destination shows it. An agent that worked and chose to send nothing says so in its own words, and a failed run shows the error with a way to fix it instead of a verdict.
The run switcher at the top of the popup reads Latest run and opens your run history: each row has its status, what fired the run, how long it took, how many nodes ran, and the error on runs that failed. It stays reachable while a run's results are still loading and on a workflow that has never run, so history no longer dead-ends.
Uploads show how far they have got
Every place you upload a file now shows a percentage and a progress bar instead of a spinner: interface blocks, form file fields, the agent chat composer, the filesystem node's file browser, the chat Files menu, and the media pickers in a node's config panel. An upload that fails says why on its own row.
A single file can be up to 100 MB everywhere, workspace uploads included.
Named inputs work as plain variables in JavaScript
In the Serverless Function node, an input named data is now just data in your JavaScript, the way it already was in Python. inputs.data still works, and your own const data = ... still takes precedence. Code the AI builder wrote against the documented input names used to stop with ReferenceError: 'data' is not defined.
Improvements and fixes2
The AI builder and your agents now know the public URLs your workflow already has. Ask either one for the address of a published app or a hosted MCP server and you get the live link instead of being told the node has no URL. The builder mints the MCP link if the node does not have one yet, and asking an agent only reads what exists.
The blog at noclick.com/blog opens on the three newest stories, then lists the full archive, with topic filters and search.
The home page runs the product
The home page at noclick.com now shows three parts of NoClick working, in order: an agent handling messages from the apps you already use, the builder turning a prompt into a workflow, and the run record showing every tool call and result afterwards. Each one is the real interface, not a picture of it.
Below them is the list of what NoClick can do and one Start Free button.
Improvements and fixes3
The home page opens on a new animated hero. The prompt box is still the first thing on it, so you can describe the work you want done and start building from there. The footer that runs across noclick.com now groups its links by product, the coding agents you can run an agent on, community, and legal.
Signing in and creating an account have been redesigned, both as full pages and as the panel that opens when you do something that needs an account. The ways in are unchanged: Google, an email and password, or your company's identity provider.
Agent template pages and the pages at noclick.com/agents share a new layout. On a template page, the sections you scroll through are the same, and the agents suggested at the bottom now show each workflow's real canvas, the preview the gallery cards use.
Improvements and fixes2
Running a template's staged conversation from its page works while you are signed out, including for templates whose agent runs on a coding CLI. Those runs use the NoClick default model, since the template ships no key of its own.
The error page has been redesigned, with clearer actions to open your dashboard, reload, or go back, and a stack trace you can show and hide.
Templates hand you a guided setup
Template pages are now built around the agent. Each one previews the real canvas, lists the services setup will ask you to connect and the questions it will ask, and shows the staged conversations the template ships so you can see the agent work before you take a copy. Click Use this agent and your copy opens straight into full screen setup. The gallery is now Agent Templates.
Improvements and fixes2
A dropdown that loads its options from a connected account now fills itself when the account offers exactly one choice, so a workspace with a single project or calendar stops asking.
Starting from an agent page asks where the agent should run and what it can do in each app before you create an account, and the choices carry into your workspace.
Improvements and fixes1
The indicator that shows the AI is working is now an animated orb, and it reflects the work in progress as the builder reads schemas, adds nodes, and connects them.
The agent interface fits narrow screens
The agent chat in a workflow's Interface tab now lays itself out from the width it actually has, rather than the width of the window. When something else takes up the screen, like the builder drawer or a split view, the chat keeps its full width and Settings opens as a sheet over it instead of splitting the row.
- History, Files, Share, and Settings in the chat header collapse to icons when the header is too narrow for their labels.
- The History, Files, and model pickers open as full-width sheets on phones instead of cramped dropdowns.
- Tablets in portrait use the single-column tab layout, so the navbar and canvas are no longer squeezed into a sliver.
Find an agent's triggers and tools by what they do
The Add trigger and Add tool palettes on an agent node now search each service's description, its aliases, and the actions it can perform, not just its name. Searching for "schedule", "timer", or "every day" finds the Schedule trigger, and "create issue" surfaces Linear, Jira, and GitHub.
Services also carry the same name here as on the canvas. Schedule used to be listed as "Trigger Cron" and X as "Twitter", and about a third of the catalog appeared under a name that did not match the one you see everywhere else. Once you pick a service, its list of triggers is searchable by keyword too.
Improvements and fixes1
Expressions written in another automation tool's syntax are now rejected when the AI builder or an MCP client saves them, with a message showing the NoClick form. Accessors like
$input,$node[...], and.item.jsonafter$('node')used to save without complaint and then fail every run.