Scheduling coding agents with Open Run

A coding agent can help with a repeatable task, but someone still needs to say what should happen, where it should happen and how to check the result.

Open Run is my project for scheduling that work on a local machine. It uses coding-agent CLIs and connects their runs to projects, triggers, conversations and Git changes.

A schedule needs a precise instruction

“Improve the project” leaves too many decisions open for an unattended run. A smaller instruction gives the result a clearer shape.

For example:

Inspect the failing date-formatting test. Explain the cause, make the smallest correction and run the relevant test. Leave the change available for review.

This is an example task, not a guarantee that the agent will fix it. Its value is that the goal, scope and verification step are visible.

Keep execution separate from acceptance

A run can produce a change without deciding that the change belongs in production.

The diff is the bridge between the agent’s work and a developer’s judgment. The developer should be able to see which files changed and whether the checks relate to the original problem.

A successful process exit alone does not establish that the application behaves correctly.

A local schedule has real operating conditions

The machine must be awake and the worker must be running for a schedule to fire. The selected CLI also needs to be available and configured.

Open Run does not require model API keys itself, but its agent CLIs still use their own subscriptions or provider configuration. “Local” describes where the orchestration runs; it does not mean the selected agent performs every model operation offline.

Make the history useful

The history of a run should help answer a few practical questions: what was requested, which agent ran, what changed and what was checked?

That is the reason I care about connecting instructions, conversations and diffs. It makes repeatable work easier to follow when someone returns to it later.

Read the Open Run repository for current commands and runtime details, or visit the project overview.