Menu

1 / 2

I built a permission-first CLAUDE.md + agent stack for Claude Code (free, MIT)

DEV Community·Sabahattin Kalkan·6 months ago
#Isq3LmMC
#ai#claudecode#devtools#agent#claude
Reading 0:00
15s threshold

I've been using Claude Code daily for months. And I kept hitting the same wall:

The agent would just start doing things . No plan. No approval. Just... acting.

It deleted files I didn't want deleted. It refactored things I didn't ask it to refactor. It made "helpful" assumptions that broke my architecture.

So I built Full Stack HQ — a configuration kit that enforces a permission-first workflow. Here's what I learned.

The core problem with AI coding agents

Most people configure their AI agent once (or never) and just... let it go. The result is an agent that:

Makes assumptions about what you want

Takes irreversible actions without asking

Mixes planning and execution in the same step

Has no consistent code style or architectural awareness

The agent is powerful but unpredictable. That's the worst combination in software development.

The solution: permission-first workflow

Nothing happens without your explicit approval.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.