Skip to Content
Keko

Proof of work

Threads use a desktop, and show screenshots and recordings of what they built

Threads on Keko Cloud machines can use the machine's desktop: open pages in Chrome, click, type, scroll, take screenshots and record the screen. Any model can use these tools. Threads on This Mac don't have them.

On your server

Threads on your server get the same tools once it's set up with keko setup --desktop, which installs a desktop, Google Chrome on x64 or Chromium on arm64, and ffmpeg for recordings. Each Keko Cloud thread has a machine of its own; on a server, every thread shares the server's one desktop, so they see and drive the same screen. The desktop belongs to the user running keko: other users on the server can't see or use it, and its stream reaches the Desktop tab only through Keko. Each thread's recordings are its own.

In the thread

  • Screenshots show in the chat, in the step that took them.
  • Recordings are saved with the thread and can be played from the step. A thread starts and stops a recording around what it wants to show, such as a flow it built working end to end.
  • The Desktop tab in the work pane shows the machine's screen live, on Keko Cloud and on your server.

Approvals

Looking never asks: screenshots, recordings and reading what's on screen run without asking. The first click or keystroke asks once, as Use the machine's desktop. Allowing it allows the whole desktop for the rest of the thread, including typing into terminals, until the thread ends. On a server, the card adds that the other threads on it share this desktop. In Auto, the reviewer judges the desktop once, not every click.

Opening an address is judged like opening it from a command: localhost counts as running the dev server, anything else as using the network. Starting a program is judged as the command line it runs, and reading the clipboard counts as using a secret. See Approvals and Auto.

Screenshots and the model

Every screenshot stays in the chat. In what's sent to the model, older screenshots are left out in batches, so the model sees the latest ones and the conversation stays within its context window.

On this page