This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Clooks
Claude Code hooks that don't break silently
Clooks is a TypeScript hook runtime for Claude Code - because wiring shell commands into JSON and hoping every guardrail behaves isn't good enough. If a hook crashes, the action can still slip through, risky command and all. Clooks gives you typed context, reusable config, clear execution order, and team-wide guardrails that live in your repo. Write the hook once. If it breaks, the agent stops.
At Playbook, we run sophisticated agentic workflows across the entire team. But even the best workflows can't always accommodate how every individual prefers to work - leading to weird workarounds or begrudging acceptance.
Claude Code Hooks are shell commands wired into JSON: no typing, no composition, and no good way to adapt them to your workflow if it doesn't quite match your team's defaults. Worse, if a Claude Hook crashes, the action can still fall through the gaps - and oops, that destructive command just slipped through because your bash script was buggy. (Claude ignores hooks that threw errors by default.)
Clooks came out of that frustration: a more powerful TypeScript runtime for Claude Code Hooks.
Hooks can live in your repository committed alongside your code, so once your team has Clooks installed, everyone runs the same guardrails automatically. You can also install Clooks globally, so your personal hooks can follow you across every Claude Code session across your computer.
On crashes, Clooks catches the error, blocks and informs claude about it. Hooks are fully typed, testable in isolation and composable, so Claude can help write and validate them with autocomplete instead of guessing at shell scripts.
What Clooks gives you:
Crash blocking - if a hook breaks, the action stops by default. Claude will wait for you.
Typed TypeScript hooks - typed contexts - stop guessing at documentation and trust the typing.
Built-in testing - Claude can generate realistic payloads and test them directly against the code using clooks
Repo + global hooks - write entire hook workflows or guardrails for your team, or just for yourself
Layered Configuration - re-use and layer your configurations so you can adjust it until it's perfect for you
Ordered and parallel pipelines - Set up more complex flows, rewriting commands as they go without interrupting your agent's focus
Hot Reload - configuration & new hooks work immediately, no need to restart your sessions
Marketplace+Plugin installs - If you see a set of hooks you like, install it either through clooks or as if you're installing a claude plugin - clooks will automatically detect and copy over the hooks
Clooks is MIT licensed and open source.
Long-term, my goal is a full agent-agnostic ecosystem: We write the hooks once, and they work, whether you're on Claude Code, Codex, OpenCode, or whatever comes next.
You can install clooks with this one-liner and claude will walk you through:
claude plugin marketplace add codestripes-dev/clooks-marketplace && claude plugin install clooks@clooks-marketplace && claude /clooks:setup
Then try installing the suggested built-in hooks, or ask claude to create one for you, like:
/clooks:create-hook Write me a hook that tracks every bash command that a subagent does.
There's still so many more feature ideas I have floating about how we can make this the best tool for everyone. I'd love feedback from anyone using Claude Code hooks extensively: what guardrails have you built, and where do native hooks still feel painful?
About Clooks on Product Hunt
“Claude Code hooks that don't break silently”
Clooks was submitted on Product Hunt and earned 11 upvotes and 1 comments, placing #94 on the daily leaderboard. Clooks is a TypeScript hook runtime for Claude Code - because wiring shell commands into JSON and hoping every guardrail behaves isn't good enough. If a hook crashes, the action can still slip through, risky command and all. Clooks gives you typed context, reusable config, clear execution order, and team-wide guardrails that live in your repo. Write the hook once. If it breaks, the agent stops.
On the analytics side, Clooks competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Clooks performed against the three products that launched closest to it on the same day.
Who hunted Clooks?
Clooks was hunted by Joe Degler. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Clooks including community comment highlights and product details, visit the product overview.
Joe Degler
Hey Product Hunt 👋
At Playbook, we run sophisticated agentic workflows across the entire team. But even the best workflows can't always accommodate how every individual prefers to work - leading to weird workarounds or begrudging acceptance.
Claude Code Hooks are shell commands wired into JSON: no typing, no composition, and no good way to adapt them to your workflow if it doesn't quite match your team's defaults. Worse, if a Claude Hook crashes, the action can still fall through the gaps - and oops, that destructive command just slipped through because your bash script was buggy. (Claude ignores hooks that threw errors by default.)
Clooks came out of that frustration: a more powerful TypeScript runtime for Claude Code Hooks.
Hooks can live in your repository committed alongside your code, so once your team has Clooks installed, everyone runs the same guardrails automatically. You can also install Clooks globally, so your personal hooks can follow you across every Claude Code session across your computer.
On crashes, Clooks catches the error, blocks and informs claude about it. Hooks are fully typed, testable in isolation and composable, so Claude can help write and validate them with autocomplete instead of guessing at shell scripts.
What Clooks gives you:
Crash blocking - if a hook breaks, the action stops by default. Claude will wait for you.
Typed TypeScript hooks - typed contexts - stop guessing at documentation and trust the typing.
Built-in testing - Claude can generate realistic payloads and test them directly against the code using clooks
Repo + global hooks - write entire hook workflows or guardrails for your team, or just for yourself
Layered Configuration - re-use and layer your configurations so you can adjust it until it's perfect for you
Ordered and parallel pipelines - Set up more complex flows, rewriting commands as they go without interrupting your agent's focus
Hot Reload - configuration & new hooks work immediately, no need to restart your sessions
Marketplace+Plugin installs - If you see a set of hooks you like, install it either through clooks or as if you're installing a claude plugin - clooks will automatically detect and copy over the hooks
Clooks is MIT licensed and open source.
Long-term, my goal is a full agent-agnostic ecosystem: We write the hooks once, and they work, whether you're on Claude Code, Codex, OpenCode, or whatever comes next.
You can install clooks with this one-liner and claude will walk you through:
Then try installing the suggested built-in hooks, or ask claude to create one for you, like:
There's still so many more feature ideas I have floating about how we can make this the best tool for everyone. I'd love feedback from anyone using Claude Code hooks extensively: what guardrails have you built, and where do native hooks still feel painful?