Run prompts on a schedule

Save recurring prompts with cron rules and an explicit timezone. The controller runs them without an open console, in a new session or in the sessions you choose. A run against a frozen session thaws it, waits until it is ready and then delivers the prompt.

Every run rechecks the creator’s current membership and target permissions; a saved schedule keeps no access that was later revoked. An accepted dispatch is not a completed answer, and disabling future runs does not stop work that was already accepted. The existing walkthrough does not show this screen.

How it works

  1. Choose the timing

    Enter cron rules directly or describe the timing to Control Room, then inspect the normalized rules and timezone before saving.

  2. Choose the target

    Target a new managed session, the authorized sessions of a repository or Project, or an explicit set. Choices are grouped by project with running sessions before frozen ones; ended sessions are hidden.

  3. Read the actual outcome

    Run history separates dispatch, execution, results and reported token usage. Quota and thaw failures are reported separately; missing usage stays unknown.

  4. Run a schedule now

    Run now (Shift+R), devctl schedules run-now or the run_schedule_now MCP tool starts one manual run of an enabled schedule through the same permission checks, delivery and history as a timed run. The next timed run is neither moved nor skipped.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.