Trust a folder's hooks

A project folder can come with hooks of its own, and DataMind Oda withholds them until you trust exactly the set you were shown. This page covers the trust banner that asks in a chat, the trust states, and how to stop trusting a folder.

The banner and the Hooks settings are part of the desktop app and the VS Code extension; the web app does not show them. Hooks covers the settings page and the hooks themselves.

Trust a folder's hooks

When you open a chat in a folder whose hooks are not trusted yet, a banner appears above the message box.

1. Read the title: This folder has {count} hooks in the Claude Code format (1 hook when the folder has one), with the folder's path below it and the message They run these commands on this computer automatically. Trust and run them?
2. Check the hooks: each sits on its own line as event · matcher · command, and a hook with no matcher reads every call. Up to five hooks are listed, and the rest are counted as and {count} more.
3. Choose Trust to approve exactly the hooks that were shown. They run in sessions in that folder from then on.
4. Choose Not now to set the question aside; the folder stays Not trusted and its hooks stay withheld.

• Trust approves the set as the banner showed it: if the hooks file changed in between, the new set is not trusted and the question comes back.
• If the answer cannot be saved, the banner shows Could not complete the change: {failure}.
• Once trusted, the folder's hooks run; Hook runs and changes in chat shows how each run appears in a chat.

The trust states

Settings > Hooks marks each of your project folders with one of three states, and the banner asks about the folder of the current chat.

• Trusted: you approved the folder's hooks as shown, and they run in that folder.
• Not trusted: the folder's hooks are withheld. The hint reads These hooks do not run until you trust this folder. Sessions with Full access run them without asking.
• Changed since you trusted them: you trusted an earlier set and the hooks changed afterwards, so they are withheld until you trust the new set.

Only a folder's hooks are trusted or withheld; your own hooks in Your hooks run in every folder.

When a trusted folder changes

• When the folder's hooks change after you trusted them, the folder flips to Changed since you trusted them and its hooks stop running.
• The hint becomes The hooks changed after you trusted this folder, so they do not run until you trust them again. Sessions with Full access run them without asking.
• In a chat in that folder, the banner asks again, titled The hooks in this folder changed since you trusted them. Check the new set, then choose Trust again if it is what you expect.

Full access sessions

• In a Full access session, a folder's untrusted hooks run without asking. The banner only informs: it is titled Full access: {count} project hooks run in this session, lists the hooks, and offers only Got it.
• Choose Got it to dismiss the notice. Nothing is recorded as trusted, so a later session without Full access asks about the folder again.
• Workspaces, files and permissions covers the access modes.

Stop trusting a folder

1. Open Settings > Hooks and find the folder's group. Its trust row shows when you trusted the folder.
2. Choose Stop trusting. The trust is revoked, the folder's hooks stop, and the folder reads Not trusted again; a chat in the folder asks again.

Questions, answered

When does the trust banner appear?

In a chat in a folder that has hooks you have not trusted yet, while Run hooks is on; in a Full access session it informs instead of asking. A folder with no hooks has nothing to trust, and once you trust the set the banner stays away until the hooks change.

What exactly does Trust approve?

Exactly the hooks the banner showed when you chose Trust: the same events, matchers and commands, for that folder. If the file changed after the banner was built, the new set is not trusted and the question comes back. Trust covers the hooks as listed, not the programs their commands run.

What happens when I choose Not now?

The folder stays Not trusted, so its hooks still do not run, and nothing is approved. Your own hooks keep running as usual.

Why does the trust banner keep coming back?

Not now sets the question aside in the window where you answered, and each window keeps its own answer. Any change to the folder's hooks brings the question back.

Why are only some of the folder's hooks listed?

The banner lists up to five hooks on their lines, then counts the rest as and {count} more. For the full set, open Settings > Hooks and the folder's group: it lists the folder's files and every hook, each with its own switch.

Why does the banner have no Trust button?

That session runs in Full access, where a folder's untrusted hooks run without asking; the banner only tells you that they do, and offers Got it. Nothing is recorded as trusted, so a later session without Full access asks about the folder again.

How do I stop trusting a folder?

Open Settings > Hooks, find the folder's group and choose Stop trusting. The folder's hooks stop and it reads Not trusted again; the row shows when you trusted the folder.

Does the banner update on its own?

Yes. Oda keeps checking the folder while the chat is open, so hooks added or changed since the banner was built appear on their own; you do not reopen the chat.

Can I trust just one hook from a folder?

No. Trust covers the folder's set as shown, so the set is approved together. To keep one hook from running, turn off its own switch in Settings > Hooks; see Hooks.