Accessible via: a link from Sammy, after asking it to build something

Developer Mode hands a build-shaped request — a new workflow, table, integration, or code change — to an autonomous agent run that builds it on its own branch, separate from the conversation you started it in.

Availability

Developer Mode is an internal, staged rollout. It is enabled per organisation by Hutly staff and does not appear as a toggle an owner can switch on. There is no permanent entry in the left rail — the surface only appears once your organisation has actually started a run, reached by asking Sammy to build something. Only owners and admins can start or manage a run.

Watching a run

A run is not a progress bar — it is a durable conversation you can leave and come back to. Sammy starts on the work as soon as the run begins, checks in with you when a decision is needed, and verifies its own work before it finishes. While it builds, Sammy works from the Intellia CLI’s own guides and your organisation’s inventory, and the commands that deploy the module or publish its workflows, apps and tables are refused; you deploy once Sammy has verified it. The page shows:

• Status — building, awaiting deploy, deploying, deployed, failed, or cancelled — plus the branch name.
• Questions — when Sammy needs a decision, the question appears on the page with the choices it is weighing. Your answer lets the run continue.
• Activity — what Sammy is doing right now, in plain words: reading files, editing files, running a command, or checking its work.

Steering a run

You can send Sammy an instruction at any time from the box at the bottom of the page. While the run is building, Interrupt stops what it is doing so your next instruction lands straight away.

Deploy unlocks once Sammy has verified the latest changes. If you send a new instruction after that, Deploy waits until the new work is verified too.

Cancel run stops the whole run and destroys its sandbox. Work already pushed stays on the branch.

Reloading

A dev run’s timeline is rebuilt from its own event log, so reloading the page mid-run — or coming back to it later — reconstructs exactly where things stand, with no lost history.