Drafted 3 of 5 replies. Next: send the 2 to Acme after legal OK.
Cloud for Botsinfrastructure for your bots
Your agent forgets between runs. Wake it with its notes.
Schedule a wake-up with the agent's notes and next step. At the time you pick, we POST it back, or hold it for the next session. No lost thread.
50 calls/day free · Pro $9/mo · bring your own model
schedule_wake · live API
nowin 2 hourszZ
Sample: Preview: wake at 2026-10-15 20:14 UTC, held for check_wakes. Show this to the user; call again with confirm=true to save.
Works with the agents you already run
- AClaude
- {}Codex
- CChatGPT
- GGrok Bot
How it works
Save the thread. Wake on time.
schedule_wakePick a time and hand over notes, next step and thread ID. Preview first, then confirm.
check_wakesAt the start of a session, collect wakes that are due, each with its saved state.
cancel_wakePlans changed? Cancel by ID. Or give a callback URL and we POST the wake to you.
Pricing
Free to start. Pro for busy agents.
Free resets daily and is not a trial. Pro is $9 a month.
Free
$0
50 calls a day, no key. Up to 10 active wakes with 8 KB of notes each, repeating every 60+ minutes.
- 50 calls a day, no signup
- 10 active wakes
- Repeat every 60+ minutes
- 8 KB of notes per wake
Pro
$9/month
5,000 calls a day, repeats every 5+ minutes and up to 64 KB of state per wake.
- 5,000 calls a day
- Repeat every 5+ minutes
- 64 KB of state per wake
- Key instantly after checkout, cancel anytime
Worked example
A support agent should check its queue every 15 minutes. Free repeats no faster than every 60 minutes, so it misses 3 of every 4 check-ins. With Pro at $9/month it wakes every 15 minutes with its notes.
For agents
Tools your agent gets
Each result includes understood, job and a one-line outcome your agent can report back in plain words.
schedule_wakeSchedule a wake-up for your agent. At the time you pick, Agent Wake POSTs your saved state (notes, thread ID, next step) to your callback URL, or holds it for check_wakes.
check_wakesCollect wake-ups that are due for your inbox (each returned once, with its saved state and thread ID) and list upcoming ones. Call this at the start of a session.
cancel_wakeCancel a pending wake-up by wake_id. Call once without confirm to preview, then with confirm=true.
usage_and_upgradeUsage today + upgrade link (not metered).
Connect
One line to install
claude mcp add --transport http agent-wake https://wake.cloudforbots.com/mcp
MCP URL https://wake.cloudforbots.com/mcp
REST POST https://wake.cloudforbots.com/api/run/<tool>
Auth optional Authorization: Bearer <key>
Codex, ChatGPT, Grok Bot: add a remote MCP server with the URL above. Skill file: SKILL.md · catalog entry: tool.json
FAQ
Questions
What problem does this solve?
Scheduled agent runs start as fresh sessions, so they forget what the last run was doing. Agent Wake stores a small state blob (goal, progress, next step, IDs) and gives it back at the time you pick, so the next run continues instead of starting over.
How does the wake-up reach my agent?
Two ways. With a callback_url, we POST the state as JSON to your public https endpoint within about a minute of the scheduled time, signed with an HMAC header you can verify. Without one, the wake waits in your inbox and your agent collects it with check_wakes at the start of its next session.
Does it change anything without asking?
No. schedule_wake and cancel_wake first return a preview of exactly what will be saved or canceled. Nothing is written until your agent calls again with confirm=true, so it can show the user and get a yes first.
What does it cost?
Free: 50 calls a day, 10 active wakes, repeats every 60+ minutes, 8 KB of state. Pro is $9 a month: 5,000 calls a day, 1,000 active wakes, repeats every 5+ minutes, 64 KB of state. You get your Pro key on screen right after paying.
Is there a model inside?
No. Bring your own model. Agent Wake only stores and delivers what your agent saves, and works with Claude, Codex, ChatGPT and Grok Bot over MCP or REST.
What can I store?
Any JSON object: the task, what is done, what is next, links and IDs. Don't store passwords or API keys. Delivered wake-ups are deleted 7 days after your agent collects them.