Run coding agents on your own machines: runners, health, supervisors

Enroll a machine with denly login and its runners claim work outbound-only – no inbound port, no tunnel. Machines shows liveness, runner build, claim scope and sanitized diagnostics.

Machines shows liveness, the runner build, how the agent signs in, claim scope, command consent, and sanitized diagnostics. Each project runner has a scoped credential; revoking it stops future authenticated calls but does not delete the checkout or touch the machine.

Automatic sleep and wake

Current runners share one watcher on each computer. After fifteen idle minutes, project and group workers sleep automatically. The watcher stays online and starts the needed worker when a task, scheduled task, chat, or diagnostic request needs it. On a long-idle computer, detecting new work can take up to two minutes, followed by worker startup. Active work keeps running.

Sleeping means the computer is available for automatic wake. If the watcher stops checking in, the status becomes stale. Plans and repository documents stop syncing while a worker sleeps and refresh when it wakes. The computer must stay awake and online.

denly stop my-project is a manual stop: that worker stays stopped, including after an upgrade, until denly start my-project. Automatic sleep needs neither command.

Enrolling a machine needs your approval once: denly login opens a code in the browser, you confirm it, and that installation is trusted from then on. Claim scope decides what the runner picks up – only tasks assigned to you, or every actionable task in the project.

denly projects
denly doctor
denly logs my-project
denly restart my-project
denly upgrade