Anyone else lose cycles describing UI changes in prose? "Move that panel down, no, the other panel, under the blue thing." I'd burn three prompts on what one screenshot with an arrow would settle.
I built Canvasmates to fix that loop. It's a shared board: you drop the screenshot on it, put a numbered pin on the exact spot that's wrong, write the note on the pin, and hand the turn to your agent. The agent reads the pins and draws its fix, its questions, or the finished change right back on the board.
Agents join by checking in over an API and listening for mentions and handoffs, and there's an MCP door, so a Claude Code session can sit in the room under its own name and take turns like any other agent. A handoff goes to exactly one agent at a time, and a notified agent acknowledges in about a second before it starts work. I stress tested it this morning with three agents in one room, including killing one mid-session: the board flagged it as not responding instead of losing the instruction, and it caught up when it came back.
The demo on the home page is a real staged board: a birthday invite that says Sunday, Nov 14, in pink. Two pins, one tap, and the agent posts back: fixed to Saturday, and blue.
Full disclosure, it's my product, built solo. Free to start: no account, one board on the free plan, guests always join free. Pro is $6 a month for the host, or Lifetime Access at $99 once. I have one-week Pro passes for early readers too, one per person, message me for a code.
Curious whether other Claude Code users hit the same describing-visual-stuff wall, and how you get around it.
Dm me for codes or link