Popmelt

v0.36.0

Popmelt

v0.36.0
© 2026 Popmelt
HelpPrivacyTerms
Docs

  • Getting started with Popmelt Core
  • Creating annotations with the Chat tool
  • Comparing and refining options with Explore
  • Tweaking styles with the Steer tool
  • Helping your AI understand your taste with the Imprint tool
  • Using Popmelt with Three.js and react-three-fiber
  • Add custom context to Popmelt annotations and threads
  • Recovering an annotation that won’t send
  • Inviting a teammate to a local session
  • Where Popmelt saves and sends your data

  • Annotating static objects in images
  • Annotating moving objects in video
Docs/Core

Recovering an annotation that won’t send

Find out whether a note is still a draft, reached its thread, or needs attention from the bridge or coding agent.

If the note is still on screen, copy its text before reloading. Stay in the same browser profile and on the same dev URL, including the port. That is where Core can recover a local draft.

Check whether the note arrived

  1. Open the annotation’s thread from its badge, or open the conversation in History if it was archived. Look for the exact text you tried to send.
  2. If the message is there, read the status below it. Queued, an active run, or a request for approval means Popmelt already has the message. Follow that run in the thread.
  3. If the text is missing, check the canvas and composer. A numbered note with a send arrow is still a draft. Enter finishes typing on the canvas. Click the arrow or press Command/Control+Enter to send. In a thread, Enter sends the reply.
The send arrow beside the numbered note is available while the annotation is pending.

If the bridge is disconnected

The bridge connects the toolbar to the coding agent in your checkout. Open the toolbar’s connection status and check that you have the URL for the dev server you started.

With the default Next.js or Vite integration, request the status through your app’s port. For an app running on port 3000, use this command.

curl -i http://localhost:3000/popmelt/status

A working route returns JSON with a Core version and project ID. An HTML page or a 404 usually means the request missed the bridge. Check the app port, the framework plugin, and, for Next.js, the wrapped dev command. If you customized Vite’s basePath, use it in place of /popmelt. Check for active work before restarting the server. Check the framework setup.

On a paired phone, the preview page can still load after its bridge pairing expires. If the bridge restarted, generate a fresh phone link from the same checkout and open it in the browser you used before. Reconnect your phone.

Act on the thread status

StatusWhat to do
Not sentReconnect, reopen the thread, and check for the reply. If it is missing, send the text from the composer once.
Sign-in requiredCheck the CLI for the agent selected in the composer. Run codex login status or claude auth status in the environment that runs the bridge. Sign in there and retry.
At capacity or Rate limitedGive the provider a moment, then retry in the same thread.
Connection lost or Timed outRead the last reply and check for changes the agent already made. Ask it to continue with the remaining work.

If an older note stays on Sending, keep a copy of the text, restore the connection, then reload the same URL and check the thread again. If the note returns to Pending, send it once. If it is still stuck and the thread has no matching message, recreate the saved note on its target. For a recurring failure, include the Core version, framework, selected agent, and the last status you saw when reporting it.

Didn't find the answer? Have an idea?

Ask a question