Answer a prompt once

Making a rule

Always on a card, or ⌘R, allows the request and saves a rule for the current project. AgentNod suggests the pattern from the request: the first two words of a command, such as npm test *, or the folder of the file being edited.

Rule… opens the full form: the pattern, allow or deny, this project or everywhere, this agent or any.

Always appears where Claude's own prompt would offer it, so it is absent for destructive commands, commands that touch secrets and commands with shell expansion.

Written through to Claude Code

For Claude Code, an allow rule is also added to permissions.allow, in Claude's own form: Bash(npm test:*). Claude then stops raising the prompt, in the terminal as well as in AgentNod.

The entry has the same reach as the rule. A rule for one project goes into that project's .claude/settings.local.json, the file Claude's own "Yes, and don't ask again" writes to. Claude Code keeps it at the root of the repository and reads it there only, in every folder and worktree of that repository. A rule for everywhere goes into ~/.claude/settings.json, which Claude Code reads in every project.

Always makes a project rule. Everywhere is a choice in the Rule… form, and the switch beside it says which of the two files the entry goes to. Turn the switch off and the rule stays in AgentNod, which answers for it instead.

AgentNod keeps a new settings.local.json out of git through the repository's .git/info/exclude, as Claude Code does for one it creates.

Deleting a rule in Settings → Rules removes its entry from Claude's allow list. Uninstalling the Claude Code hooks removes every entry AgentNod added and keeps the rules. An entry that was in the list before the rule was made is left alone.

Rules for Codex and Cursor live in AgentNod. The request still reaches the hook, and the rule replies for you.

Reading them back

Settings → Rules lists each rule as a sentence, for example "Allow Bash npm test * · Any agent, in api-server", with how many times it has answered, the Claude Code file its entry is in, and a bin to delete both.

The dashboard counts how many of the day's decisions were answered by rules.

Several at once

When more than one low-risk request is waiting, the inbox offers a button such as "Allow 3 safe". It allows the requests that read, or write inside the repo, and leaves the rest as cards.