TaskWindow v0.2.10

Changed

human input is now the default. Clicks, scrolls, typing and mouse_move
take the human path unless you pass human: false, so lazy-loading lists,
hover menus and type-ahead inputs work on the first try instead of after an
agent notices the plain event did nothing. Each action costs a few hundred
milliseconds more; human: false gets the old instant event back.

Fixed

human: "true" no longer fails the call. Some agents send booleans and
numbers as strings, and the schema rejected the whole call, so the agent went
looking for a way around the tool. Every boolean and number parameter now
accepts "true", "false" and numeric strings; anything else is still
rejected. browser_batch steps go through the same schema as direct calls, so
they get the same defaults, and bad parameters fail the step by name instead of
reaching the extension.

Agents no longer ask to run an update that does nothing. When the Chrome
Web Store shipped an extension newer than the daemon on npm, every agent
session asked the user for permission to run taskwindow update, which could
only answer "already up to date". The agent now hears that there is nothing to
run yet, and is still told to update once npm has the newer daemon.

Install

Run npm install -g taskwindow@latest, then taskwindow install. The guided installer configures the daemon and selected coding agents and opens the Chrome Web Store listing; the extension pairs on its own after "Add to Chrome" and Chrome keeps it updated.

Manual archives are attached below (the extension zip is for taskwindow install --extension <zip>, the unpacked development route). Run taskwindow doctor for connection diagnostics or taskwindow pair for manual recovery.

See the README for the full guide.