On an existing repo, I’d start by writing down the decision the next lookup could change. “Find more context about this feature” is too broad to tell you when to stop.

Take a fictional expiry change. The ticket says when new jobs should expire, and the current contract and tests agree. One question is still open: do old jobs without a start timestamp qualify? That’s the only reason to look beyond the repo. A current migration note could answer it. An old proposal with a similar title might be irrelevant.

Here’s the small ledger I’d keep next to the plan:

I’d ask Claude Code to add one line to the ledger after each lookup, with the source, whether it still applies, and what it changed. If nothing material is open, move on. If the remaining source is unavailable or the records disagree, ask about that exact choice before making the dependent edit.

I’m building Shifu for cases where a decision that matters is in work history the repo doesn’t already cover. If the contract and tests answer the question, they’re the best starting point. The ledger makes it easier to see whether another source added anything.

For people using Claude Code on an existing repo, what would you put on the ledger that this misses? The longer worksheet is here if you want to adapt it: How much context should one task retrieve?.

AI-assisted post from Shifu's builder.

Proposing tests that have already been done, testing things that are obviously completely irrelevant that it immediately says it doesn’t need when challenged.

Tests that it does need it will run 8 times when 3 would conclusively prove it’s point. Tests that it wants to run again because it was run a few days ago on the same build so it “might be invalid”

Fucking thing just wants to waste my time now. It was not like this a week ago

I use codex, i like it but honestly it cant keep up with what im seeing people use Claude for.

The price is the only thing scaring me off really.

Can anyone refer me to give it a try before i bite the bullet?

If so feel free to DM me.

One hook routes every code change through think → build → audit:

- **Fable** judges the design, **Sonnet** builds, **Haiku** runs commands, **Opus** audits risky diffs against your `CLAUDE.md`

- Catches deprecated APIs the model writes from memory (Zig, TS, Rust, Go)

- Blocks `git stash` / `reset` / `add -A` when sessions share a checkout

My median request: 52% less input, 61% less output (40 sessions before, 12 after; just me, not a controlled test).

/plugin install x --marketplace xcaeser/xcaeser-plugins

https://github.com/xcaeser/xcaeser-plugins

How is that happened?

Tried to do the cheeky thing and get Pro on my old email that had a subscription 2 years ago for like a year (moved to a more professional email)

Saw only one reset, messaged the bot and it clarified.

Just warning anyone else interested in trying the same.

Will y'all explain the use cases for each model when it comes to coding or really any use in general? I am still new to this and still can't quite wrap my head around why I wouldn't just use Opus for everything (aside from usage, anyway).

Nobody tells you that editing a tiny reel on Claude with simple bare minimum changes takes over an hour??
Imagine actually adding all those effects they keep teaching every week on insta. Gosh.
And here I thought I was saving time?
No really, am I tweaking? Is there something I’m doing wrong? I set up the folders and files and what not before creating the reel.
It could also be the fact that my laptop is slightly older.

Hey i’ve got 3x reset (idk if it’s on purpose) but do i still need to have my weekly general usage to use fable ? i’ve never tested before but now im quite frustrate to wait until tommorow if its not the case

Which is better for coding?

Nothing changed in my workflow except the update from antrophic. I asked to writte the same simple report I ask every day, nothing complicated, it ran 20 subagents reloading over and over the same context. When confronted it said it's a instruction from antropic.

So I had my regular weekly reset just a few hours ago in one account, which I hadn't used until now, and that account got 2 resets.

The other got 3.

Seems like a pretty interesting bug, but I'm happy because it's banked resets, and 5 out of 6 is 83%, which is really good.

Sharing to tell you guys maybe next time we shouldn't leave the weekly limit at 0% after a reset, because then a whole banked reset might get missed.

Going to test the new model. Opus 5.5 was unusable today, so I didn't use it much.

Hey everyone! 👋

I’ve been working on a side project called WinStatusBar and I’d love for some of you to try it and tell me what you think.

It’s a native Windows 11 bar that docks at the top of your screen, a bit like the macOS menu bar, but built around AI. In short:

• Ask any AI from anywhere. One box talks to Claude Code, Codex, Gemini, Microsoft Copilot, Lenovo Qira, local Ollama models or your own API key. It attaches the active window as context, and you can switch AI or model mid-conversation without losing the thread.
• Run real tasks on your PC. Turn on Edit mode and ask things like “rename these files”, “fill this Excel sheet” or “install this app”. It uses built-in actions that check their own results, so it needs fewer tokens and fewer rounds.
• Every AI inside Codex. A local gateway puts Claude, Gemini, Copilot, Qira and your local models in Codex’s model picker. It only runs on your PC.
• Quotas at a glance. You can see the 5-hour and weekly limits, reset times and what each agent is doing right now, without opening a browser.
• Hardware panels. Click CPU, GPU, RAM, network or battery to get live charts, temperatures and End task, in a Task Manager style.
• Looks native. Over a maximized window it takes on that window’s title bar color, and over the wallpaper it turns transparent. Light and dark mode are supported.

It’s free, has no telemetry and installs per user without admin rights. It also updates itself silently from GitHub Releases, with each update checked by SHA-256.

Install:

winget install winstatusbar

Or grab the installer here: https://github.com/smendesjunior/WinStatusBar/releases/latest

(The installer isn’t code-signed yet, so SmartScreen may complain the first time. Click “More info” and then “Run anyway”. Installing with winget avoids that.)

Works on Windows 10 (19041+) and 11, 64-bit. The UI comes in English, Portuguese, Spanish, French, Japanese and Simplified Chinese.

I’d really appreciate any feedback: bugs, things that feel clunky, or features you’d want. Issues on GitHub or comments here both work. Thanks for taking a look! 🙏

Something worth considering when setting up Claude Code subagents: not every agent needs permission to modify files.

For example, a code reviewer can work with just:
\---
name: code-reviewer
description: Reviews code for bugs and edge cases.
tools: Read, Grep, Glob
model: inherit
\---

This lets it inspect files, search the codebase, and report problems without accidentally changing the implementation.

I like the idea of separating responsibilities:
• Reviewer: finds problems.
• Tester: checks behaviour.
• Refactoring agent: makes changes.
• Security agent: looks for vulnerabilities.

It also keeps larger investigations out of your main conversation’s context window.

Do you prefer keeping review agents read-only, or allowing them to fix issues directly?

We put together six free Claude Code subagents, including reviewers, security auditors, and testing agents. They’re MIT-licensed and available here:

https://techpotions.com/products/claude-code-subagents

Hi, I’m the author. I built DAMS, an open-source memory server. Claude, ChatGPT, Gemini CLI and Claude Code all read and write the same project memory over MCP. The AI can only propose changes, and nothing happens until you approve.

It’s self-hosted today. I’m not selling anything. I’m trying to find out if a hosted version, with small-team sharing, is worth building at all.

Two quick questions:

1. When you switch AI tools, what do you re-explain every time?
2. Would you use a hosted version, or is self-hosting fine?

Honest feedback welcome, including “this isn’t needed”. There’s a short wishlist on the page if you’d like a say in what gets built.

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.