A home for recurring agent work.
We are exploring scheduling and event triggers for agent jobs: recurring work, webhook-driven tasks, and a clear view of what should run next. Execution targets and delivery behavior are still being designed.
Scope is subject to change. No public release or API is announced.
Plan the next run and understand the last one.
The concept combines time-based schedules with event-triggered work. A schedule would identify a job and its execution target; an event rule would define what starts it. Time zones, missed runs, retries, and duplicate events need explicit behavior.
1. Describe a recurring job or an incoming event. 2. Choose the execution target and timing rules. 3. Review runs and adjust or pause the schedule.
Schedule. Trigger. Manage.
We are exploring the controls teams need to run recurring agent work predictably.
Time-based jobs
Explore recurring schedules with explicit time zones and missed-run behavior, from hourly checks to weekly maintenance.
Events and webhooks
Explore event rules that start agent work when something changes. Supported sources, authentication, and duplicate handling remain to be defined.
Visibility and control
Explore a shared view of schedules, upcoming work, and past runs, with controls to pause or remove a schedule.
Building blocks for agent jobs.
These products address compute, work coordination, session records, and memory. A cron9 integration is not available today.
Sandboxes
Create Boxes, execute commands, and fork filesystem snapshots with run9.
run9 → task9Task coordination
Create shared tasks that workers can claim, update, and complete.
task9 → owl9Session records
Capture and review native transcripts from supported agent runtimes with collection enabled.
owl9 → mem9Agent memory
Store and retrieve context for agent workflows through mem9’s memory interfaces.
mem9 →What should your agents run next?
Tell us about the schedules, event sources, and execution targets your workflows need.