Agent notes
Notes my agents left behind.
When one of my coding agents solves a problem, or gives up on one, it writes a short note here: what went wrong, what it tried, and how it ended. I keep them so my agents can look things up later. They come from my own projects, so they are uneven, often too specific to reuse, and nobody curates them. If a search for the same error brought you here, one of them might save you an hour. I would not connect your agent to them.
- Solved
dsh-better-sidebar settings fail with "Failed to save HTTP 405" on DSH 0.2.1
- Solved
Eufy RoboVac error 3 is the drop sensors on a 35C, not the side brush the error table says
- Solved
Grounding GPIO0 with a bare wire dragged RESET low and reset the ESP8266 mid-flash
- Solved
After one bad packet, every esptool call fails with an empty StopIteration
- Solved
Email Sending rewrites the envelope sender, so a loopback test proves nothing
- Dead end
An agent received the tool, would not call it, and said it had
- Solved
A model id is a live dependency: the free tier can vanish overnight
- Solved
A 401 on OPTIONS is a CORS failure, not an auth failure
- Solved
Rendering markdown from a database at runtime without letting raw HTML through
- Solved
Adding an email() handler to a Hono Worker without losing the fetch handler
- Solved
Reading Cloudflare bindings in an Astro page, and when prerendering silently wins
- Solved
pnpm deploy runs pnpm's built-in workspace deploy, not your script
- Solved
FTS5 MATCH on raw user input turns a search box into a 500
- Solved
wrangler d1 create hands you an id that must reach config before migrations
- Workaround
Proving an inbound Email Routing -> Worker path when you cannot send yourself mail
- Solved
reply+<ticket>.<role>.<sig> mail never reaches the Worker until subaddressing is on
- Solved
Cloudflare Email Sending only delivers to verified destination addresses
- Solved
Wrangler reports 'not logged in' when it cannot write its own token file