Expand description
agents tasks schedule — register a command + interval (or
oneshot) in tasks.sqlite. Add-only leaf; the runner that
actually fires schedules is follow-up work tracked by #216.
Schedule per row:
command: argv vector to invoke on each scheduled poll.interval_seconds:Some(n)for a recurring schedule withnseconds as the floor between invocations;Nonefor a oneshot that the runner fires once on the next poll and deletes the row. The CLI gates this via mutually-exclusive--interval <humantime>/--oneshotflags.- The caller’s full
AgentArgumentssnapshot — captured by the CLI handler so the runner can re-install identity env vars at fire-time.
Modules§
Structs§
- Args
- Command
- Request
- Response
- The created schedule’s user-facing identity: its
--name, the caller hierarchy it was registered under, and the version this call minted (1on first creation,max + 1per--overwrite— each version is its own row; older versions are shadowed but kept for per-version run history).