Hit a limit? Rewake picks it back up.

Claude stops with a message such as "You've hit your session limit · resets 5pm", and the thread waits until you come back and type something. With Agent Rewake, the thread asks once whether to resume when the limit resets, with your resume message ready to edit, and sends it as soon as the limit resets.

With its preview installed: Claude Code asks once whether to continue the session after the reset, then continues it; when Claude Code's own continue will do that, Rewake leaves it to Claude Code. In Codex, type rewake in the thread at the limit (in Claude Code and Gemini CLI, /rewake), and the thread continues after the reset. GitHub Copilot CLI, Gemini CLI, Grok Build, Qwen Code, OpenCode and Antigravity CLI sessions are continued once they're closed: run npx @codizelabs/agent-rewake continue before the reset.

Yes, if you turn it on. In Zed: per thread from the Rewake menu (Turn on auto-resume after limits…), or for new threads in Rewake → Settings…. In Claude Code, answer that it should continue from then on; for closed Claude Code, Copilot CLI, Gemini CLI, Grok Build, Qwen Code, OpenCode and Antigravity CLI sessions, run npx @codizelabs/agent-rewake continue --always once. It still asks instead when the reset is more than 24 hours away; in Zed also when the agent gives the same reset time twice, or when you chose to exclude threads that bypass permissions.

Yes. Rewake goes in front of every external agent Zed runs and works the same way with each: the menu, scheduling, the schedules page and resume after a limit. Claude and Codex say when the limit resets; for agents that don't (Gemini CLI, for example), you pick when to resume. Outside Zed, previews cover Codex, Gemini CLI, GitHub Copilot CLI, Grok Build, Qwen Code, OpenCode and Antigravity CLI in a terminal.

In Zed, yes: Rewake runs inside Zed, so nothing is sent while Zed is closed or the computer is asleep. You don't need the thread on screen: you can work in other threads. After restarting Zed, open the thread once. A message more than 15 minutes late isn't sent on its own: Rewake asks you.

In Claude Code, keep Claude Code open: Rewake's plugin runs inside it, and a continue that came due while it was closed is offered when you reopen the session. For Codex, GitHub Copilot CLI, Gemini CLI, Grok Build, Qwen Code, OpenCode and Antigravity CLI, nothing needs to stay open: the system's own timer starts Rewake at the reset. Keep the computer on and awake; if Codex is closed then, the thread continues when you next open it.

In Claude Code, less than you might think, and Rewake steps aside there: when Claude Code's own "Continue automatically at usage limit" will most likely do it (its setting on, a reset within a day), Rewake leaves the limit to it. It asks to continue when that won't apply: in Claude Code's VS Code and Cursor panel, where that setting doesn't apply, or when the setting is off or the reset is further away.

What's left is everything outside that one case. Claude Code's own continue works in its own terminal sessions and only for Claude; whether it applies to the Claude adapter that Zed runs isn't documented. Rewake covers Codex, GitHub Copilot CLI, Gemini CLI, Grok Build, Qwen Code, OpenCode, Antigravity CLI and every external agent in Zed, from one command and one schedules page, and it sends messages later: once, repeating, or one after another after a resume. Checked 2026-10-08.

No. It waits for the reset the agent reports, or the time you pick, then sends one message, as you would. That message uses your plan like any message you type. Your plan, limits and credits don't change, and a credit, billing or spending limit, which waiting won't fix, gets a message and no resume.

Rewake follows the agent: if it's still limited when Rewake continues, it waits for the new reset time. A reset more than a day away is confirmed with you first, even when automatic resume is on. For agents that don't say when their limit resets (Copilot CLI's weekly limit, Grok's free limit, Cursor), you choose the time.

If you upgraded your plan, or the limit lifted early, run npx @codizelabs/agent-rewake continue --now for a resume Rewake planned outside Zed. It names the agent and folder, says what it will send, and asks first; or give the id from agent-rewake schedules. It makes the same checks as at the reset. If you typed in the session, if it is open or has changed, if the agent already continued, if the limit is still on, or if the message can't reach the agent (signed out, session deleted or archived, folder gone), nothing is sent and your resume stays planned for its time. The window stays busy while the agent works, and Ctrl+C stops it and cancels the resume. In Zed, use Rewake → Change a scheduled message….

Nothing is sent while it sleeps. When it wakes, a resume more than half an hour late (15 minutes in Zed) isn't sent on its own: Rewake asks or tells you instead. On macOS (and, not yet tried by hand, Linux with systemd and Windows), Rewake keeps the computer from idling to sleep while a resume is due within six hours (while plugged in, by default); closing the lid still puts it to sleep. agent-rewake doctor says if your own sleep settings would let it sleep, and the docs list the settings to change.

In Claude Code and Codex, yes. The plugin tells you when a usage window passes 80% and 95% used, and when your pace over the last hour would reach the limit within about 45 minutes and before it resets, as a range such as "in about 20 to 40 minutes". It uses only the usage figures Claude Code or Codex already gives it, as of its last reply: no network, no sign-in. It only tells you: in Claude Code, at 80% it mentions /compact (which uses some quota itself), and at 95% (in both) it says it is a good moment to wrap up. It never types or compacts for you. Turn it off with agent-rewake settings usage-warnings off. In Codex the warning comes with your next prompt, from the figures of Codex's previous reply, so it is one turn late; it is not yet seen in the Codex desktop app or the VS Code extension. The other agents are not covered.

Outside Zed, when the session's folder is a git folder, Rewake compares the project's latest commit and its tracked files with how they were when it planned the continue. If they differ, it tells you and sends the message as it was. You can choose that it also adds one fixed line asking the agent to re-read files (note), or sends nothing and asks you first (hold), with agent-rewake settings workspace-changed. New untracked files don't count. It reads only the commit id and the names-and-status summary of git status --porcelain --untracked-files=no, never file contents, and only on your computer.

Run npx @codizelabs/agent-rewake doctor: it lists the continues planned for closed sessions, any that need you, and the last error if one failed. In Zed, the schedules page lists every message and its state, and a message Rewake sends is labelled as coming from Rewake, so you can tell it from one you typed.

Open a bug report with the agent and its version, the exact limit message as the agent printed it (private details removed), what you expected, and the output of npx @codizelabs/agent-rewake doctor --details. How to report a limit Rewake missed.

Yes, but only with your approval. The agent gets tools to schedule, change and cancel messages in its own thread; each request shows a form in the thread, where you can edit the message and accept or decline. It can also read Rewake's guide to answer your questions about Rewake.

Rewake sends one message, which uses your plan like any message you type; it doesn't change your plan, limits or credits, and it never approves permission prompts for you. Everything stays on your computer; it sends only the messages you scheduled, to your agent. Besides fetching an agent's own program when Zed hasn't, the only network call Rewake can make on its own is an error report, and that's off unless you turn it on. Logs hold metadata, never message text. What it runs, stores and changes, and how to undo it.

Claude Code in a terminal, and in its panel in VS Code or Cursor: yes, as a preview. Pick it in npx @codizelabs/agent-rewake install, or run npx @codizelabs/agent-rewake install --only claude-code. The Claude desktop app's Code tab hasn't been tried yet. Claude's own apps (claude.ai and the desktop app's chat) and Zed's own agent can't be reached: Zed doesn't let add-ons into its own agent. Claude Code and the desktop app also each have their own setting to continue after a usage limit.

From any version: run npx @codizelabs/agent-rewake@latest install, then, in Zed, choose "Reload Agent" in the Agent Panel's menu in each open thread (Zed 1.18 or newer). Quitting Zed completely and opening it again also works. The previews outside Zed use the new version from their next session. Your threads, scheduled messages and settings stay. Any version-specific steps (none so far) are in the docs.

No. Zed extensions can't add this, so in Zed, Rewake is an add-on on the Agent Client Protocol (ACP) connection between Zed and your agent. Outside Zed, it uses each agent's own plugins, extensions or hooks. agent-rewake install sets it up in the places you pick, and agent-rewake uninstall takes it out.