NCBM/plyngent
1
0
Fork 0
mirror of https://github.com/NCBM/plyngent.git synced 2026-11-07 07:17:54 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: describe YOLO skipping YOLO-tagged confirms

Browse Source 
Session YOLO skips the soft confirms of `YOLO`-tagged tools — interpreter runs included — while untagged tools keep prompting and a command that escalates privileges keeps its own confirm through `DangerReason(yolo_skip=False)`. A plugin now also sees that answer shape where the danger classifier is documented, and the round's aggregated prompt leaves the covered calls out.
This commit is contained in:
worldmozara
2026-10-21 19:10:56 +08:00
parent 8ec63aa6a2
commit 4c597274e7
2 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/plugins.md
+4 -2
View File
@@ -48,8 +48,10 @@ Notes:
- Session-only helpers may add **`PUBLIC`** and **`SESSION_STATE`** when they
only touch session data and host-approved APIs (see plans under `doc/plans/`).
- Optional soft-confirm bits: **`YOLO`** (eligible for YOLO auto-approve),
**`TRUSTABLE`** (grant once per session after approve). Hard denylists are
never YOLO-skipped.
**`TRUSTABLE`** (grant once per session after approve). The host's danger
classifier may refuse that skip for one call by returning
`DangerReason(text, yolo_skip=False)` — plyngent does so for a command that
escalates privileges. Hard denylists are never YOLO-skipped.
- Optional host-policy bit: **`READ_ONLY`** marks tools that never mutate host
state — they become eligible for read-only contexts such as
`/btw --tools=read` side turns or planning. Tools that only sometimes mutate