@fibteq/myrel-runner 0.9.0 → 0.10.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.
Files changed (4) hide show
  1. package/README.md +4 -2
  2. package/dist/cli.js +59 -58
  3. package/dist/index.js +55 -54
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -83,8 +83,10 @@ computer too; the CLI gets them with `--add-dir` (Claude Code, Codex) or `--incl
83
83
 
84
84
  When Claude Code runs as a thread's agent, its permission prompts go to Myrel (`--permission-prompt-tool
85
85
  mcp__myrel__approve_access`). If a step reaches a file outside the project's folders, Myrel asks you in the thread
86
- (Allow once, Add to project, Don't allow) and the step waits for your answer. A prompt about something inside the
87
- folders is about the access level above and is declined as before. With `full`, Claude Code then runs with
86
+ (Allow once, Add to project, Don't allow) and the step waits for your answer. A command or web request the access
87
+ level does not allow on its own (with `edit`: `git commit`, `git push`, tests) is asked about the same way (Run it,
88
+ Allow commands this turn, Don't run), so there is no need to restart the runner with `--access full` for one task. A
89
+ file change inside the folders with `read` is declined as before. With `full`, Claude Code then runs with
88
90
  `acceptEdits` and commands and web tools pre-allowed instead of `bypassPermissions`, so only files outside the folders
89
91
  are asked about. Codex and Gemini CLI cannot ask mid-run, so they stay inside the folders.
90
92