@omniaibot/win-x64 1.6.13 → 1.6.14
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.
|
@@ -1 +1 @@
|
|
|
1
|
-
1.6.
|
|
1
|
+
1.6.14
|
|
@@ -47,30 +47,19 @@ This skill is an execution specification for agents. It is not a human command m
|
|
|
47
47
|
- Parse JSON output from commands that return JSON.
|
|
48
48
|
- Do not claim success without verification evidence.
|
|
49
49
|
|
|
50
|
-
### Runtime
|
|
50
|
+
### Runtime
|
|
51
51
|
|
|
52
|
-
|
|
52
|
+
Use the installed `omnibot` command that is available to the user. Before an
|
|
53
|
+
agent-driven browser workflow, verify that the CLI is available and inspect the
|
|
54
|
+
relevant command help when needed:
|
|
53
55
|
|
|
54
56
|
```bash
|
|
55
57
|
command -v omnibot
|
|
56
58
|
omnibot --version
|
|
57
59
|
```
|
|
58
60
|
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
For a source-checkout test, make this concrete before the first browser action:
|
|
62
|
-
define the command prefix once:
|
|
63
|
-
|
|
64
|
-
```bash
|
|
65
|
-
export OMNIBOT="uv run omnibot --no-start"
|
|
66
|
-
```
|
|
67
|
-
|
|
68
|
-
stop any existing daemon, start the workspace daemon with
|
|
69
|
-
`uv run python -m omnibot --api-port 18764 --ws-port 18765 daemon run`, and
|
|
70
|
-
invoke every subsequent CLI command as `$OMNIBOT ...` (or the
|
|
71
|
-
workspace `.venv/bin/omnibot --no-start ...`). Never use bare `omnibot` in that
|
|
72
|
-
workflow, because it can auto-start the globally installed packaged daemon and
|
|
73
|
-
silently test different code.
|
|
61
|
+
The CLI manages its local daemon automatically. Do not depend on a source
|
|
62
|
+
checkout, Python environment, repository files, or developer-only commands.
|
|
74
63
|
|
|
75
64
|
## Native Command Router
|
|
76
65
|
|
|
Binary file
|