August 2026

Type @ in an agent chat and a list of the conversation's workspace files appears. Pick one and its full path is inserted into your message, so you can point the agent at a file without typing the path out. Arrow keys move through the list, Enter or Tab accepts the highlighted file, and Esc closes it.

You can also delete files now. Each row in the Files menu has a trash button that asks you to confirm on the row itself before the file is removed from the workspace.

Every agent on a workflow now has a Linux sandbox with a shell, whether or not you have wired a filesystem node to it. The sandbox starts the first time the agent actually runs a command, so an agent that only ever answers in chat never starts one. In a chat, the agent's /workspace folder is kept per conversation and survives across runs.

A test run answers shell commands with made-up output like every other tool call, so a rehearsal never starts a real sandbox.

The AI builder can look things up for itself while it builds too. Paste an API URL or a sample payload and it can fetch the URL and inspect the real response instead of wiring a node blind. It has no access to your connected accounts while it does this.

You can now upload files into a workspace yourself, so the agent finds them there on its next turn. In an agent chat, use the upload button in the Files menu header, and the files land in that conversation's workspace. In a filesystem node's config panel, use Upload in the file browser, and they land in that node's volume.

Every page under noclick.com/agents now has a Setup section under the hero that walks the whole path before you commit to it: choose whether the agent runs On your computer or In the cloud, pick what it can do in each app, then sign in to each app once.

The last step follows your choice. On your computer ends on the exact command that connects your coding agent to NoClick, shown with a placeholder link because setup mints the real one. In the cloud ends on signing in to the coding agent NoClick runs for you.

Click Test in an agent's chat header to run it against a staged event. Your real agent runs on your real model and prompt, but every tool call it makes is answered with made-up data, so nothing reaches your accounts and nothing is sent. The screen says so up front, and every answered call carries a simulated pill.

Gmail, Slack, WhatsApp, and Telegram triggers ship written situations to test against, and every other trigger gets an editable sample. You can rewrite the staged message in place, keep several named runs per agent, and share a finished run as a read only page anyone can open.

A photo, voice note, or document sent to a WhatsApp-triggered agent now arrives as a link the agent can download, along with the file type and name. The message caption comes through as the text. Media used to reach the agent as a placeholder with nothing behind it.

• Files up to 25 MB are saved to your workflow's resources at the moment the message arrives, so the link keeps working for the whole run.
• Larger files, and files the provider no longer holds, are reported to the agent as media it could not retrieve, so it can ask the sender to resend instead of guessing.
• Nodes wired downstream of the WhatsApp trigger read the same link from the trigger output.