CronCreate tool estimate · request
Stored count_tokens request for CronCreate tool estimate.
Record provenance
- Measurement
estimate-tool-CronCreate- Record ID
95a90263517e25b1270a61b683e038e8e8656b3c91ed7d156e24894b771d76f4- Exact artifact
raw/count-tokens/95a90263517e25b1270a61b683e038e8e8656b3c91ed7d156e24894b771d76f4.request.json
{
"id": "95a90263517e25b1270a61b683e038e8e8656b3c91ed7d156e24894b771d76f4",
"label": "estimate-tool-CronCreate",
"generatedAt": "2026-06-09T00:30:00.641Z",
"url": "https://api.anthropic.com/v1/messages/count_tokens?beta=true",
"headers": {
"anthropic-beta": "claude-code-20250219,context-1m-2025-08-07,interleaved-thinking-2025-05-14,context-management-2025-06-27,prompt-caching-scope-2026-01-05,mid-conversation-system-2026-04-07,advisor-tool-2026-03-01,effort-2025-11-24,token-counting-2024-11-01",
"anthropic-version": "2023-06-01",
"content-type": "application/json",
"x-api-key": "<redacted>"
},
"body": {
"model": "claude-opus-4-8",
"messages": [
{
"role": "user",
"content": [
{
"type": "text",
"text": "<system-reminder>\nAs you answer the user's questions, you can use the following context:\n# currentDate\nToday's date is 2026-06-08.\n\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\n</system-reminder>\n\n"
},
{
"type": "text",
"text": "say hi",
"cache_control": {
"type": "ephemeral"
}
},
{
"type": "text",
"text": "{\"description\":\"Schedule a prompt to be enqueued at a future time. Use for both recurring schedules and one-shot reminders.\\n\\nUses standard 5-field cron in the user's local timezone: minute hour day-of-month month day-of-week. \\\"0 9 * * *\\\" means 9am local — no timezone conversion needed.\\n\\n## One-shot tasks (recurring: false)\\n\\nFor \\\"remind me at X\\\" or \\\"at <time>, do Y\\\" requests — fire once then auto-delete.\\nPin minute/hour/day-of-month/month to specific values:\\n \\\"remind me at 2:30pm today to check the deploy\\\" → cron: \\\"30 14 <today_dom> <today_month> *\\\", recurring: false\\n \\\"tomorrow morning, run the smoke test\\\" → cron: \\\"57 8 <tomorrow_dom> <tomorrow_month> *\\\", recurring: false\\n\\n## Recurring jobs (recurring: true, the default)\\n\\nFor \\\"every N minutes\\\" / \\\"every hour\\\" / \\\"weekdays at 9am\\\" requests:\\n \\\"*/5 * * * *\\\" (every 5 min), \\\"0 * * * *\\\" (hourly), \\\"0 9 * * 1-5\\\" (weekdays at 9am local)\\n\\n## Avoid the :00 and :30 minute marks when the task allows it\\n\\nEvery user who asks for \\\"9am\\\" gets `0 9`, and every user who asks for \\\"hourly\\\" gets `0 *` — which means requests from across the planet land on the API at the same instant. When the user's request is approximate, pick a minute that is NOT 0 or 30:\\n \\\"every morning around 9\\\" → \\\"57 8 * * *\\\" or \\\"3 9 * * *\\\" (not \\\"0 9 * * *\\\")\\n \\\"hourly\\\" → \\\"7 * * * *\\\" (not \\\"0 * * * *\\\")\\n \\\"in an hour or so, remind me to...\\\" → pick whatever minute you land on, don't round\\n\\nOnly use minute 0 or 30 when the user names that exact time and clearly means it (\\\"at 9:00 sharp\\\", \\\"at half past\\\", coordinating with a meeting). When in doubt, nudge a few minutes early or late — the user will not notice, and the fleet will.\\n\\n## Session-only\\n\\nJobs live only in this Claude session — nothing is written to disk, and the job is gone when Claude exits.\\n\\n## Not for live watching\\n\\nCronCreate re-runs a prompt at fixed wall-clock intervals. To watch a log file, process, or command output and be notified the moment something changes, use the Monitor tool instead — Monitor streams events as they happen; cron polls on a schedule.\\n\\n## Runtime behavior\\n\\nJobs only fire while the REPL is idle (not mid-query). The scheduler adds a small deterministic jitter on top of whatever you pick: recurring tasks fire up to 10% of their period late (max 15 min); one-shot tasks landing on :00 or :30 fire up to 90 s early. Picking an off-minute is still the bigger lever.\\n\\nRecurring tasks auto-expire after 7 days — they fire one final time, then are deleted. This bounds session lifetime. Tell the user about the 7-day limit when scheduling recurring jobs.\\n\\nReturns a job ID you can pass to CronDelete.\",\"input_schema\":{\"$schema\":\"https://json-schema.org/draft/2020-12/schema\",\"additionalProperties\":false,\"properties\":{\"cron\":{\"description\":\"Standard 5-field cron expression in local time: \\\"M H DoM Mon DoW\\\" (e.g. \\\"*/5 * * * *\\\" = every 5 minutes, \\\"30 14 28 2 *\\\" = Feb 28 at 2:30pm local once).\",\"type\":\"string\"},\"durable\":{\"description\":\"true = persist to .claude/scheduled_tasks.json and survive restarts. false (default) = in-memory only, dies when this Claude session ends. Use true only when the user asks the task to survive across sessions.\",\"type\":\"boolean\"},\"prompt\":{\"description\":\"The prompt to enqueue at each fire time.\",\"type\":\"string\"},\"recurring\":{\"description\":\"true (default) = fire on every cron match until deleted or auto-expired after 7 days. false = fire once at the next match, then auto-delete. Use false for \\\"remind me at X\\\" one-shot requests with pinned minute/hour/dom/month.\",\"type\":\"boolean\"}},\"required\":[\"cron\",\"prompt\"],\"type\":\"object\"},\"name\":\"CronCreate\"}"
}
]
},
{
"role": "system",
"content": "The following skills are available for use with the Skill tool:\n\n- deep-research: \n- update-config: \n- keybindings-help: \n- verify: \n- code-review: \n- simplify: \n- fewer-permission-prompts: \n- loop: \n- claude-api: \n- run: \n- init: \n- review: \n- security-review: "
}
],
"thinking": {
"type": "adaptive"
},
"output_config": {
"effort": "high"
},
"system": [
{
"type": "text",
"text": "x-anthropic-billing-header: cc_version=2.1.168.c27; cc_entrypoint=sdk-ts; cch=e5b75;"
},
{
"type": "text",
"text": "You are a Claude agent, built on Anthropic's Claude Agent SDK.",
"cache_control": {
"type": "ephemeral"
}
}
]
},
"bodyCanonicalSha256": "ed964cb3f51805a77081936ffc9beea3f17f8fc910f29119535657a663d7eccf"
}