Docs

Point and edit

Point lets you select any element in the preview and say what it should be instead. This chapter also covers sending more while a reply runs, stopping a reply, and what to do when one doesn’t come through.

Turn on Point

  1. Select Point

    Select Point in the preview toolbar. The preview says Click an element to change it, and the page stops following its own links and buttons while Point is on.

  2. Pick an element

    Move the pointer over the page. A ring follows the element under it. Select the one you want to change.

  3. Say what to change

    A small card opens next to the element. Type what it should be instead, then press Enter or select Send.

Pick an element, say what it should be, and the reply changes just that.

Pick with the keyboard

With Point on, you can walk the page with the arrow keys instead of the mouse.

↑Moves to the element that contains this one.
↓Moves to the first element inside this one.
←→Moves to the previous or next element at the same level.
EnterPicks the element and opens the card.
EscCloses the card, or turns Point off when no card is open.

The comment card

The card’s header names the kind of element you picked and its text, such as “Button · See the menu”. Type the change in plain words, such as “Make this button bigger and green”, and send it.

Your message appears in the chat with a chip above it naming the element. Point stays on after you send, so you can go on picking elements and commenting.

What Ploof Studio learns about the element

Point sends more than your words. With each comment, Ploof Studio gets:

  • the page the element is on, and exactly where it sits in that page
  • the element’s tag and its text as it appears on screen
  • its size and its computed styles
  • the CSS rules that style it, including which ones take effect and which ones another rule overrides

That is why a short comment such as “less padding” is enough. Ploof Studio knows which button you mean, down to the styles behind it.

Send more while a reply runs

You don’t have to wait for a reply to finish. While one runs, the prompt bar says Queue a change… and its send button becomes Queue message. The Point card’s button becomes Queue change.

Queued messages wait in a tray above the prompt bar that says how many are queued, and the preview toolbar shows the count too. When the current reply finishes, the next queued message is sent, and each one gets its own reply. Select Remove from queue on a row to drop it.

The queue pauses in two cases, and the tray says why.

  • Paused because you stopped the reply
  • Paused because the last reply failed

Select Send next to carry on, or send a new message, which sends the oldest queued one first.

The queue lasts until you quit Ploof Studio. Moving between projects keeps it.

Stop a reply

Select Stop generating in the prompt bar at any time. Ploof Studio keeps the text that arrived and every file it finished. Only the file it was writing at that moment is lost.

When a reply doesn’t come through

If a reply fails, the chat says why and offers Try again, which sends the same message again. Files the failed reply already wrote stay in the project. Some errors also offer Open Settings.

This project has no model yet.Pick a model in the prompt bar.
This project’s provider is disconnected.Pick another model, or connect the provider again in Settings.
The provider refused the saved key.Replace the key in Settings, under Providers.
Your Setapp AI credits are used up.Get more credits, wait for them to renew, or add an API key.
The provider is limiting requests.Wait a little, then select Try again.
The provider could not be reached.Check your connection, then select Try again.
That answer did not come through.Select Try again.

Stuck on something?

Write to us and a person reads it and replies.

support@ploof.dev