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): document the job-gated NO_REPLY rule
oxoxDev66ba9726a162
diff --git a/crates/openhuman-core/src/cron/README.md b/crates/openhuman-core/src/cron/README.mdindex 2d7c0e47eb..1267983cb4 100644--- a/crates/openhuman-core/src/cron/README.md+++ b/crates/openhuman-core/src/cron/README.md@@ -174,8 +174,18 @@ alerts tab and run history.| `announce` | Requires `channel` and `to`. Sends synchronously through `cron::channel_bridge::send_to_channel`; the run records `Delivered` only after the channel accepts the message, otherwise `Failed`. The `cron_add` tool checks `to` against the channel's `allowed_users`. || `origin` | Sends the reply back into the conversation that created the job ([`scheduler/origin_delivery.rs`](./scheduler/origin_delivery.rs)). Requires `CronJob.origin`. |-Origin delivery treats blank output or exactly `NO_REPLY` as `Suppressed`:-nothing is sent and no alert is raised. For a web origin, the reply is stored in+A run that has nothing to send is recorded as `Suppressed` in every delivering+mode: nothing is sent and no alert is raised. That is blank output, or+`NO_REPLY` (in any case, with `_`, `-` or a space, quoted or with trailing+punctuation) from a job whose own prompt names the `NO_REPLY` token, such as+"report new mail, otherwise reply NO_REPLY". Reminders and other jobs whose+prompt does not name it must deliver: a run that answers `NO_REPLY` or nothing+gets one corrective turn (the prompt again, plus "NO_REPLY is not allowed for+this task"), and if that still yields no message the run delivers+`Reminder: <job name>`. The token itself is never sent. Shell and flow output+is not model-written, so those jobs may always answer `NO_REPLY`.++For a web origin, the reply is stored inthe origin thread under `run_reply_message_id("cron:<job>:<run>")`, theweb-channel `proactive_message` event is emitted with that `thread_id` and`request_id`, and `append_to_origin_transcript` appends it to the thread's agent@@ -188,8 +198,7 @@ chat's in-memory history.Independently of the mode, `push_cron_alert` writes an entry into thenotifications store (the alerts tab) for any failed run, and for a non-emptysuccessful run in a delivering mode (`proactive`, `announce`, `origin`). A-`none`-mode success stays silent, and so does an origin run that chose-`NO_REPLY`.+`none`-mode success stays silent, and so does a suppressed run.### Origin and session targets@@ -214,7 +223,7 @@ The session target shapes the prompt:| Target | Prompt || --- | --- || `isolated` | `[cron:<id> <name>] <prompt>` |-| `current` | An unattended-run preamble (the reply is delivered as-is; reply `NO_REPLY` to send nothing), then a tail of the origin conversation (last 10 messages, at most 1400 characters, newest kept), then the task. Web history comes from the thread store, channel history from `channel_bridge`. |+| `current` | An unattended-run preamble, then a tail of the origin conversation (last 10 messages, at most 1400 characters, newest kept), then the task. Web history comes from the thread store, channel history from `channel_bridge`. The preamble says the reply is delivered as-is; only a job whose prompt names `NO_REPLY` is told it may answer `NO_REPLY` when its condition is not met, every other job is told to always reply with the message. || `main` | Runs like `current`; it is not yet a distinct main session. |Trust follows the origin. A job with a channel origin runs under@@ -315,10 +324,10 @@ feature) nothing loads and every cron call answers `COMPONENT_DISABLED:tinyflows| `scheduler/run_delivery.rs` | `deliver` (delivery plus completion events) and `trigger` (flow schedule trigger, system jobs). || `scheduler/failure_classification.rs` | Canned user messages and the permanent-failure classifiers that halt retries. || `scheduler/shell_job.rs` | Security-gated shell execution with a timeout. |-| `scheduler/agent_run.rs` | Agent-job turns, and `build_agent_for_cron_job`. |+| `scheduler/agent_run.rs` | Agent-job turns (with the corrective turn for a disallowed `NO_REPLY`), and `build_agent_for_cron_job`. || `scheduler/origin_context.rs` | `build_run_prompt`: the isolated prefix or the `current` preamble plus conversation tail. || `scheduler/delivery.rs` | `deliver_run` and `deliver_job`, the mode switch, and `push_cron_alert`. |-| `scheduler/origin_delivery.rs` | `deliver_to_origin`, `NO_REPLY` suppression, transcript append. |+| `scheduler/origin_delivery.rs` | `deliver_to_origin`, the `NO_REPLY` rules (`is_no_reply`, `job_allows_no_reply`, `deliverable_reply`, `fallback_reminder`), transcript append. || [`origin.rs`](./origin.rs) | `JobOrigin` capture from the live turn, the approval-gate exemption, and the turn origin a run executes under. || [`job_builder.rs`](./job_builder.rs) | `create_agent_job`: origin-aware defaults and delivery validation shared by the `cron` and `schedule` tools. || [`channel_bridge.rs`](./channel_bridge.rs) | Cron's handle on the channel runtime: per-chat history and live channels, registered by `start_channels`. |diff --git a/crates/openhuman-core/src/cron/host_delivery.rs b/crates/openhuman-core/src/cron/host_delivery.rsindex 37a461b955..9e63dc8d85 100644--- a/crates/openhuman-core/src/cron/host_delivery.rs+++ b/crates/openhuman-core/src/cron/host_delivery.rs@@ -7,8 +7,9 @@//! embedded agent's job hands its output to the host instead of writing into a//! local thread or channel: the host is told whose job it was (the profile, the//! agent, or both), which conversation the job was created in, and the job's-//! recorded origin. A run with nothing to say (blank or `NO_REPLY`) never-//! reaches it. A run with neither a profile nor an agent (the desktop's own+//! recorded origin. A run with nothing to say (blank, or `NO_REPLY` from a job+//! whose prompt allows it) never reaches it, and the `NO_REPLY` token itself+//! is never handed over. A run with neither a profile nor an agent (the desktop's own//! orchestrator) keeps the core's delivery.use std::sync::{Arc, RwLock};diff --git a/crates/openhuman-embed/src/profiles.rs b/crates/openhuman-embed/src/profiles.rsindex 72e6cf1289..96be24ddab 100644--- a/crates/openhuman-embed/src/profiles.rs+++ b/crates/openhuman-embed/src/profiles.rs@@ -167,8 +167,9 @@ impl ProfileRuntimeBuilder {/// provisioned profile once a minute for due agent jobs/// ([`ProfileRuntime::sweep_cron`]) and hands each reply to/// [`CronDelivery::deliver`] with the profile, the thread the job was- /// created in and its [`JobOrigin`]. A run that answers `NO_REPLY`, or- /// fails, is never delivered. Without one nothing is swept.+ /// created in and its [`JobOrigin`]. A failed run is never delivered, nor+ /// is `NO_REPLY` from a job whose prompt allows it; any other job always+ /// delivers a message. Without one nothing is swept.#[must_use]pub fn cron_delivery(mut self, delivery: Arc<dyn CronDelivery>) -> Self {self.cron_delivery = Some(delivery);diff --git a/crates/openhuman-embed/src/runtime/builder.rs b/crates/openhuman-embed/src/runtime/builder.rsindex 2238b650ab..6a9c69d6f6 100644--- a/crates/openhuman-embed/src/runtime/builder.rs+++ b/crates/openhuman-embed/src/runtime/builder.rs@@ -256,7 +256,8 @@ impl RuntimeBuilder {/// [`CronDelivery::deliver`](crate::CronDelivery::deliver) with the agent/// id, the thread the job was created in and its/// [`JobOrigin`](crate::JobOrigin), instead of writing into a local thread- /// or channel; a run that answers `NO_REPLY`, or fails, is never delivered.+ /// or channel. A failed run is never delivered, nor is `NO_REPLY` from a+ /// job whose prompt allows it; any other job always delivers a message./// Jobs still run only while their agent is live (the scheduler service/// must be on). It is process-wide, as the runtime is, and the core has no/// uninstall for it: it stays installed for the life of the process.