Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@karnstack/reins@0.6.0

Minor Changes

• f2b0801: reins do '<goal>' hands a small browser task to TypeSafe's Jev model: it reads the page, picks each click, field and dropdown with one Jev call per step, and types only the values the agent passed with --fill. It stops and prints the exact next command for risky clicks (buy, send, delete, ...), missing values, dialogs, leaving the site, or no progress. --continue resumes the run, and --confirm '<label>' pre-approves a click. Exit codes: 0 done, 2 stopped for input, 1 error. On the extension side: the jev_observe / jev_act handlers (site tier full), per-tab JS dialog tracking, and a pre-action re-check of each chosen element. Jev can also submit a search field with Enter (SUBMIT_SEARCH, search-like fields only), a click that opens a new tab moves the run to that tab, three stale acts in a row stop the run as stuck, and the summary line reports the Jev input tokens used. A click on a link that opens a new tab (target="_blank"), from reins click or reins do, no longer lets Chrome raise its window over the app you are working in: the extension opens the tab itself, next to the current one and active; reins click reports the new tab's id (openedTabId in --json).
• c7b6513: reins key set|status|clear typesafe stores a TypeSafe API key in ~/.reins/credentials.json (readable only by you), after checking it with TypeSafe. The extension popup gains a Jev section to save, replace or remove the same key. This is the setup for reins do. On the extension side: the popup gains the Jev key section and its reins:call frame carries a per-call timeout for the slow key check.
• 7736109: reins restart stops the background daemon and starts a fresh one, waiting for previously connected browsers to come back (and exiting 1 if they don't). After npm i -g @karnstack/reins@latest, the next tool command (e.g. reins tabs) notices a daemon older than the CLI and restarts it on the new version, instead of leaving the old code running; reins status and reins doctor point out the mismatch. reins kill now waits until the daemon has actually exited.

@reins/extension@0.6.0

Minor Changes

• f2b0801: reins do '<goal>' hands a small browser task to TypeSafe's Jev model: it reads the page, picks each click, field and dropdown with one Jev call per step, and types only the values the agent passed with --fill. It stops and prints the exact next command for risky clicks (buy, send, delete, ...), missing values, dialogs, leaving the site, or no progress. --continue resumes the run, and --confirm '<label>' pre-approves a click. Exit codes: 0 done, 2 stopped for input, 1 error. On the extension side: the jev_observe / jev_act handlers (site tier full), per-tab JS dialog tracking, and a pre-action re-check of each chosen element. Jev can also submit a search field with Enter (SUBMIT_SEARCH, search-like fields only), a click that opens a new tab moves the run to that tab, three stale acts in a row stop the run as stuck, and the summary line reports the Jev input tokens used. A click on a link that opens a new tab (target="_blank"), from reins click or reins do, no longer lets Chrome raise its window over the app you are working in: the extension opens the tab itself, next to the current one and active; reins click reports the new tab's id (openedTabId in --json).
• c7b6513: reins key set|status|clear typesafe stores a TypeSafe API key in ~/.reins/credentials.json (readable only by you), after checking it with TypeSafe. The extension popup gains a Jev section to save, replace or remove the same key. This is the setup for reins do. On the extension side: the popup gains the Jev key section and its reins:call frame carries a per-call timeout for the slow key check.