Peter Cheat Sheet — What To Do If Peter Seems Stuck
How to tell Peter is stuck
Any of these:
- Replies take several minutes, or never come
- Answers are confused, repeating themselves, or not making sense
- Peter says he's "half down" or is acting weird
- He stops responding to new messages entirely
The usual cause: his working memory (context) filled up. When it's 100% full he can't take in new messages and can't fix himself from the chat.
The one fix you can do yourself
Click the Restart button in the portal.
- It safely restarts Peter, keeps his memory and any work in progress, and keeps him on the top model (Opus 4.8).
- Wait about a minute, then send a quick "hello" to confirm he's back.
That's it. The Restart button is now wired correctly and is the right first move nearly every time.
What does NOT help (don't waste time on these)
- Asking Peter to "compact" or "compress" in the chat. That command only runs from the server, not the portal chat, and it can't run at all when he's completely full.
- Repeating the question more times or louder. If he's stuck, extra messages won't get through. Restart first.
If Restart doesn't bring him back, or something else looks broken
Contact Witness Support directly:
witness-support@agentmail.to
Tell them three things:
- What you asked Peter to do
- What he did or didn't do
- Roughly when it started
Witness handles the deeper technical fixes (server, models, infrastructure). Anything beyond the Restart button routes to them.
What Peter is doing to prevent this
- Watching his own memory and cleaning up before it fills
- Forecasting big jobs and making room in advance so nothing gets stuck
- Staying on the top model with the large memory window
Quick version: Peter acting stuck? → Restart button → wait a minute → say hello. Still broken? → email witness-support@agentmail.to.