@qawolf/cli 1.24.0 → 1.25.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli.js +1935 -582
- package/dist/runner-sdk.js +567 -72
- package/package.json +1 -1
- package/skills/qawolf-cli/SKILL.md +2 -1
package/package.json
CHANGED
|
@@ -127,8 +127,9 @@ that `url`; never guess a route and never send a repository link in its place.
|
|
|
127
127
|
| --- | --- | --- |
|
|
128
128
|
| `qawolf agent get` | read | Read what the QA Wolf AI has said and whether it is still working. Poll this after agent.send until the status settles. A status of "waiting-for-you" means the last reply is a question the work is blocked on, and answering it with agent.send is what unblocks it. Replies accumulate, so a caller that polls repeatedly sees the earlier ones again. |
|
|
129
129
|
| `qawolf agent send` | write | Ask the QA Wolf AI to do a piece of work in plain language, such as covering a user journey, investigating a failing run, or fixing a broken flow. This is the one verb that starts work from nothing: every other write acts on a flow, run or issue that already exists. Answers as soon as the request is accepted, with the id to follow it by, because the work runs for minutes to tens of minutes. Poll agent.get for progress, and send here again to answer a question or add context to work already running. |
|
|
130
|
-
| `qawolf auth login` | local | Authenticate with
|
|
130
|
+
| `qawolf auth login` | local | Authenticate with QA Wolf in a browser or with an API key |
|
|
131
131
|
| `qawolf auth logout` | local | Remove stored credentials |
|
|
132
|
+
| `qawolf auth switch` | local | Choose which workspace to work in |
|
|
132
133
|
| `qawolf auth whoami` | read | Show authentication status |
|
|
133
134
|
| `qawolf automate` | write | Request automation for draft flows. First create a named local .flow.ts draft for every requested journey that does not already have a matching draft; never reuse a generic starter or placeholder. Each new draft must start with a JSDoc Goal: description, import flow from @qawolf/flows/web, and use export default flow(...); a comment-only file or direct test(...) call is not a valid draft. Commit and push all changes with Git to publish them, then list remote drafts to resolve every selected ID. Do not use patch to create or rename a selected flow. Finally make one automation request containing all requested flow IDs. |
|
|
134
135
|
| `qawolf doctor` | local | Diagnose problems running flows locally |
|