Customization

Agent Hooks Manager

Every hook your agents have configured, in one dialog — Claude, Codex, Gemini, Kimi, Cursor, Kiro, Devin, Qwen, Qoder, Grok and more. Flip one off with a switch, pause a whole agent's set, and read the journal of every edit.

Agent Hooks Manager

Why You Need This

How this feature boosts your daily productivity

Hooks run commands automatically at set points in an agent's work, and they accumulate across a dozen config files you never open — so when one misfires you are grepping JSON to find out which agent owns it. Open it from Tools → Hooks or Settings → Agents → Open hook manager and every hook is grouped by agent with the config profile it reads, each row naming when it runs (Before a tool runs, After a tool finishes, When a session starts, When you send a prompt…), the file it came from, whether it is user or project scope, and who owns it. A switch edits the agent's real config file and offers Undo afterwards; Pause my hooks captures the currently enabled set and restores exactly that set when you unpause. 1DevTool's own session-tracking integrations, organization policies and plugin-owned hooks show read-only with the reason and are never rewritten.

How It Works

Get started in 4 simple steps

1
1

Open the hook manager

Tools → Hooks in the AI group, or Settings → Agents → Open hook manager — both land on the same dialog, which scans and shows when it last ran.

2
2

Read a hook without opening its file

Hooks are grouped by agent with the config profile each group reads. Every row says when it runs — Before a tool runs, After a tool finishes, When a session starts, When you send a prompt — plus its config file, user or project scope, and who owns it.

3
3

Find the one you mean

Search by name, event or match, and filter by agent, scope or status — including a view of just the entries that need attention.

4
4

Switch it off, or pause the set

A switch edits the agent's real config file and offers Undo afterwards. Pause my hooks captures the currently enabled set and disables it; unpausing restores exactly that set. The Changes tab journals every write.

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

$ cat ~/.claude/settings.json
$ cat .codex/config.toml
$ cat ~/.gemini/settings.json
# which one runs that command?
# comment it out, restart, try again
# forget to put it back

The 1DevTool Way

Tools -> Hooks 79 on · 0 off
Claude Profile: Default 23 on
Before a tool runs ~/.claude/settings.json [On]
After a tool finishes · 1devTool [Read-only]
Pause my hooks -> restores exactly that set

Key Capabilities

Everything included with Agent Hooks Manager

List every hook your agents have configured, grouped by agent
Cover Claude, Codex, Gemini, Kimi, Cursor, Kiro, Devin, Qwen, Qoder and Grok
See when each hook runs, its config file, its scope and its owner
Search by name, event or match and filter to entries needing attention
Turn a hook off or on with a switch that edits the real config file
Undo a save, with the exact definitions it changed
Pause one agent's hooks and restore exactly the set that was on
Read a journal of every change the manager wrote
Open a hook's config file in the editor or reveal it on disk

Why It Matters

The productivity impact of having customization built into your workspace

Your Editor, Your Rules

Every shortcut, font, theme, and layout is configurable. Make 1DevTool feel like home.

Eye Comfort

Dark and light themes tuned for all-day coding. Reduce eye strain with the right contrast for your environment.

Muscle Memory Friendly

Remap shortcuts to match your existing habits. No relearning required when switching from VS Code or Vim.

Per-Project Defaults

Different projects can have different terminal types, default URLs, and behavior settings.

Ready to boost your workflow?

Download 1DevTool for free and experience Agent Hooks Manager along with 314 other features — all in one app.