You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
wakectl limits sets runs at once and when a run is stopped.wakectl limits runs 1 lets one run go at a time (two at most, as before), and wakectl limits stop-after 90 stops a run after 90 minutes rather than 120. Both take within half a minute, with no restart.
wakectl roots sets where Wake looks for your clones.wakectl roots add ~/code and wakectl roots remove ~/code change the folders setup asks about, one and two folders down; wakectl roots lists them.
wakectl setup --json for an app that runs setup its own way. It prints what setup would ask, with today's answers: this machine's checks, the folders it offers, the clones there and which apps asked for each, run modes, models and whether the listener starts at login. It changes nothing, and no key is ever in it.
Each run keeps the link to what it was summoned for.wakectl status --json and wakectl open --json give each run's url, the page on the app it works on, and herdr, whether it runs in a herdr tab or headless, so a program can link to the ask and offer the right way back in. Runs kept by an older Wake have neither.
wakectl status shows a run in herdr waiting on you. When a run stops on a question in its tab, a tool asking permission or a folder to trust, status says so with the question as the tab shows it, status --json gives the run's waiting (since and what), and the log says it. It clears when the run goes on. The question stays on your machine: an app that supports wake:waiting hears only that the run waits, and when it goes on.
wakectl as a single file, no Bun needed. Each release on GitHub now carries a binary for macOS (Apple silicon and Intel) and Linux (x64 and arm64), each with its SHA-256. wakectl install starts the listener from it, and wakectl update tells you when a newer one is out rather than reaching for npm.
Stop a run now: wakectl stop amber-heron. It ends a run going on this machine, found by its name, its ticket or its session id. A headless run's tool is stopped; a run in herdr is interrupted with Esc and its tab kept. The app shows the run couldn't finish, stopped by its owner.
Each run's steps are kept on your machine, a file per run. The lines wakectl logs shows for a run also go to its own file under runs/ in Wake's folder, as JSON lines, so a program can show one run's steps without reading the whole log. Readable by you alone, never sent anywhere, and removed when Wake forgets the run after its last 200.
--json for scripts and apps that drive wakectl.wakectl status --json prints the listener, each pairing's connection, the runs with their resume commands, the approved repositories and the settings as JSON; repos, model, doctor and open take it too. Only the forms that change nothing do, and no key is ever in it.
wake/v1 has calls for devices that watch. An app can let an agent's owner add a phone, a browser or a desktop app that lists the agent's runs and answers asks. Each holds a watch key, made only from a code the app shows its signed-in owner, so nothing a run can reach can say yes for them. An optional wake:waiting lets Wake say a run waits on its owner. The spec has them now, wakectl check probes them, and Wake calls wake:waiting when a run in herdr waits.
wakectl check tests an app's calls for devices that watch. Where the app makes watch codes, it checks that POST /wake/v1/watch and every watch call refuse what they must: a code nobody issued, a key that opens nothing, and this machine's own place key when it is paired with the app, since a place key must open none of them. It tries the optional waiting too.
Wake for GitHub: Pro, a plan for your own account. $8 a month or $80 a year, for what Wake's paid apps need: your runs, and what they ask you, on your other devices. Until those apps come, it does what Free does. Team stays the organisation's plan, with its policy and audit; like Team, Pro isn't on sale yet.
Changed
wakectl open never starts a run that is still going a second time. For a run going in herdr, it brings the run's tab to the front and opens herdr in your terminal (from inside herdr, the tab alone). For one going headless, it says so and that wakectl stop ends it, where it used to resume the session beside the run and fight it. A run that has ended resumes in your terminal as before.
wakectl install leaves an app's listener alone. When an app on your Mac runs the listener itself, as its own login item, install writes no second LaunchAgent under the same name and uninstall doesn't stop it: each says an app runs it, and that start at login is that app's setting. doctor and setup count it as installed, and pair no longer says to install.