You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,11 +38,11 @@ When refactoring replaces an old path, delete the old one. No back-compat shims,
38
38
## Build & Validation
39
39
40
40
```bash
41
-
bun run typecheck
42
-
bun run build
43
-
bun run test
41
+
bun run check
44
42
```
45
43
44
+
`bun run check` is the single pre-PR gate: it runs `lint`, `typecheck`, `build`, and `test`, in that order, matching CI.
45
+
46
46
Run the full suite before declaring any task complete. Do not substitute individual targets. If a failure is pre-existing and unrelated to your change, say so explicitly.
47
47
48
48
`bun run test` runs `bun test ./src ./tests ./evals`. A bare `bun test` also
write-free. Shell file-writes stay denied. Spawn is a judgment call,
188
+
not a tool ban.
189
+
190
+
-**Exec and capability evals can run as a chosen primary director.**
191
+
`corbits exec --director <id>` (and eval `--director`) overlays that
192
+
package's system prompt and initially-advertised tool set on the product exec path.
193
+
Omit / skywalker keep the default Skywalker session. Directors that
194
+
cannot spawn (for example build) do not mount `task`. This is an
195
+
exec/eval/CI override, not a TUI or single-agent mode.
196
+
14
197
## [0.2.99] - 2026-08-21
15
198
16
199
Skywalker is the primary orchestrator over a closed director fleet: product write tools stay off the primary, and you cannot spawn Skywalker as a task leaf. Workers are not done until they return the four-heading report. First-party action skills ship as slashes; eval runners require an explicit provider/model pair; the style skill no longer refuses non-git folders.
Wrappers such as `bash -c '…'`, `sh`/`zsh -c`, `xargs`, and transparent prefixes (`env`, `nice`, `timeout`) are peeled so the same rules apply to the inner command. Unparseable wrappers fall through to ask rather than auto-allow.
103
103
104
-
Catastrophic patterns (`rm -rf /`, `sudo`, `curl | bash`, force-push, open-ended `find`/`rg`/`grep -r`, …) are always denied by authorization, independent of auto mode. `--dangerously-skip-permissions`(and mid-session `/yolo`in the TUI) is a separate escape hatch that bypasses the permission gate (not secret-guard path denies or authz hard blocks).
104
+
Catastrophic patterns (`rm -rf /`, `sudo`, `curl | bash`, force-push, open-ended `find`/`rg`/`grep -r`, …) are always denied by authorization, independent of auto mode. `--dangerously-skip-permissions`still forces this process; `/yolo`persists as the user-global default. Both bypass the permission gate (not secret-guard path denies or authz hard blocks).
105
105
106
106
Details live in `docs/PRODUCT.md` (safety model) and `docs/ARCHITECTURE.md` (permission gate and auto-shell policy).
0 commit comments