The fastest, cheapest, most efficient open-source agent harness. Run more than 500 agents on a $10 VPS.
Rust agent-orchestrationai-agentsai-assistantdesktopllmlocal-firstmcppersonal-aiprivacyrustsecond-braintauri
docs(cron): clarify schedule tool scope
Steven Enamakelcddbea25cbe4
diff --git a/crates/openhuman-core/src/cron/tools/README.md b/crates/openhuman-core/src/cron/tools/README.mdindex 84081df0fb..fd7d788a5d 100644--- a/crates/openhuman-core/src/cron/tools/README.md+++ b/crates/openhuman-core/src/cron/tools/README.md@@ -6,8 +6,9 @@ implementation; [`collapsed.rs`](./collapsed.rs) wraps them into a single action`CronTool`. The cron tool types are re-exported from `crate::cron::tools`; `tools/ops.rs`assembles the registered tool set.-Every tool first checks `config.cron.enabled` and returns an error result-when cron is disabled.+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 statediff --git a/docs/gitbooks/en/features/native-tools/cron.md b/docs/gitbooks/en/features/native-tools/cron.mdindex ee90b01f5b..f73c598efd 100644--- a/docs/gitbooks/en/features/native-tools/cron.md+++ b/docs/gitbooks/en/features/native-tools/cron.md@@ -18,7 +18,7 @@ Scheduling is a built-in capability. The agent can set up recurring jobs ("every| `cron_run` | Runs a job once, right now, whatever its schedule. || `cron_runs` | Shows recent run history: when, how long and what it produced. |-For "do this once at time T" cases that don't need a recurring entry, there is also a one-shot `schedule` tool in [System and utilities](system-and-utilities.md).+For one-shot or recurring scheduled tasks, there is also a `schedule` tool in [System and utilities](system-and-utilities.md).Agent jobs run a full model turn each time they fire, so they must be at least five minutes apart. `cron_add` and `cron_update` reject a tighter cron expression or `every_ms` for an agent job, and they say which two runs would be too close. For example, `*/7 * * * *` fires at :56 and again at :00. Shell jobs have no such limit.diff --git a/docs/gitbooks/en/features/native-tools/system-and-utilities.md b/docs/gitbooks/en/features/native-tools/system-and-utilities.mdindex 90e8512cfc..e77c4c6cd6 100644--- a/docs/gitbooks/en/features/native-tools/system-and-utilities.md+++ b/docs/gitbooks/en/features/native-tools/system-and-utilities.md@@ -15,7 +15,7 @@ Use the `shell` tool for Node.js, npm, and Python commands. OpenHuman uses the h| --- | --- || `shell` | Run a shell command. Output is bounded and the exit code is captured. || `current_time` | Get the current time in any timezone, with formatting options. |-| `schedule` | Do something once at a given time. For recurring jobs see [Cron](cron.md). |+| `schedule` | Create, inspect, or cancel one-shot and recurring scheduled tasks. || `pushover` | Send a push notification to your devices. || `read_workspace_state` | Inspect the current working folder: open files, recent edits, environment. || `proxy_config` | Read or change proxy configuration for outbound requests. |