Skip to content

Your lightweight open-source personal agent.

docs(automations): keep Markdown paragraphs on one line

chengyongrud076e4ef13ab
diff --git a/AGENTS.md b/AGENTS.md
index 259c2afb5..d85d4aafb 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -20,3 +20,4 @@ The Python gateway owns agent execution, sessions, tools, memory, and security p
- Analyze the required behavior, state ownership, and root cause before extending existing code. Refactor when the structure causes the problem; a smaller diff does not justify another fallback.
- Do not add defensive tests for hypothetical internal states or unsupported combinations. Each new test needs a reachable path and a meaningful contract to protect.
- Do not run `ruff format`; mechanical formatting obscures git blame and creates unrelated diffs. This constraint takes precedence over the optional touched-file formatting in `CONTRIBUTING.md`.
+- Do not manually wrap prose in Markdown files. Keep each paragraph on one source line; use line breaks only for Markdown structure.
diff --git a/docs/automations.md b/docs/automations.md
index 0746a1f4e..d77028fd7 100644
--- a/docs/automations.md
+++ b/docs/automations.md
@@ -46,17 +46,9 @@ Write what the task should do, such as "Remind me to drink water". nanobot sends
For separate sends, specify the recipients in the instructions. The agent can still use `message` to send to other chats, send to several recipients, or attach files. Existing tasks that explicitly request this tool remain supported.
-Writing "send to WhatsApp" in the instructions does not change the task's saved chat. Its normal
-reply still returns to that chat. A separate send requires the agent to call `message` with the
-other destination.
-For a fixed destination, create the task in that chat or use
-[Change the Chat for a Scheduled Task](#change-the-chat-for-a-scheduled-task). Keep explicit
-`message` instructions when you want separate sends or several recipients.
-
-If a result does not arrive, check the saved chat and the run's `message` calls first. Then check
-the gateway's channel send errors. `Turn completed` confirms execution finished, not that the
-destination received a message. A successful `message` tool return confirms queue acceptance,
-not receipt by the chat service. Do not resend until you check whether the first send arrived.
+Writing "send to WhatsApp" in the instructions does not change the task's saved chat. Its normal reply still returns to that chat. A separate send requires the agent to call `message` with the other destination. For a fixed destination, create the task in that chat or use [Change the Chat for a Scheduled Task](#change-the-chat-for-a-scheduled-task). Keep explicit `message` instructions when you want separate sends or several recipients.
+
+If a result does not arrive, check the saved chat and the run's `message` calls first. Then check the gateway's channel send errors. `Turn completed` confirms execution finished, not that the destination received a message. A successful `message` tool return confirms queue acceptance, not receipt by the chat service. Do not resend until you check whether the first send arrived.
For background checks that should stay quiet unless there is something useful to report, use heartbeat instead of a user-created scheduled automation.
@@ -66,26 +58,13 @@ An upgrade does not overwrite your workspace's `AGENTS.md` or convert existing h
### Scheduled Result Delivery
-The gateway saves final scheduled messages before it accepts them into the outgoing queue.
-This includes explicit `message` calls in existing tasks. Each recipient has a separate delivery
-record. Progress, reasoning, and streaming events do not enter this queue. WebUI streaming and
-saved chat history keep their existing behavior. External channels receive a complete scheduled
-reply instead of a streamed reply. Ordinary chat streaming is unchanged.
+The gateway saves final scheduled messages before it accepts them into the outgoing queue. This includes explicit `message` calls in existing tasks. Each recipient has a separate delivery record. Progress, reasoning, and streaming events do not enter this queue. WebUI streaming and saved chat history keep their existing behavior. External channels receive a complete scheduled reply instead of a streamed reply. Ordinary chat streaming is unchanged.
-The queue cannot recover a send that the agent never requested. If an expected recipient has no
-delivery record, check the task's saved chat and the run's `message` calls first.
+The queue cannot recover a send that the agent never requested. If an expected recipient has no delivery record, check the task's saved chat and the run's `message` calls first.
-If a channel reports that it has not sent any part of a message, the gateway retries every
-30 seconds, for up to one hour after queue acceptance. It sends the saved message to the saved
-destination. It does not run the task or call the model again. A gateway restart resumes pending
-messages. Deleting or resetting the source chat cancels pending messages from that chat generation.
-Disabling a channel prevents its pending messages from being sent. Changing, pausing, or deleting
-a task affects future runs; it does not redirect or recall an already queued result.
+If a channel reports that it has not sent any part of a message, the gateway retries every 30 seconds, for up to one hour after queue acceptance. It sends the saved message to the saved destination. It does not run the task or call the model again. A gateway restart resumes pending messages. Deleting or resetting the source chat cancels pending messages from that chat generation. Disabling a channel prevents its pending messages from being sent. Changing, pausing, or deleting a task affects future runs; it does not redirect or recall an already queued result.
-If a request times out after sending starts, or the gateway stops during a send, delivery is
-unknown. The gateway does not retry that message automatically: the service might already have
-accepted it. Check the destination before sending the result again. This is not an exactly-once
-delivery guarantee. Adapter or service-specific retries still follow their own protocol.
+If a request times out after sending starts, or the gateway stops during a send, delivery is unknown. The gateway does not retry that message automatically: the service might already have accepted it. Check the destination before sending the result again. This is not an exactly-once delivery guarantee. Adapter or service-specific retries still follow their own protocol.
Look for `Channel delivery` in the gateway log. The run ID links execution to each delivery ID:
@@ -96,13 +75,7 @@ Look for `Channel delivery` in the gateway log. The run ID links execution to ea
| `failed` | Not sent: expired, disabled channel, replaced source chat, or rejected destination/policy |
| `unknown` | An interrupted or failed attempt might have reached the service; no automatic retry |
-The queue is stored in `delivery/outbox.sqlite3`, beside the active config file. Include this
-directory in instance backups; stop the gateway before copying it. It holds at most 256 pending
-messages, with a 1 MiB serialized limit per message. A full queue or storage error rejects the
-enqueue operation instead of reporting it as accepted. Terminal records discard message text
-and keep status for up to seven days, capped at 1,000 records. Existing job and session files
-are not converted. Older versions ignore this queue. After an upgrade, pending messages can
-resume only within the original one-hour limit.
+The queue is stored in `delivery/outbox.sqlite3`, beside the active config file. Include this directory in instance backups; stop the gateway before copying it. It holds at most 256 pending messages, with a 1 MiB serialized limit per message. A full queue or storage error rejects the enqueue operation instead of reporting it as accepted. Terminal records discard message text and keep status for up to seven days, capped at 1,000 records. Existing job and session files are not converted. Older versions ignore this queue. After an upgrade, pending messages can resume only within the original one-hour limit.
## Local Triggers