@fibteq/myrel-runner 0.8.0 → 0.9.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.
Files changed (4) hide show
  1. package/README.md +12 -0
  2. package/dist/cli.js +50 -50
  3. package/dist/index.js +46 -46
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -76,6 +76,18 @@ Read-only tasks (`--access read`) always run in the folder itself.
76
76
  With `edit`, the CLI can change files in the folder but cannot run commands that would need your approval. Use
77
77
  `full` only for folders and projects you trust: it lets the CLI run any command without asking.
78
78
 
79
+ ### Project folders and asking first
80
+
81
+ A project can list other folders besides its main one (Project settings > Folders). They must be shared on this
82
+ computer too; the CLI gets them with `--add-dir` (Claude Code, Codex) or `--include-directories` (Gemini CLI).
83
+
84
+ When Claude Code runs as a thread's agent, its permission prompts go to Myrel (`--permission-prompt-tool
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
88
+ `acceptEdits` and commands and web tools pre-allowed instead of `bypassPermissions`, so only files outside the folders
89
+ are asked about. Codex and Gemini CLI cannot ask mid-run, so they stay inside the folders.
90
+
79
91
  Tasks in the same Myrel thread continue the same Claude Code session (`--resume`), so follow-ups keep context.
80
92
 
81
93
  ### Your CLI as the thread's agent