Skip to content
BENIBIX Learn

allowManagedHooksOnly

AI⌨️ Claude CodeConfiguration

Also known as allowManagedHooksOnly setting

The key that lets only the company's hooks run.

Think of it like

It is like a school where only the teacher's alarms may ring. Alarms kids bring stay quiet.

Example

Emma's company found a hook in a repo that sent code to an outside server. IT turns this key on, and only its own hooks run.

Why it matters

A hook runs a command on your machine, so a hook from a cloned repo is a real risk.

Definition

allowManagedHooksOnly is a key for managed settings. It lets only IT's hooks run. Set to true, it skips hooks in user, project and local files. Hooks still run if they come from IT, from the Agent SDK, or from a plugin IT turns on. It is read from managed settings only.

Example code

json
{
  "allowManagedHooksOnly": true
}
Run only the hooks IT sends out.
Each lockdown key takes one thing away from people's own files.

Common mistake

Putting it in a user or project file. It only works from managed settings.

Key takeaways

  1. 1
    Company hooks only. Others skipped.
  2. 2
    SDK hooks still run. And forced plugins.
  3. 3
    Managed only. Nowhere else.