@fibteq/myrel-runner 0.14.0 → 0.14.1
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/README.md +7 -0
- package/dist/cli.js +42 -40
- package/dist/index.js +29 -27
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -104,6 +104,13 @@ the ones it would ask about come to you as a card in the thread. Your Claude acc
|
|
|
104
104
|
Antigravity CLI cannot ask mid-run, so for them `auto` is the same as `edit` (Antigravity's own auto mode needs its
|
|
105
105
|
terminal sandbox and is missing on business accounts).
|
|
106
106
|
|
|
107
|
+
Antigravity CLI is stricter than Codex below `full`: there is no sandbox where its commands run on their own. A
|
|
108
|
+
command, a web page or a file outside the folders needs approval, which it cannot ask for when Myrel runs it, and
|
|
109
|
+
being declined ends the whole run with no answer. So with `read`, `edit` and `auto` it is told to keep to the files
|
|
110
|
+
and Myrel's tools, and a run that still stops says which permission stopped it. Give it `full` to let it run
|
|
111
|
+
commands, or allow single ones under `permissions.allow` in `~/.gemini/antigravity-cli/settings.json` (e.g.
|
|
112
|
+
`command(git)`).
|
|
113
|
+
|
|
107
114
|
With `edit`, the CLI can change files in the folder but cannot run commands that would need your approval. Use
|
|
108
115
|
`full` only for folders and projects you trust: it lets the CLI run any command without asking.
|
|
109
116
|
|