The fastest, cheapest, most efficient open-source agent harness. Run more than 500 agents on a $10 VPS.
Cron tools
Agent-facing tools over the cron domain. Six per-operation tools
(add.rs, list.rs, update.rs, remove.rs, run.rs, runs.rs) are the
implementation; collapsed.rs wraps them into a single action-dispatched
CronTool. The cron tool types are re-exported from crate::cron::tools; tools/ops.rs
assembles the registered tool set.
The cron-domain tools first check config.cron.enabled and return an error
result when cron is disabled. The separate schedule tool exposes its own
one-shot and recurring schedule actions.
Registration state
crate::tools::ops::all_tools registers CronTool as the compact, advertised
scheduler surface, plus the six per-operation tools as hidden aliases behind
it. Each per-operation tool reports ToolExposure::Hidden (fn exposure),
which tools/impl/meta/tool_search.rs strips from the advertised catalogue,
so they stay dispatchable by name (replayed transcripts, saved skills,
user_filter.rs family cron, toolpack scheduling) without cluttering the
model's tool list with six near-duplicate schemas.
Collapsed dispatch (collapsed.rs)
CronTool (CRON_TOOL_NAME = "cron") advertises one schema with an action
field (list / add / update / remove / run / runs) instead of six
near-duplicate schemas: four of the six take only job_id. Each action
forwards to the matching per-operation tool through
tinytools::collapse (merge_action_schemas,
resolve, args_without_action), so schedule parsing, the SecurityPolicy
check and delivery validation live in exactly one place.
permission_level_with_args / external_effect_with_args resolve the real
per-action answer once action is known; with a missing or unknown action
they fall back to the strictest member (Execute, shared by add / update
/ run) and true, so an unparseable call over-restricts rather than under-.
The argument-free permission_level / external_effect report the same
strictest values.
Per-operation tools
| Tool | Name | Permission | external_effect |
Delegates to |
|---|---|---|---|---|
CronAddTool |
cron_add |
Execute |
true |
cron::add_shell_job / cron::add_agent_job |
CronListTool |
cron_list |
trait default (ReadOnly) |
trait default (false) |
cron::list_jobs |
CronUpdateTool |
cron_update |
Execute |
true |
cron::update_job (after SecurityPolicy::is_command_allowed on patch.command) |
CronRemoveTool |
cron_remove |
Write |
true |
cron::remove_job |
CronRunTool |
cron_run |
Execute |
true |
cron::get_job + Schedule v6 manual worker lifecycle; the module owns run history and completion |
CronRunsTool |
cron_runs |
trait default (ReadOnly) |
trait default (false) |
cron::list_runs (output truncated to MAX_RUN_OUTPUT_CHARS = 500) |
The mutating tools (add, update, remove, run) set
external_effect = true so ApprovalGate::intercept runs even for turns that
originate from an inbound channel message (GHSA-f46p-6vf9-64mm): they persist
or immediately execute a stored command or agent prompt on the host.
CronAddTool details
- Args:
name(derived as a slug ofpromptwhen omitted),schedule(kind: cron | at | every),job_type(shell|agent, inferred from the presence ofpromptwhen omitted),commandorprompt,session_target(SessionTarget, defaultIsolated),model,delivery,delete_after_run(defaults totrueforatschedules). - Shell commands are checked with
SecurityPolicy::is_command_allowedbefore being scheduled. - Agent jobs default to
DeliveryConfig { mode: "proactive", best_effort: true, .. }.validate_deliveryonly inspectsmode: "announce": it requireschannelandto, exemptsweb, rejects an unconfigured channel, accepts anytowhen the channel'sallowed_usersis empty, and otherwise requirestoto be in that list: this blocks scheduling a cron whose output is delivered to an arbitrary chat id (#928). JobType::Flowis unreachable through this tool (flow-schedule rows are created internally byflows::ops::flows_set_enabledviacron::add_flow_schedule_job); the arm returns an explicit error instead ofunreachable!()in case thejob_typeheuristic above ever changes.
Related
crondomain:../README.md: job/run model, scheduler, delivery modes, agent-job minimum interval.schedule.rs: the separatescheduletool for recurring and one-shot jobs; it is not part of the collapse above.crates/openhuman-core/src/tools/impl/meta/collapse.rs(module pathtinytools::collapse): the generic action-collapsing helpercollapsed.rsbuilds on.- Cron and scheduling
Tests
add_tests.rs, list_tests.rs, update_tests.rs, remove_tests.rs,
run_tests.rs, runs_tests.rs cover each per-operation tool;
collapsed_tests.rs covers the merged schema, per-action versus fallback
permission levels, the unknown-action error, and that every member is
Hidden.