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

Helping your AI understand your taste with the Imprint tool

Build shared project understanding through collaboration, and bring it into later conversations.

Imprint is a living project memory of intent, preferences, and design decisions. It helps later conversations recover relevant understanding without treating every one-off change as a permanent rule.

Ground what Popmelt learns

When a thread produces a potentially reusable preference, Popmelt may ask whether it should apply in future work. Read the question in the thread. For example, decide whether all prompt-copy buttons should have a copy icon or whether the current invitation is a special case. Choose one of the three answers.

OptionWhat it tells your AI
YesAdd the learning to the project's shared understanding for future reference
This timeThis is a one-off override: keep it local to this situation
NoLeave the Imprint unchanged (you'll be asked to explain if you'd like)

You remain the authority. Provisional explanations are advisory; your explicit instructions and accepted product decisions take precedence.

“This time” keeps the copy-icon choice specific to the current invitation.

Inspect the evidence

Choose Imprint (I) to review the project's understanding. Filter grounded, emerging, and challenged explanations. Expand an explanation to inspect its rationale, related understanding, concrete expressions, and grounding evidence, or reopen its source thread.

The panel is for inspection. Changes to understanding are proposed and grounded through collaboration in threads, not authored directly from this panel.

Use context in ordinary agent conversations

Core can pair project-bound Codex conversations with the same memory through its bundled ambient plugin. Inspect the installation from your project first:

npx @popmelt.com/core codex status

With your permission to change personal plugin configuration, your agent can install or update the bundle:

npx @popmelt.com/core codex install

Follow the reported restart instructions after active work finishes, then start a new project-bound conversation. Confirm that the new session has loaded the plugin's context and tools; installed files alone don't prove activation. You can also choose toolbar-only use.

An experimental native Claude Code plugin is available through claude status, claude install, and claude doctor after npx @popmelt.com/core. It is a local Code integration, not a promise of support in Claude Chat, Cowork, or cloud sessions. The toolbar works independently of this optional plugin.

During native setup, run npx @popmelt.com/core codex doctor or npx @popmelt.com/core claude doctor from the project environment. The JSON result separates the provider CLI from the bridge. Follow provider.nextStep when the CLI is missing, signed out, or could not be verified. Then rerun doctor after the user completes sign-in. Verify your agent

If a later request draws on Imprint, the agent can explain which earlier choice informed its answer. For example, a request to add a button to a system card might bring back the glass treatment the team used on a previous card. Check whether that reasoning fits the new request and reply if it should be an exception.

The earlier decision supplies a reason for the proposed button style.

Point and discuss

With the ambient integration active and your app running, point to an element and ask your agent what you're looking at. It can inspect that target, read a saved thread, or retrieve relevant project context without submitting a new comment.

Focus is a timestamped snapshot, not continuous vision. Keep the intended target selected or point again. If several pages are active, clarify which one you mean. Reading a draft does not authorize its execution.

When more than one project store applies, choose the writable primary store and any read-only mounts explicitly. Directory proximity does not grant write authority.

Imprint and conversation history live with the project under .popmelt/. Context required for an agent request is passed to the selected AI provider; local storage does not mean the whole collaboration is offline: if you aren't hosting the LLM you're using locally, your data is still passing through your provider as usual.

Next: Creating annotations with the Chat tool.

Didn't find the answer? Have an idea?

Ask a question