Repository navigation
Rules
keel checks every agent with rules. Build › Rules shows all of them in plain words.
an agent wants to act ──► keel's hook checks it ──► allowed ──► it runs
│ │
└─► refused: the agent reads why ▼
after the step: keel compares the files
and puts back what the phase does not allow
-
Always on:
.envfiles, keel's own rule files (.keel/config.yml,.keel/rules/), old migrations, force push,--no-verify, commits and history rewrites inside a flow, secrets and switched-off tests in an edit, and keel's own sign-in keys. These never switch off. -
You can switch off: generated files, build output,
-x test, new packages, reading a file twice, big-file reads, the push gate, MCP tools that change things. Off is saved in.keel/config.yml(rules.off). -
Your lists (
.keel/config.yml): protected files, generated files, build output, shell commands,mcp.allow, the big-file limit (read_guard_max_lines, default 2000 lines; 0 = off), the push gate, architecture boundaries. The page edits them in place; only theguards,mcp,rulesandboundariesparts are rewritten. -
Rule packs: your own rules, one YAML file each in
.keel/rules/, shared with the team through git. Library installs one (strict secrets, no new dependencies, migrations only in a flow, frontend can't touch the API, Spring, Node, Python); New rule writes one with a form or as YAML; Check and try it says which of the project's recent tool calls it would have refused. Export and Import move a pack between projects. The Marketplace has rule packs too.
schema: 1
name: no-deploys # the id and the file name: .keel/rules/no-deploys.yaml
title: No deploys
version: 1.0.0
rules:
- id: no-kubectl
kind: bash # bash | edit | read | mcp
match: [kubectl apply]
phases: all # all | in-flow | none | [green, refactor]
reason: Deploys are a person's job.The whole format (publisher, summary, requires, every field of a rule) is in
docs/rules/pack-format.md. A pack file is shaped like a plugin's manifest, so the same file can
later come from the Marketplace; the Rules page shows where each pack came from (keel's library, your own, the
marketplace) and its version.
Which engine checks what, when. Each rule on the page shows one sign per engine:
| Sign | Means |
|---|---|
| ✓ | checked before the action: it never happens |
| ◐ | checked before for git, gh, the package managers and file printers only |
| ↺ | checked after the step: keel puts the file back |
| ✗ | not checked by this engine |
Claude, OpenCode, API-key models and Codex 0.150+ are checked before every action. Copilot has no hook keel can load: its shell commands go through keel's command wrappers, and its file edits are only checked after each step. The model picker says so when you choose Copilot or Codex.
Rules now on the Flow page says, for the phase that runs: what agents may change (✓), what they may not (✗), what never (🔒), the files you allowed, your rule packs, which rules stopped something (how often, before the action or after the step), how well the running engine is checked, and the last command an agent saw fail.
When keel cannot read the rules (no guard context, or an error in the hook) it fails closed: only reads pass, and
.env files and build output stay refused. Everything else waits until it is fixed.
From docs/GUIDE.md · All pages
keel v2
- Home
- How a flow works
- Flows in detail
- Web research
- Rules
- KeelBot
- keel TUI (keel2 tui)
- Thinking effort
- Plugins and the Marketplace
- Stacks
- Plugins: Database, Git and CI/CD
- Quality
- Inbox and run modes
- Usage and caps
- Tasks and Jira
- Logins
- Signing in
- Use keel from Claude Code or Claude Desktop (MCP)
- keel2 commands
- Where keel keeps its files (layouts)
- Native mode (no Docker)
- Docker mode
- Several project folders
- Git worktree projects
- Problems
- Folders in the container
- Without the install script
- Develop keel v2