Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

gstack – Garry Tan's Claude Code Setup

github.com

Post reply on HN
Print view View original

11–17 of 17 posts

Re: gstack – Garry Tan's Claude Code Setup

#12

Post by NamlchakKhandro »

zippolyon wrote: post #6

Not Claude Code specific — works with any Python agent via a one-line decorator. LangChain, AutoGen, CrewAI, or anything custom. Claude Code just gets a zero-config hook via .claude/settings.json. Pi-agent should work fine if it's Python-based.

what makes you think it's python based?

Re: gstack – Garry Tan's Claude Code Setup

#13

Post by zippolyon »

jiri wrote: post #4

Hmm. Is this claude code specific or can this be installed for pi-agent also? I guess I'll just ask pi ;-)

Not Claude Code specific — @k9 decorator works with any Python agent (LangChain, AutoGen, CrewAI). For Claude Code it hooks via .claude/settings.json, zero code changes. For pi-agent: if it's Python-based, yes it works. https://github.com/liuhaotian2024-prog/K9Audit

Re: gstack – Garry Tan's Claude Code Setup

#14

Post by zippolyon »

NamlchakKhandro wrote: post #12
zippolyon wrote: post #6

Not Claude Code specific — works with any Python agent via a one-line decorator. LangChain, AutoGen, CrewAI, or anything custom. Claude Code just gets a zero-config hook via .claude/settings.json. Pi-agent should work fine if it's Python-based.

what makes you think it's python based?

Fair point — it's Python-based if you use the @k9 decorator directly. For Claude Code specifically, the hook works regardless of what language the agent is written in, because it intercepts at the tool call level via .claude/settings.json.

Re: gstack – Garry Tan's Claude Code Setup

#15

Post by dmppch »

The role decomposition — distinct specialist personas for planning, review, QA, shipping — is the pattern worth paying attention to here, separate from the LOC debate. Then making them work together in a panel/team format.

I've been working on agent workflow tooling and what keeps surprising me is how quickly authoring the skills becomes the trivial part compared to keeping them composable and in sync across projects.

gstack's git-clone-and-copy install model works great solo, but I'm curious how it holds up when different repos need divergent review gates or QA flows — that's where every "just copy the skills folder" approach I've seen starts to buckle.

Post reply on HN