abc/analysis_claude_code
1
0
Fork 0
mirror of https://github.com/shareAI-lab/analysis_claude_code.git synced 2026-08-07 12:33:46 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix(s03): let Gate 2 own the workspace boundary instead of safe_path

Browse Source 
safe_path hard-raised on out-of-workspace paths while Gate 2 asked about the same condition, so approving an out-of-workspace write never took effect. Make the permission pipeline the sole boundary authority: drop safe_path, resolve paths directly in the file tools, and extend the Gate 2 rule to read_file. Sync all three READMEs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Viper
2026-07-27 20:27:22 +08:00
committed by root
parent a9cafe953a
commit 4d8d420e41
4 changed files with 11 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
s03_permission/README.en.md
View File

@@ -28,7 +28,7 @@ The three gates correspond to three decisions:
| Gate | Purpose | On Match |
|------|---------|----------|
| 1. Deny List | Permanently forbidden operations (`rm -rf /`, `sudo`) | Denied immediately, not executed |
| 2. Rule Matching | Context-dependent operations (writing outside workspace, `rm` files) | Passed to Gate 3 |
| 2. Rule Matching | Context-dependent operations (reading/writing outside workspace, `rm` files) | Passed to Gate 3 |
| 3. User Approval | After Gate 2 matches, pauses for user confirmation | User decides allow or deny |
None of the three gates match → execute directly. Most routine operations take this path.
@@ -59,7 +59,7 @@ def check_deny_list(command: str) -> str | None:
```python
PERMISSION_RULES = [
{
"tools": ["write_file", "edit_file"],
"tools": ["read_file", "write_file", "edit_file"],
"check": lambda args: not (WORKDIR / args.get("path", "")).resolve().is_relative_to(WORKDIR),
"message": "Writing outside workspace",
},