agentusecasesAll 965 use cases
Software & DevOps

Port Claude Code hooks to pi extensions

After leaving Claude, the author pointed an agent at their Claude hooks folder and had it rebuild them as a pi extension, which it did quickly.

Done withClaude Code

What they did
The author had built up a collection of Claude Code hooks over several months. Unlike skills, hooks use a Claude-specific format, so they were the hardest part to migrate to pi. They pointed an agent at the Claude hooks folder and told it to make them work in pi, as a pi extension.
How it went
According to the author, the agent did the port very quickly. The comment gives no details on how well the hooks worked afterward, or on what was checked or fixed by hand.
Worth knowing
Hooks don't carry over between tools the way skills do, so give the agent your whole hooks folder as the reference when asking it to build the extension.

Try it yourself with Claude Code

Read the hooks in my folder [path to .claude/hooks or settings] and rebuild each one as an extension for [new agent or tool name], following its extension docs at [docs URL]. Keep the same behavior for each hook and write a short test or example run for each. Stop when every hook has an equivalent, and list any that can't be ported exactly.

Read the original ↗

Source: HN · Apr 20, 2026

Five of these in your inbox every morning

The best things people got an AI agent to do, each with the prompt to try it.

More like this