Repository navigation
Conversation
Add an early access page for chat automations: enabling the chat-automations experiment and the experiment rule kill switch, webhook automations (endpoint, bearer secret, 256 KiB JSON body, responses, single and multi use, rotation), schedule automations (cron, time zone, server previews, no catch-up, Run now), targets, When busy, the manage_automations tool and heartbeats, limits, and known risks. Register the page in the manifest, add a glossary entry, and link it from the experiments list and the built-in tools table. _Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high_ Signed-off-by: Thomas Kosiewski <tk@coder.com>
…bhook_use An occurrence that came due while the experiment was off runs late only if a 30 s scan sees the experiment on inside the 60 s grace window, so in practice the experiment must be back on within 30 s. Also note that an update request ignores webhook_use instead of rejecting it.
Drop the Prompt row from the limits table (prompts have no length cap; the request table already marks the field required) and a repeated new chat qualifier on reasoning effort. Signed-off-by: Thomas Kosiewski <tk@coder.com>
…-toggle' into tk/codagt-1216-automations-docs
…d rotate fixes Rotating the secret of a used single-use webhook now returns 409, and manage_automations never returns webhook secrets. Note that update, enable and run_now are rechecked when the change is applied. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
Docs previewCheck off each page once it's been reviewed. If a page changes in a later push, its checkbox clears automatically so it gets a fresh look. Pages not yet wired into the docs navigation aren't listed here. |
|
Manual CI run for head |
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d7709b0aa5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Keep the note on one line, declare one audience, describe off as stopping automations, show the off command output, split target steps into one instruction each, and stop promising a future endpoint path. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
…-toggle' into tk/codagt-1216-automations-docs
|
Manual CI run for head |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0bc969a2c5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Disclose that the tool can read, turn off and delete any of the owner's automations in the organization, note that turning the experiment off does not remove queued prompts, and link Run now refusals to the webhook response table. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
|
Manual CI run for head |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9b606a9cfc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Mark kind and target_mode as required, say a minute schedule can start a turn every minute, and note that chat-dependent webhook refusals are also logged. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
|
Manual CI run for head |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 34cac3a2bf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Split the schedule steps and add the organization step, make recovery after the experiment returns best effort, note silent schedule states, and limit the relay advice to senders that can't set a bearer header. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
|
Manual CI run for head |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b3c1c3e7e5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
sync with main a328bee: merged #30219
Generated with |
…codagt-1216-automations-docs No conflicts. make gen produced no diff. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
|
merged #30219
Generated with |
…codagt-1216-automations-docs No conflicts. make gen produced no diff. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
Generated with |
…codagt-1216-automations-docs No conflicts. make gen produced no diff. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
Generated with |
…codagt-1216-automations-docs No conflicts. make gen produced no diff. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
|
merged #30219
Generated with |
…le recovery Add manage_automations to the platform tools table in the architecture page, which enumerates every built-in tool. Describe the late run of an occurrence that came due while the experiment was off as best effort: lock or hook delays can still push it past the 60 second window. Turning the experiment back on before the due time remains the way to be sure it runs. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
…codagt-1216-automations-docs No conflicts. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
|
Docs review fixes: manage_automations in the architecture page's platform tools table; the late recovery of an occurrence missed while the experiment was off is described as best effort. Merged #30219.
Generated with |
|
Review follow-ups in head cc508e0, both in 9675918:
Generated with |
Turning the experiment back on before an occurrence is due avoids the late recovery path, but it does not guarantee the occurrence runs. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
|
On the recovery wording held from review 5383780861 (thread r4151796827):
The best-effort sentence landed in 9675918. Commit dc0d910 replaces the last overstatement, "To be sure an occurrence runs, turn the experiment back on before its due time." No other docs page repeats the recovery claim. "When a schedule runs" describes only the 60-second lateness limit and that missed occurrences are never replayed. Generated with |
ibetitsmike
left a comment
There was a problem hiding this comment.
Xum reviewed this PR on behalf of @ibetitsmike using GPT-6.1 Sol (high) Exec subagents.
The original certainty-wording finding is fixed. One own-layer documentation-style issue remains below, so I am withholding approval. This is not a runtime scheduling defect; the accepted functional boundaries remain unchanged.
| ### Silent failures | ||
|
|
||
| Skipped and missed schedule runs appear only in the server logs, as `chat automation schedule occurrence skipped` and `chat automation schedule occurrence missed` messages. | ||
| A schedule whose target chat is archived or deleted, or whose owner isn't active, doesn't run and logs nothing. |
There was a problem hiding this comment.
P3: Follow the docs word-choice policy
Both whose clauses use the schedule as their antecedent. docs/.style/style-guide/word-choice.md ("Whose for people, not things") explicitly disallows that inanimate construction. This policy is documentation-only, so a clean Vale run does not check it. The scheduling behavior described here is correct; preserve it while changing the wording.
| A schedule whose target chat is archived or deleted, or whose owner isn't active, doesn't run and logs nothing. | |
| A schedule doesn't run or produce logs when its target chat is archived or deleted, or when its owner isn't active. |
There was a problem hiding this comment.
Fixed in 8a58767. Silent failures now uses your wording: "A schedule doesn't run or produce logs when its target chat is archived or deleted, or when its owner isn't active."
I also checked every hand-written docs page this stack adds or changes (automations.md, architecture.md, chat-search-syntax.md, index.md, platform-controls/index.md, glossary.md) against the word-choice rules that Vale doesn't check. There was no other inanimate "whose". The same commit fixes the other findings, all on this page:
- "the server" / "server logs" / "server options" now name the control plane,
coderd(introduced as "the process that runs the control plane") andcoder server(Naming Coder's components). - "keep the URL easy to update" is now "keep the URL configurable" (Don't assume simplicity or difficulty).
markdownlint (pnpm run lint-docs) and Vale report 0 errors.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high
…s page Replace the inanimate "whose" in Silent failures with the reviewer's wording, name the control plane, `coderd` and `coder server` instead of "the server", and drop "easy" from the experimental API note. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
ibetitsmike
left a comment
There was a problem hiding this comment.
Xum validated this PR and approved it on behalf of @ibetitsmike.
The reported wording findings are fixed. The unchanged head, base, body and seven docs blobs match the completed independent Standards and Spec reviews; those manual verdicts were carried, not rerun.
All six fresh exact-head docs checks passed: Markdownlint, tables, manifest validation, formatted generated-manifest byte comparison, manifest JSON, and local links/anchors (169 local passes; external URLs not fetched).
Exact-commit CI run 37012079913 passed, including required; its 26 check runs succeeded or were skipped. The PR rollup omits that dispatch run. Pixel / Review remains pending and explicitly non-required. This docs-only approval does not claim Pixel validation or merge readiness. No fresh Go, frontend, full-suite or remote UAT checks were run.
…omations-docs Brings main ff158c0 into this layer. No conflicts. --- _Generated with [`xum`](https://github.com/coder/xum) • Model: `anthropic:claude-opus-5-5` • Thinking: `high`_
Closes CODAGT-1216
Part of CODAGT-1135
Adds an early-access page for chat automations in Coder Agents:
docs/ai-coder/agents/automations.md. It covers enabling thechat-automationsexperiment and theoffexperiment rule as the operator kill switch, webhooks (endpoint, bearer secret, 256 KiB JSON body, responses, single and multi use, rotation), schedules (cron and time zone, server previews, no catch-up, Run now), When busy, themanage_automationstool and heartbeats, the per-owner cap and the queue share, and the accepted risks (spend, silent failures, prompt injection).It also adds the manifest entry (early access, after Chat Sharing), a glossary entry, a
manage_automationsrow in the built-in tools table, and a link from the experiment-gated features list in Platform Controls.The page documents the code as built on this stack, not the RFC, where they differ. Notable differences: reasoning effort is only offered for new chat targets; schedules accept an occurrence up to 60 seconds late and never replay older ones; the dashboard has no delete control, so delete is documented through the API;
manage_automationsnever returns webhook secrets.Dogfood UAT followed the page step by step on a
develop.shinstance built from this branch (experiment rule on and off, webhook creation and curl deliveries with the documented status codes we could trigger, schedule previews and Run now, the Manage automations switch), and passed.Where the page's claims come from
codersdk/deployment.go(ExperimentChatAutomations,ExperimentsUserScoped)coderd/exp_chat_automations.go(requireChatAutomations, events handler),coderd/x/chatd/automation_schedules.go(scan skips owners, keeps cursors)coderd/coderd.go,codersdk/chatautomations.go,coderd/x/chatd/automations.go(validation)coderd/x/chatd/automations.go(ErrAutomationOwnerOnly)coderd/exp_chat_automations.go(events handler,writeChatAutomationError),coderd/exp_chats.go(maxChatRequestBodyBytes)coderd/x/chatd/automations_publish.go(automationEventText)coderd/x/chatd/automations.go(RotateAutomationSecret),AutomationWebhookFields.tsx(button hidden)coderd/httpmw/ratelimit.go(RateLimitByEndpointKey),--api-rate-limitdefault 512coderd/schedule/cron/cron.go,coderd/exp_chat_automations.go(chatAutomationNextRunCount = 5, schedule preview)coderd/x/chatd/automation_schedules.go(automationScheduleInterval,automationScheduleGrace)coderd/x/chatd/automations_publish.go(busy check,max(1, MaxQueuedMessagesPerChat/2)),codersdk/chats.go(default 20)coderd/x/chatd/automations_tool.go,coderd/exp_chats.go(manage_automations_enabledchecks),AgentChatInput.tsxcodersdk/deployment.go(--chat-max-automations-per-owner),codersdk/chats.go(default 50)coderd/x/chatd/automation_schedules.goenterprise/audit/table.go(promptandwebhook_secret_hashare secret)Identifiers kept off the page because the reader never types or receives them:
queue_generation,schedule_revision,schedule_next_run_at, and the internal error names above.Generated with
xum• Model:anthropic:claude-opus-5-5• Thinking:high