claude-warden 1.10.0 → 2.0.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/.claude-plugin/marketplace.json +1 -1
- package/.claude-plugin/plugin.json +2 -2
- package/README.md +29 -8
- package/dist/codex-export.cjs +20234 -0
- package/dist/index.cjs +17 -11
- package/package.json +2 -1
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
|
-
"name": "
|
|
3
|
-
"version": "
|
|
2
|
+
"name": "warden",
|
|
3
|
+
"version": "2.0.1",
|
|
4
4
|
"description": "Smart command safety filter for Claude Code — parses shell pipelines and evaluates per-command safety rules to auto-approve safe commands and block dangerous ones",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "banyudu"
|
package/README.md
CHANGED
|
@@ -48,7 +48,7 @@ Two commands inside Claude Code:
|
|
|
48
48
|
|
|
49
49
|
```
|
|
50
50
|
/plugin marketplace add banyudu/claude-warden
|
|
51
|
-
/plugin install
|
|
51
|
+
/plugin install warden@claude-warden
|
|
52
52
|
```
|
|
53
53
|
|
|
54
54
|
That's it. Restart Claude Code and Warden is active.
|
|
@@ -68,6 +68,27 @@ cd claude-warden && npm install && npm run build
|
|
|
68
68
|
claude --plugin-dir ./claude-warden
|
|
69
69
|
```
|
|
70
70
|
|
|
71
|
+
## Codex CLI (experimental)
|
|
72
|
+
|
|
73
|
+
Codex currently uses `execpolicy` (`.rules` files) for command approvals. Warden can export your effective command-level decisions to a Codex rules file:
|
|
74
|
+
|
|
75
|
+
```bash
|
|
76
|
+
pnpm run build
|
|
77
|
+
pnpm run codex:export-rules
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
This writes `.codex/rules/warden.rules` in the current project by default.
|
|
81
|
+
|
|
82
|
+
- Use `--cwd <dir>` to choose which workspace config to load.
|
|
83
|
+
- Use `--out <path>` to choose an output path.
|
|
84
|
+
- Use `--stdout` to print the generated rules.
|
|
85
|
+
|
|
86
|
+
Example:
|
|
87
|
+
|
|
88
|
+
```bash
|
|
89
|
+
node dist/codex-export.cjs --cwd . --out .codex/rules/warden.rules
|
|
90
|
+
```
|
|
91
|
+
|
|
71
92
|
## Configure
|
|
72
93
|
|
|
73
94
|
Warden works out of the box with sensible defaults. To customize, create a config file:
|
|
@@ -140,13 +161,13 @@ Need to temporarily bypass all permission prompts? YOLO mode auto-allows all com
|
|
|
140
161
|
### Activate via slash command
|
|
141
162
|
|
|
142
163
|
```
|
|
143
|
-
/
|
|
144
|
-
/
|
|
145
|
-
/
|
|
146
|
-
/
|
|
164
|
+
/warden:yolo session # Full session, no expiry
|
|
165
|
+
/warden:yolo 5m # 5 minutes
|
|
166
|
+
/warden:yolo 15m # 15 minutes
|
|
167
|
+
/warden:yolo off # Turn off immediately
|
|
147
168
|
```
|
|
148
169
|
|
|
149
|
-
Running `/
|
|
170
|
+
Running `/warden:yolo` with no arguments shows a menu of duration options.
|
|
150
171
|
|
|
151
172
|
### How it works
|
|
152
173
|
|
|
@@ -156,14 +177,14 @@ YOLO mode is **session-scoped** — it only affects the current Claude Code sess
|
|
|
156
177
|
|
|
157
178
|
When Warden prompts you for permission (`ask` decision), the system message includes a tip about YOLO mode so you can discover it when you need it most.
|
|
158
179
|
|
|
159
|
-
## Feedback and `/
|
|
180
|
+
## Feedback and `/warden:allow`
|
|
160
181
|
|
|
161
182
|
When Warden blocks or flags a command, it includes a system message explaining:
|
|
162
183
|
|
|
163
184
|
1. **Why** the command was blocked/flagged (per-command reasons)
|
|
164
185
|
2. **How to allow it** — a ready-to-use YAML snippet for your config
|
|
165
186
|
|
|
166
|
-
Use the `/
|
|
187
|
+
Use the `/warden:allow` slash command to apply the suggested config change. It will ask which scope (project or user) to use.
|
|
167
188
|
|
|
168
189
|
## Built-in defaults
|
|
169
190
|
|