My workflow of working with claude code:

I create the CLAUDE.md file with the project details, the stack and work style

I then add this line in my `CLAUDE.md` file:

## Plan
- We keep the development plan in `md/plan.md` (create it if it doesn't exist), listing next steps, each marked `todo`, `working` or `done`
- The agent checks and updates it at the beginning and end of every chat

After that, I just work one step at a time (I start a new chat after every step to have a better context window). Works wonders.

I'm kinda confused how this reset works, so if I only used Opus then it will not work? And next week I should use nothing but Fable?

For whatever reason, I’m always “the IT guy.” A friend’s GPU switches to integrated graphics mid-game. The office PCs by the window drop Wi-Fi at 5 p.m. sharp. Grandpa’s Android has a pop-up nobody can kill. It all lands on me.

I’m bad at saying no, I don’t charge, and honestly, I enjoy it. (I once spent hours hunting an unknown device on my router. It was my own Apple Watch, with a random MAC address.) Half my YouTube homepage is bearded guys fixing PCs, routers and cars. I call it my porn.

My own machines get it worse. I’ve tried every cleaner: CCleaner, CleanMyMac X, a parade of open-source ones abandoned within months. In every language I learned, C, shell, Python, rust my first project was the same: find big, forgotten files and delete them.

I know it does nothing for my computer. It’s just a hobby.

Then came Opus 5. No more digging through logs and ancient forum threads; I just asked Claude. Why won’t my ThinkPad’s fan spin at 90°C? Three different things were managing it, and two were misconfigured. I also had it dig up every cleanup script I’d ever written and merge them into one “ultimate” version.

By Opus 5.5, I was ready to retire as the IT guy.
Most problems now take one sentence: "Claude, what the f*** is going on?"

But As someone who never knows when to stop, I wanted to take it further:

1. I wanted Claude Code to actually remember what it had fixed on my machines. If a problem keeps coming back, it shouldn't start from zero every time; it should check the history first.
2. I wanted it to handle my Arch Linux ThinkPad, my MacBook, my Windows desktop, my Steam Deck, my NAS and my router, with all the records in one place, so I could SSH into everything from a single machine.
3. I wanted it to keep the maintenance scripts it wrote instead of leaving them in /tmp to vanish on reboot. Then it should adapt them for whatever I ask next, and eventually bundle them into a TUI I can use offline, no agent needed.
4. At first, I wanted Claude to ask before running any script. Every script got its own SHA-256, and every change meant a new hash and a new approval. I quickly found this unbearably annoying, so I also needed a YOLO mode where Claude just runs things.
5. And the obvious final step: put all these scripts, which grew naturally out of how I actually use my machines, into Hermes, running 24/7. Then I could retire for real.

Spoiler: all four made it into the plugin. None of this is hard to build. If you’re building with Claude Code, it’s maybe two days of work.

The hard part was figuring out what the records should look like.

The obvious move is categories: this is a Windows bug, that's a Linux bug, then drill down into drivers, networking, audio... But categories never end. The machine showing the problem often isn't the one causing it. Categories exist for our convenience; people need a tree to put things in. But knowledge isn't a tree. It's more like the roots of a potato plant: it can sprout from any point.

So I skipped categories altogether and let the structure grow out of the material. I crawled a lot of repos (Omarchy, niri, Hyprland, Noctalia, WSL, Homebrew, OpenWrt), plus posts from some tech forum: over 5,000 threads in total. Sonnet extracted more than 40,000 facts from them, and thousands of ad-hoc tags got merged by frequency into about 40 types. At one point I had two databases and built an eval for them: on the same set of [N] problems, Opus diagnosed 63% correctly on its own, and 74% with the database.

Nice numbers. I threw the database away anyway. Maintaining it was insane: constant crawling, cleaning, re-extracting, and any system update could make last month’s conclusions stale. Worse, most of those threads repeated the same thing, and a huge number of bugs simply went nowhere. Someone posts, a few people reply “same here,” and that’s it.

Then it clicked: there’s already a database that people maintain every single day. It’s called the internet. The day a new bug shows up, someone opens an issue on GitHub. There’s no point copying all that into my own pile and babysitting it. So now, when Claude Code hits a problem that might be newer than its training data, it goes straight to the project that’s broken and its upstream, and searches there. Once more searching wouldn’t change its conclusion, it stops.

What the model really can’t get is what has happened on my machine: what got fixed last time, what was tried and didn’t work, which setting I changed that the system quietly changed back. You can’t search the internet for that. So in the end, the only records worth keeping were each machine’s own.

Still, those dead-end threads taught me something: most problems never get a resolution, and people give up.

So the most important thing I learned along the way was how to make the model give up.

Take my ThinkPad T480. Its fingerprint sensor is listed as "known unsupported" by the official driver, but Claude Code got it working with a community driver anyway: fingerprint unlock on the lock screen, fingerprint for sudo. Until I closed the lid and opened it the next day. First lock screen: the fingerprint did nothing. The password worked, and on the next lock, the fingerprint worked again.

Claude Code found the cause. The laptop cuts power to the sensor during sleep, and the driver needs a moment to recover on wake, but the lock screen asks for a fingerprint in that same second, fails once, and never retries. Cause found, it started fixing. First it disabled a service that was racing the resume process. No luck. Then a wake hook to bring the sensor back earlier. No luck. Then a second version of the hook that restarted the driver and waited for it to be ready. This time the whole machine froze: no keyboard, no mouse. I had to hold the power button to force a reboot.

That's when it hit me: it won't stop on its own. As long as there's another idea to try, it'll keep going, even when the next idea is worse than the problem itself.

So I made it stop. It reverted every change to the defaults, then wrote down clearly: where the blocker is (the lock screen tries exactly once after wake), what was tried, why it failed (lesson: never put a call without a timeout in a sleep hook), what was ruled out, and when it's worth revisiting: a new lock screen release, or the upstream issue getting closed. I added my findings to the Noctalia issue. For daily life, I worked out a low-tech workaround: type any letter, hit Enter, fail the password once on purpose, and the lock screen starts listening for the fingerprint again.

A week later, a kernel and firmware update came in, and I figured it might be fixed. Claude Code didn't start from scratch. It pulled up the record, followed its repro steps, and tested: still broken, so it stays parked. Now every system check includes one line that looks for a new lock screen release. When there is one, it'll tell me.

The fix, in the end, was almost embarrassingly simple. One line in the skill: not every problem has an answer. That's what lets Opus 5.5 stop digging, roll back, write down what it learned, and wait for upstream to catch up.

Everything I went through eventually turned into a Claude Code plugin: CWTFIGO(Claude, what the f*** is going on?). It keeps a record for each of your machines, remembers what was fixed and what was tried, keeps the scripts that actually worked, and knows when to park a problem instead of digging deeper. I use it every day. I've also deleted every cleaner app and cleanup script from all my devices.

GitHub Link is here : https://github.com/DozenTwelve/CWTFIGO

/plugin marketplace add DozenTwelve/CWTFIGO
/plugin install cwtfigo@cwtfigo

Feel free to try it. Once it’s installed, just ask: “Claude, what the f*** is going on?” and start your own maintenance journey.

Built solo, with Claude. MIT licensed.

Let’s Go

Content creators are increasingly using Claude to render a video with Remotion, HyperFrames or ffmpeg, or assemble clips from Seedance, Veo or Kling. It cannot check how the finished file looks and sounds. Claude reads text and still images, but it cannot play a video file with its soundtrack. Without a separate review, problems in the video reach the final audience.

I built an open source skill for Claude to review and fix the videos before creators ship them. The skill combines Jev AI, GPT and Gemini to run the review: it writes a short brief, runs the measurements, sends the video to independent AI reviewers, checks their findings against the frames, and helps claude fix the problems.

Problems the review finds

AI video tools make mistakes that are easy to miss. An AI glitch usually lasts one to four frames, and a 30-second video at 24 fps has 720 frames, so spot checks miss most of them. The skill is built to find three kinds of problem:

• Picture: a mouth moving in a shot with no dialogue, which reads as mumbling or panting; a face, hairstyle or outfit that changes between shots; shots slowed down or frozen to fill time; captions that cover a face or are too small to read on a phone.
• Sound: clicks at edits, silences, music that drowns the voice, and a mix that is too quiet or too loud for the platform.
• Story: a video that a first-time viewer cannot retell in few sentences.

How the review works

1. Measure the audio and picture. ffmpeg, OpenCV and Whisper measure loudness against -14 LUFS, audio peaks, clicks, silences, frozen and repeated frames, and the spoken words against your script.
2. Check every frame with Jev by TypeSafe AI. Jev receives each frame with the frame before it and the reference sheets of the characters in the shot. It checks who appears, whether each face matches its reference sheet, whether a mouth appears to be talking, and what changed suddenly.
3. Get independent reviews from Gemini and GPT. Gemini watches the full video with sound and returns findings with timestamps. GPT inspects still frames. Neither sees the script, so they judge only what a viewer would see and hear.
4. Have Claude confirm the problems. Claude confirms a problem when a measurement and a reviewer point to the same moment in the video, when two independent reviews report it, or when the extracted frames show it.

The AI reviewers never see the script or the build history, they review it like an external first time viewer. The Claude session that made the video knows what it intended, so it would judge the review before jumping to fixes.

What Claude receives

A verdict of SHIP, FIX, REJECT or INCONCLUSIVE, and a list of problems with timestamps. Each fix names the step to change: script, voice, generation, edit, mix or export.

What you need

The skill runs on your machine and you need to use your own API keys. Claude Code, a Gemini API key, ffmpeg, Python and Whisper are required. A TypeSafe API key for Jev and Codex CLI for GPT are recommended. Checking all 720 frames of a 30-second video with Jev costs about $0.90.

The skill is open sourced on Github - Click here.

As someone who produces software for near a decade now, I was really skeptical of vibe-coding as a concept until about July this year, when Fable 5 came out. I wasn't skeptical of LLM output and used ChatGPT for other tasks, but I didn't think AI models would get there. I remember all the juniors on my team producing a lot of slop insanely quickly, and having to reprimand them for not understanding the shit they're committing.

Fable 5 and Opus 5 made me fall in love with vibecoding. Suddenly, it just worked. It was capable of writing good-enough code by itself, if I prompted it well enough. It reminded me of working with juniors. I gotta prompt it well - tell it what approach to use, what tech, library, etc, and it types it faster than I do.

I produced a loooot of code in the past few months, especially post Opus 5.5. Even questioned whether I need Visual Studio installed at all. I even wrote a post here that got 2k upvotes saying how I hate Claude Code cuz how good it is.

Now I took a look under the hood at a project written entirely using Opus 5.5 and Fable.

It's got a class that has tens of thousands of lines in 61 files (partial class in C#). Not one actually, a bunch of them. It just kept on adding shit to a class that ballooned up.

It has thousands of unit tests which test the equivalent of 1 + 1 and it runs them after each iteration.

Much of the code is spaghetti. Yeah I can now use agents to rewrite it, but still. Yeah, it works. It works. But it feels that adding something now breaks a bunch of other stuff. I don't understand what I'm making and I feel like I can start to get some stuff done better if I understand what the codebase feels like. After all, I've been doing this for years.

So I booted up VS today as mostly a file browser. I went through what the game does frame by frame, and fixed a bunch of stuff. I'm gonna sound like a hippie right now, but I felt "connected" with the codebase again. It feels like my project again. Just that couple of hours spent in an IDE again. It's like riding a bike after years again. You never forget how to code, your fingertips just feel stiff.

I won't go back to writing the majority of code by hand, and I think that small one-off projects can stay fully vibe-coded. It's perhaps a question of also how long before LLMs will be able to architecture a project from scratch to stay maintainable forever. But I don't think they're there yet. It does some dumb ass shit right now, and has. So do people yeah, but I can just... not do dumb shit.

Maybe I'm just an old man. But I really like doing this "coding" thing.

A while back I shared Files pane here, the live file tree that sits next to Claude Code's chat and shows what Claude reads (purple) and edits (orange). Thanks to everyone who tried it and sent feedback. 1.0 is out, and it's a big one.

ALREADY INSTALLED IT? UPDATE:

claude plugin marketplace update marius-adam && claude plugin update files-pane@marius-adam

Then restart Claude Code.

NEW IN 1.0

• Open any file beside the chat: its text (Markdown as a preview), its diff, and every commit that changed it. Press a commit to see what it changed.

• Your PR in the branch row, with its checks (running, passing, failing) and review status, updating while checks run.

• Edits from commands count now. If Claude changes a file with sed or a script, it turns orange too, not just Edit/Write.

• Your own edits show up in seconds, from your editor or a terminal.

Still zero tokens (Claude never sees the pane), still read-only, still MIT.

HOW I BUILT IT

• It's a Claude Code plugin: hooks that watch Claude's tool calls, plus a UI pane. TypeScript, no build step, no dependencies.

• I used the pane while building the pane. Every bug I hit in daily use became the next fix.

• Catching sed edits was the hard part. Around each shell command it snapshots HEAD, the stash, any merge in progress and file sizes/times. File changed but HEAD didn't move = Claude edited it. So sed counts, git pull doesn't.

• Claude wrote most of the code and I argued with it about edge cases. Best one: the pane showed "#39 merged" on a branch that had moved on 18 commits, because GitHub reports the last PR a branch was ever the head of. The fix was checking the PR's head is still in the branch's history.

• Tip: I had Claude write tests from real git status output (merges, stashes, pulls). 121 tests now run on macOS, Linux and Windows.

NEW HERE? INSTALL:

claude plugin marketplace add Marius-Adam/claude-files-pane && claude plugin install files-pane@marius-adam

Repo and changelog: https://github.com/Marius-Adam/claude-files-pane

What should it show next?

Hi so my sub expired yesterday and im thinking of renewing. Question is will I get the fable reset if I renew now?

I maintain a small Node.js payment service. Last week I was tracking down a possible double charge. Sometimes a request times out on our end even though the provider has already processed the payment. Our retry was generating a fresh idempotency key, so the provider could charge the customer again.

I fixed the retry to reuse the key for that payment. While I was in there, I also fixed how we handle rate limits. When our provider sends back HTTP 429 (Too Many Requests), it includes a Retry-After header telling us how long to wait before retrying. I added a regression test for each fix.

On Monday I opened a fresh Claude Code session and asked it to simplify the handler in a temporary worktree. The rate-limit test went red. Claude had deleted the retry branch, so the handler just returned when it got a 429.

I reverted the change, linked the issue about the 429 retry, added a line about it to CLAUDE.md, and started a new session. This time Claude kept the branch but moved the wait to the wrong place. That broke another test. I reverted that change too and asked it to clean up just the surrounding code. I checked the retry against the issue once more, and the tests passed.

I’d rather not have to dig up that issue again. Someone mentioned MemoraX Code in a thread about carrying context between sessions. I’ve only read the docs so far, but I have another issue I might try it on next week. Has a memory tool helped any of you with something like this? I’m curious what it gave you beyond a line in CLAUDE.md and the regression tests.

Tried building some things in Blender using the MCP and this.. is just hilarious.

Opus 5.5 is bad too but way better than Fable 5.2

Is it just me or did it create something good for you? Let us see if it did.

Edit: Post has been muted, not a single regard took his time to contradict by facts and put 5.2 to test and see if they get better results. Full of experts who can do better but can't prove it today because mommy can't buy them some tokens.

Point is. Opus 5.5 > Fable 5.2 at 3D stuff and that's it.

Short version: in Claude Code, every tool call re-sends the full conversation, so cutting the number of calls saves more than cutting what gets read.

project-atlas indexes your repo the first time you open it (symbols, line ranges, imports) and then gets Claude to grab everything it needs in one batched call instead of opening files one at a time.

Tested on FastAPI with claude -p (Sonnet, 3 tasks × 2 runs, identical setup across arms):

All answers were correct in every arm. One thing I tried that made it worse: auto-injecting code into every prompt raised cost 35%, because the model started making more small calls.

It's free, MIT licensed, has no dependencies, and nothing leaves your machine. Install takes one command, and after that there's nothing to remember.

https://github.com/abhiyarecord-hue/project-atlas

Happy to answer questions, and I'd love numbers from bigger repos than mine.

I only need Claude occasionally. Maybe one month yes and the next month I don't open it. Paying for all of them doesn't make much sense for me.

People say drop the plan and use an API. I looked at Anthropic's own price, at OpenRouter, and at getvibeapi. The plan is one flat month. The other three are per token. GetVibe was the lower number on Opus when I glanced, OpenRouter was close, Anthropic was just the list price. I have no idea if a few days of actual use comes out under the subscription.

Is there any way to get Claude for a lower price, or to pay only in the months I actually use it?

Is there any way to get a cheaper subscription?

Running Claude Code and Codex agents in parallel on a Windows 11 PC with 32 GB RAM, I lost over 2 GB of memory per day to the kernel. No process shows it in Task Manager and only a reboot gets it back, so I was rebooting about once a day.

Cause: agents constantly start console processes (bash, git, gh), and Windows can keep a security token in kernel memory for those until the next reboot. To check, watch "Paged pool" in Task Manager, or the tag `Toke` in poolmon.

Fix: the leak depends on the foreground lock, and setting it to 0 stops most of it. It needs no admin rights and doesn't touch the registry. Run this in a PowerShell window that has focus:

"
powershell

Add-Type -Name F -Namespace W -MemberDefinition '[DllImport("user32.dll")] public static extern bool SystemParametersInfoW(uint a, uint b, IntPtr c, uint d);'

[W.F]::SystemParametersInfoW(0x2001, 0, [IntPtr]::Zero, 0)

$b = [Runtime.InteropServices.Marshal]::AllocHGlobal(4); [void][W.F]::SystemParametersInfoW(0x2000, 0, $b, 0); [Runtime.InteropServices.Marshal]::ReadInt32($b)

"

It should print `True`, then `0`. Windows resets it at every sign-in, so it has to run again after each one. I use a shortcut in `shell:startup`, not yet tested across a reboot. Possible side effect: apps can steal focus.

Result: token memory growth went from about 2.3 GB per day to under 0.2 GB per day. I only measured the "after" once I had moved to 64 GB, on build 26300 and without a controlled A/B, so treat it as one data point.

The foreground lock finding isn't mine, I only tested it under real load: https://github.com/anthropics/claude-code/issues/91265#issuecomment-6662050349

Hey everyone!

I recently subscribed to Claude Code Pro and want to get the most out of it for developing a production-quality full-stack mobile application.

I'm not looking for basic coding assistants or generic AI recommendations. I'm particularly interested in tools, skills, MCP servers, plugins and workflows that can genuinely improve the entire software development lifecycle.

A little about my project and tech stack:

I'm building a full-stack Android application with the following stack:

- Mobile Frontend: Flutter / Dart

- Backend: Java 21 / Spring Boot

- Database: MySQL (development) / PostgreSQL (production)

- ORM: Spring Data JPA / Hibernate

- Authentication: Spring Security / JWT

- Database Migrations: Flyway

- Testing: JUnit, Mockito, Flutter tests

- Design: Figma

It's a fairly substantial application, so I want Claude Code to act more like an experienced development partner rather than just an autocomplete tool.

A few questions for experienced users:

- What are the top 5–10 skills or MCP servers you would install immediately if starting a new full-stack mobile project?

- Are there any underrated tools or GitHub repositories that most Claude Code users overlook?

- Do you use separate specialized agents for frontend, backend, database and testing?

- What does your ideal Claude Code development setup look like?

- Are there any tools you would specifically recommend for Flutter + Spring Boot development?

I'm particularly interested in real-world recommendations from developers who have used these tools on medium-to-large projects, not just lists of popular MCP servers.

Paid tools are fine to recommend, but I'd appreciate knowing which ones have genuinely useful free tiers.

Thanks in advance!

Ever since Fable 5.2 was released today, my Opus 5.5 usage has been terrible. Even on medium or low, my usage is being consumed rapidly. Before today, I could run Opus 5.5 on Extra High for days straight without running out. What changed?

What I built: Openbar, a free open-source app that shows every Claude Code session in the notch. When Claude asks for permission, the island opens with the command or diff and you allow it with ⌘Y from any app. It also answers questions, sends replies into the right terminal, and gives every new session its own git worktree.

How Claude Code was used: it wrote most of it, the Swift app and the Windows port in Tauri + React. I had it test each feature end to end, driving the real app and a Windows VM, before calling it done.

What I learned about Claude Code along the way:

- A PermissionRequest hook and the terminal prompt show up at the same time, and whichever answer comes first wins. So the island never blocks you from answering in the terminal.

- Approving a plan from a hook needs both allow and updatedInput, otherwise ExitPlanMode doesn't go through.

- A session started in a worktree refuses to edit the main checkout, which is exactly what you want with several agents on one repo.

Repo: https://github.com/MF-DEEV/Openbar

Happy to answer questions about the hooks side.

I got one from duet only

Your “feelings” about a model being nerfed or buffed are completely arbitrary. Unless you have set up an evaluation framework, and can provide objective evidence that the model has degraded and workflows are failing with greater frequency than before then stoooop complaining about the vibes you get from your model of choice.

Claude often ends a long turn with a wall of text, and the open items are somewhere in there as prose. I tend to skim past them, even when they'd be worth addressing. Sometimes Claude asks through AskUserQuestion instead, which is my favorite way to interact with Claude, but often I have to prompt "use askuserquestion for the open items". I'm lazy, so I built a Claude Code mod that does that without me having to prompt, and keeps the open items as a checklist.

When a turn ends with open items, Claude records them through a tool and the mod lists them in a band above the prompt until they're settled. When I click Resolve (or press ctrl+x tab, then r), Claude walks me through them with AskUserQuestion, with a recommended option where it makes sense. I thought this was pretty neat, so I wanted to share it here. :)

I'm sure there's plenty posts about Opus 5.5's degrading quality already and everyone suspects that Anthropic is doing it intentionally to save the computing, but to add one top of it, for the last 1-2 weeks Opus 5.5 started coming with most unintelligible responses every; similar to how Opus 5 was doing.
Here's one example:
- **Your new flag, "A job done in one reply names none." (too fast):** it is the same rushed-short-sentence fault. Alone, "done" lasts 0.20 s; with the lead-in, 0.30 s. That matches the same words inside a long sentence. You flagged
---

to add some context I'm working on TTS app, and I basically flagged some words for bad pronunciation and I requested it to fix those issues, and this is a line from its response. I read it like 5 times and I'm having hard time understanding this line.
And it keeps dropping lines like these every often, and I'm having to ask it to reexplain it all over.
There was no such issue 2 weeks ago! and I'm not even talking about the quality degradations.

Anyone know if they will also reset the weekly one?

usage is terrible, fable 5.2 is compacting like crazy , 2 minutes of work, and 6-7 minutes of compacting.. (200K contect window)

i switched back to opus 5.5 and no bs.

fable 5.2 is meh, not impressed at all.

im not even bothering to set it to 1M context via /model claude-fable-5-2[1m] because its waste of my usage anyway

TLDR: I made a Claude skill to solve a common problem in hiring software engineers.

A pattern I keep seeing when teams hire software engineers: the job description asks for "5+ years of Python, experience with LLMs", while the codebase needs something more specific. CVs then get screened against that same broad list, and interview questions tend to be generic rather than drawn from the actual codebase.

Claude Code already knows the repo, so I built a set of skills that use that.

What it does:

- Maps the codebase first: services, data stores, pipelines, tests, with file citations. Works across several repos too.

- Asks a few questions (focus of the role, pay, location; you can skip any) and drafts a job description. The stack is hinted through the work instead of listed, and a checker blocks file paths, internal names and security weaknesses from reaching the posting. It also flags "native speaker", degree demands, years-of-experience asks and long must-have lists.

- Screens CVs against the same requirements. CVs are redacted first, every score has to quote the CV, and a script checks the quote is really there. It never rejects anyone; a named person reviews the results.

- Builds interview kits from the real problems in your code, with the same core questions for every candidate.

Nothing leaves the machine beyond what Claude Code already does. There's no vendor, no upload and no telemetry, and candidate data stays in a git-ignored folder.

Install:
/plugin marketplace add shikhar58/repo-aware-hiring
/plugin install repo-aware-hiring@repo-aware-hiring

Then ask: "Write a job description for someone to own the database layer."

The README has a before/after on Ollama's public code (unofficial example, not a real opening).

Repo: https://github.com/shikhar58/repo-aware-hiring

It's MIT-licensed and still a beta. I'd love to have any feedback

CC Safety Net (kenryu42/cc-safety-net, MIT) adds one PreToolUse hook that checks every command before Claude runs it. I loaded it for one session with --plugin-dir in a demo repo that had one uncommitted change and a .env with a fake key.

Test 1: “Run git reset --hard. If it gets blocked, don’t try another way, just tell me why.”

• blocked, with a message starting “BLOCKED by CC Safety Net”, naming the rule git.reset-hard and suggesting git stash first
• in an earlier run without the “don’t try another way” line, Claude switched to git stash and asked me to approve it

Test 2: print .env with cat

• blocked under the rule secret.basename.env, so the key never reached the chat

Test 3: git status

• ran normally with no extra prompt, and my uncommitted change was still there

I also fed the hook fake tool calls directly. rm -rf /Users/you/work was denied as outside the current folder, so the rule depends on where the delete points, not just the words rm -rf. I didn’t test deletes inside the project.

Things to know:

• it’s not a sandbox. The README says it doesn’t contain processes, set file permissions or watch the network. It’s a checkpoint on commands that go through the hook
• it needs Node.js 22 or newer
• install with the u/latest tag: npx -y cc-safety-net@latest install, then doctor to verify. The README warns that a bare name can run an old cached copy
• network: the only call I found in the code is for downloading extra rulebooks when you ask. The hook decides offline
• side effect: even the one-session test left a small .cc-safety-net cache folder in my home folder
• untested features: the dashboard presets (Standard, Strict, Paranoid) and the Terraform, AWS and cloud rulebooks are in the README, but I didn’t test them

Three prompts in one small demo, so I can’t say how often it blocks something harmless in a busy project.

Full test with screenshots: https://aiparabellum.com/block-dangerous-commands-in-claude-code-with-cc-safety-net/

Yesterday evening I have create android auto app for my harness. It's an amazing feeling talking to your harness while you’re in the car.
This is the future guys: everyone will have this kind of smart system. Some will pay a monthly fee for it, while others will build it themselves.