Skip to Content
Keko

Keko Cloud

Each thread gets a Linux machine of its own, which keeps working while your Mac sleeps

A thread on Keko Cloud gets a Linux virtual machine of its own, with the project cloned on it. It's the default device when you're signed in.

What a cloud machine has

  • The project, cloned on the machine, and the thread's worktree on its own branch.
  • Docker, and a desktop with Chrome, which threads use for proof of work.
  • Preview links for every server the thread starts.
  • The project's setup, run on every new worktree (Projects and environments).

Sleep and wake

A machine stops a few minutes after its thread goes idle. The thread keeps its history; your next message, or the thread's next tool call, starts the machine again and carries on. A stopped machine costs no cloud hours.

A machine whose thread hasn't been used for 14 days is cleared to free its disk. Its work is kept first: the branch, its checkpoints and any uncommitted files, without pushing anything. The thread says "Workspace cleared after 14 days asleep". Its next message makes a new machine, clones the project, puts the branch and files back, and says "Workspace made again from" the branch.

Usage

Cloud machines count against your plan's cloud hours, from the moment a machine is being made until it stops. When the month's hours are used up, running machines stop once their turn ends, messages to cloud threads wait until the next month or an upgrade, and new threads do what you chose for when Keko Cloud is out (Your server); threads on your own devices keep running. See Plans and usage.

Private repositories

To clone private repositories on Keko Cloud, install the GitHub App. The machine clones with your own GitHub access, so a thread can only reach repositories you can.

On this page