Rebuild Claude hooks as a pi extension

A developer had an agent convert a folder of Claude Code hooks into a pi extension after switching tools.

Done with Claude Code· Intermediate· Apr 2026

What they did
They had spent months collecting Claude Code hooks, which use a Claude-only format. To move them over, they gave an agent the whole hooks folder and asked it to recreate each hook as part of a pi extension.
How it went
The agent finished the port quickly. The write-up doesn’t say whether the rebuilt hooks were tested, or whether any parts needed manual cleanup.
Tips
When you ask for a migration like this, provide the full hooks directory so the agent can see the complete setup. Have it pause before any step that would submit, delete, or change live configuration.

Try it yourself with Claude Code

I’m moving from [old tool] to [new tool]. Review everything in [path to hooks folder] and rebuild each hook as an extension for [new tool], using the extension guide at [docs URL]. Keep the same behavior as closely as possible, and for each item, include a small test or example run. Before you do anything that would overwrite live files, delete anything, submit anything, or make an irreversible change, stop and ask for my approval. When you’re done, list each hook, what was ported, and anything you could not match exactly.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on news.ycombinator.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.