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 plans and implements 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. The page shows:

• Status — planning, awaiting your approval, building, waiting on you, awaiting merge, merged, failed, or cancelled — plus the branch name.
• A push notice if the run’s work could not be pushed to GitHub. This is treated as a real failure, not a background detail, and is shown at the top of the page rather than buried in the activity feed.
• The plan — the steps the run intends to take. When a run is awaiting your approval, an Approve plan action starts the build.
• Tasks — each step of the plan, collapsed by default. Expand a task to see that step’s own activity, its result, and (while it’s running or pending) a Cancel this task action. Cancelling a step that hasn’t started yet skips it and the run continues with the next one. Cancelling a step that is already running stops it immediately — its sandbox is destroyed, so anything that step had not already checkpointed is discarded — and the run then waits on you rather than starting the next step.
• Activity — the run-level narrative: questions, your replies, and anything the run wants you to know.

Steering a run

The message box at the bottom sends text to the run. What happens to it depends on the run’s status:

• If the run is waiting on you (parked on a question), your reply resolves it and the run continues.
• If the run is building, your message is queued — it does not interrupt the task in progress. It’s folded in at the next task boundary.

Cancel run stops the whole run and destroys its sandbox. Work already checkpointed stays on the branch; anything the step in flight had not finished is discarded.

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.