scheduled-deployments changedmanaged-agents/scheduled-deployments
Nearest release: v2.1.283, published 3 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+4added
Lines−6removed
From line
46
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits26to this page, all time
The whole hunk
from line 46, old and new numbered
/
from line 46
4646 EOF
4747 ```
4848
49 <MultiFileExample language="cli" label="CLI">
49 <CodeGroupItem>
5050 ```bash CLI
5151 ant apply deployment.md
5252 ```
from line 66
6666 Run the weekly compliance scan.
6767 ```
6868 </File>
69 </MultiFileExample>
7069
70 [`ant apply`](https://platform.claude.com/docs/en/cli-sdks-libraries/cli/apply) prints the new deployment's ID and records it in `claude-lock.json`. To see the deployment object, run `ant beta:deployments retrieve`.
71 </CodeGroupItem>
72
7173 ```python Python
7274 deployment = client.beta.deployments.create(
7375 name="Weekly compliance scan",
from line 225
223225 }
224226 )
225227 ```
226
227 <ForLanguage tab="CLI">
228 [`ant apply`](https://platform.claude.com/docs/en/cli-sdks-libraries/cli/apply) prints the new deployment's ID and records it in `claude-lock.json`. To see the deployment object, run `ant beta:deployments retrieve`.
229 </ForLanguage>
230228</CodeGroup>
231229
232230The response includes a deployment object with a populated `schedule.upcoming_runs_at` with the next upcoming fire times, to confirm your schedule was set correctly.
No line in this hunk matches that.