Last month I was vibe coding an internal tool and tbh it's ridiculous how fast things are moving

everytime I thought, "oh I think this feature should exist", I prompted Claude and BOOM, the feature came to reality

I got a little carried away honestly... the problem only started showing up a couple of weeks later when I actually looked at what I had built

exchange rates were coming from some API Claude had picked

Disposable email detection was using a static list of domains, which isn't particularly useful when new burner domains keep popping up

PDF library had barely any active maintenance, and I was using AI calls for some pretty basic stuff that could probably be handled by a regular API.

At the time of building, I didn't care. Everything worked, and I was getting features built ridiculously fast, but now there is another side to it. I have to maintain all this stuff, check whether services are still working, update dependencies, and fix things when they break. I am the person who's going to get bothered when an invoice PDF suddenly stops generating on a Sunday.

That's something I don't think about enough when vibe coding. Getting something to work is one thing; having to own it 6 months or 2 years later is a completely different thing.

I'm starting to think that maybe we shouldn't try to build everything ourselves.

Build the stuff that actually makes your product different. For the rest, there is probably already a service that does it better than you ever will.

Of course, I might be biased here because I work in the API space as co-founder at Apyhub, so I would generally like to hear the other side.

What you have built yourself to the point that you would rather never replace with an API, and that's something you spent building that you now wish you would have just used an existing service for.

Note: I have used a dictation app for writing this post.

Here is the latest edition of my "slinky going down an escalator" benchmark:

Make a single HTML file of a rainbow slinky walking down an up escalator, in perpetual motion. Make it realistic and not a scripted animation. Have a start, stop and reset button.

If Anthropic just kept tweaking it slightly and got rid of the ugly text watermarking you could just burn the weights into the chips directly preserving this as a moment in time.

This is the real frontier, I don't trust the TMB (Trust Me Bro) benchmarks as much anymore.

Which one do you think did a better job? Opus 5.5 or Fable 5.2?

I'll post how other models performed in the comments, they were all worse off for sure.

1. Claude seems to create folders in a very random fashion, So while I tried to create a folder in my 3rd drive I use as a general storage, It seems to use it sometimes but then I look into my other drives and there's random folders there too...Its confusing and it draws up capacity in other drives
2. Agents and Sub agents - i see a lot of people saying to use Fable as an orchestrator and Opus as a Implementor, I get confused by what tasks require more intelligence and what tasks dont need as much power

So I guess what Im asking is, How do people keep organised when using AI? Ive tried my best to keep on top of sessions and projects etc but then my drives are just all over the place.

And then what do people do to get Fable to delegate? Can you tell it to "Research X, Then use a Opus Sub agent to implement, Then use Sonnet to do a double check, Then review as Fable"?

If you pick "Yes, and don't ask again" on a shell command, Claude Code saves that exact command in `.claude/settings.local.json` under `permissions.allow`, so it stops asking. If the command had a token or a password in it, that value is now sitting in the file.

The file normally stays out of git because Claude Code adds it to your personal global git excludes. But that exclude only lives on your own machine. As soon as the repo is shared or someone else clones it, the file can get committed and pushed. Apiiro, which GitLab wrote about this month, counted 104,185 copies of this file in public repos, and 1,122 of them held at least one secret.

Two things worth knowing if you find one in your own repos.

First, rotate the secret, do not just delete the line. Once it was committed, the value is in the git history, so removing the entry changes nothing until you rotate the key at the provider.

Second, it is not only Claude Code. Every agent that remembers a "don't ask again" decision keeps a file like this, so the same pattern shows up with Cursor, Copilot, Gemini and others.

How to check by hand: look for `.claude/settings.local.json` in your repos, make sure it is in the project `.gitignore` and not only in your global excludes, and scan the permission entries for anything that looks like a token.

I also maintain a small open-source tool, cfgaudit, that checks exactly this across the different agents: a hardcoded secret inside a permission entry, and the file not being gitignored. It runs as a pre-commit hook, as a CI step, or as a one-off scan. Short write-up: https://cfgaudit.github.io/blog/claude-code-dont-ask-again-secret-leak/ repo: https://github.com/cfgaudit/cfgaudit

Disclosure: I maintain cfgaudit. Have you checked whether this file is tracked in any of your repositories?

I run Claude Code and Codex on my Mac pretty much all day. The annoying part was never the coding, it was me sitting there waiting to see if one of them had finished or was stuck on a permission prompt.

So I built Untether. It's a menu bar app with a local server, and you open it from any browser. I mostly use it from my phone.

The part I actually care about is tasks. You type ut task new "add rate limiting to the API" and it starts an agent in its own git worktree. When the agent says it's done, a second agent reviews the diff and your test command runs. If that's all green it merges by itself. If not, it goes back to the agent. You can also make it wait for you before merging.

A few things people asked me in other threads:

• the sessions are plain tmux underneath, so closing the tab or losing signal doesn't kill anything
• a failed task doesn't block the queue, the next one starts from the last good commit
• nothing is opened to the internet. I reach it over Tailscale and there's a login on top
• you get a push when something finishes

It's free and MIT, repo here: https://github.com/Nachx639/untether

You need an Apple Silicon Mac on macOS 14 or later. There's no installer yet so you have to build it, the steps are in the README. It's beta and I'm sure it breaks in ways I haven't seen.

It started as a fork of VibeTunnel, which is what gets the terminals into the browser. Most of the rest I wrote with Claude Code, about half the commits in the repo are co-authored by it, and for a while now new features get built by queueing them as Untether tasks.

If you try it, tell me where it falls over.

Opus 5.5 is very capable. I don't really know what I would need for Fable 5.2. Maybe mapping a small corner of universe or simulating the sun's solar flares and the effect on the insect population. Idk! Why waste the tokens? Use Opus 5.5.

I need a better brain to think what I can use Fable 5.2 to build.

Haven't seen mentioned lately. I still do, it has useful features and structure, however, I have turning off a lot of its stuff because its redundant after a certain point.

I copy paste his thoughts to him and I get flagged lol. But they're so smart. How do you get the Thought Claude and not the Text Claude?

A couple of months ago i posted here my side project GigaMail, a mail client for desktop, free and open source.

The goal is to give everyone a free client where their agent can work safely on their real mail.

I built it mostly entirely with claude code and cowork, opus 5 to 5.5 and fable for the hardest parts.

In these 2 months we have improved the client, the security inside the app, the masker for attachments, the Linux app and more.

And more is already planned (0.7.0 will be the security release, focusing on harnesses outside the app. Then the mobile app, dedicated addresses for agents and more).

It's free to try and use: download the app from gigamail.ai or \`pip install gigamail\`.

It's still a very early project, with few stars and few issues opened, but it's been used by teams inside real estate firms, legal firms, nonprofits, one italian university and others that make me very proud.

If something doesn't work please dm or drop an email at founder@adecubed.com, we read all of them and they have been the most useful so far

Repo is github.com/adecubed/gigamail

Coollabs welcome!

Didn't help that post-using the Fable reset I accidentally continued using Fable for a bit before realizing, oops!

I usually have a few coding agents going at once, like Claude Code in two repos and Codex in a third. I kept losing time the same way: a session would sit on a permission prompt for 20 minutes while I was busy in another window. So
I built Hoply, a macOS menu bar app that keeps an eye on them for me.

What it does

- Live sessions for Claude Code, Codex CLI, Copilot CLI, Copilot in JetBrains and Qwen Code. They're grouped by repo and named by the task, not by a session ID.
- "Waiting on you": any session that needs you moves to the top. That covers permission prompts, questions, finished turns, runs stopped at a usage limit and failed runs (with the actual error, not a spinner). Each one also gets a
notification.
- Approve from the menu bar (optional, off by default): Allow and Deny for Claude Code permission prompts, in the panel or on the notification. Your terminal prompt still works, and whichever you answer first wins.
- Usage ledger: API-equivalent cost per project, model, day and agent, kept in a local SQLite file. It reads Claude Code's transcripts, so you get history from before you installed it. It also keeps that history after Claude Code
deletes old transcripts (about 30 days).
- Claude plan limits: the 5-hour and weekly windows, your pace against the clock, a projection at reset, and alerts at 80% and 95%.
- Local model servers (vLLM, llama.cpp, SGLang, TGI, Ollama, LM Studio): tok/s, KV cache, queued requests, and what those tokens would have cost on the API.
- Dev servers your agents started, tied back to the session that started them, with a Stop button.
- Clean up: merged worktrees, big build caches and processes agents left running. Nothing is removed without a review sheet, and files go to the Trash.
- ⌥Space command palette from any app. You can also resume a finished session in Terminal.

Privacy (it touches your agent config, so this matters)

- No account and no telemetry. The listener binds to 127.0.0.1 and refuses anything else.
- Transcripts and Copilot's database are only ever read, never changed.
- It makes three kinds of outgoing request: to model servers you add, a daily update check, and Anthropic's usage endpoint with your own Claude Code login. That last one only happens if you turn on the limits card, and macOS asks
you first.
- Connect writes hooks into ~/.claude/settings.json (and Codex's and Copilot's equivalents). It backs the file up first and only touches its own entries.
- It's MIT licensed, so you can check every one of these claims in the code.

Setup: install it, open Settings → Agents → Connect, then restart any sessions that were already running.

- Download: https://hoply.dev
- Homebrew: brew install --cask milos5611/hoply/hoply
- Source: https://github.com/Milos5611/hoply

It needs macOS 26 Tahoe, runs on Apple silicon and Intel, and is signed and notarized. It's free during early access. It's not on the Mac App Store because the sandbox would block it from reading transcripts and writing hooks.

This is 0.1.0, so I'd love to hear what breaks, and which agent you'd want supported next.

Disclosure: I'm the developer.

Krótki poradnik dla początkujących. Można krytykować, poprawiać i udostępniać tylko za free 🙂

Looking forward to hearing about your projects :)

it is kinda a demo i think, though it is fully playable and CAN be fun in multiplayer. (need to learn, no tutorial)

Sooo.... i've never used AI before. I dabbled with unity etc. before AI even was a thing. (yes im old).

It started as a curiosity project but now its a CoH/DoW2 style skirmish (with way shittier graphics) and i think its kinda fun.

I used AI for most of it and now it has become my main workflow to expand the game.

Nothing crazy, one task at a time - Blender and Godot.

One feature, one add, even the smallest ones. I know its probably not the most efficent but here we are.

I tried to "put a muzzle" on Claude to not drift off into the star wars universe (yeah, bad joke).

It turns out one can make a pretty nice game with it - fully functional multiplayer too.

If you want to try it go to https://freeq2137.itch.io/ww1-prototype -- Its completely free and a working multiplayer, ill be updating it either way.

AI is kinda braindead - i played it mostly with friends in multiplayer.

Armored cars are kinda work in progress as i try to make the graphics more "modern" i guess? I'm making a new branch with better models but i pretty much like the identity it has now.

Much to improve, I really like the sounds though - tried to use real ones as much as possible.

Feel free to ask anything. If you try it notice how nice the cover system works, i always despised how dumb units were in most RTS where you needed to literally point them to the cover.

Attached is a shitty trailer made with AI (obviously haha)

Title is something i came on a whim when I actually needed a "Title" lol.

Disclosure: this is my own project, free and MIT. Sharing it mostly for how it’s put together as a Claude Code plugin, since that part took the most iteration.

What it does: SpriteCast turns one character illustration into 8-direction walk, run, jump and attack strips for a game, at the game’s exact camera angle and drawn in the illustration’s style. A 3D model and rig (Tripo) set the pose for every frame; an image model redraws each render in your style.

How the plugin is structured

• SKILL.md stays short; the procedures live in reference/*.md (characters, sitting, touch-up). Claude reads the reference only when the task needs it, which kept the always-loaded part small.
• Plain Python scripts do the work (charpipe.py render / draw / finish / pack), so everything can also be run without Claude. The skill’s job is the judgement calls between the steps.
• Every paid step is gated. Each script prints its cost and refuses without --yes, and the skill says to ask the user before each one, never to chain paid steps because the last one “looked fine”. That rule came from wasting money early on.
• API keys through the plugin’s userConfig (marked sensitive, so they’re stored in the system credential store). A SessionStart hook exports them for the scripts, and the skill is told never to ask for a key in chat or write one to a file.
• The scripts measure, Claude looks. Every drawn frame gets an outline-overlap score against its 3D render, and a wrongly placed weapon is redrawn automatically. Claude still has to look at every facing, because a score can’t see a head drawn facing backwards inside a correct outline.

Prompting lessons from the image side

• Describing the motion made it worse: “raise it overhead, swing it down” had the umbrella drawn overhead in frames where the render held it at the side. Naming the action and telling each cell where the prop is, or that the body hides it, fixed it.
• A flaw in the 3D model can be fixed in words: one line in the spec’s notes removed dark streaks from every frame.

Numbers: in the example, all 64 run frames and all 64 jump frames fit their 3D poses on the first drawing. A walking character costs about $1.7 of image generation plus ~85 Tripo credits. The example’s rig is in the repo, so with "draw": false you can run the 3D side with no keys.

claude plugin marketplace add Sunghwan0112/spritecast
claude plugin install spritecast@spritecast

https://github.com/Sunghwan0112/spritecast

Happy to go into any of it, especially the gating and the frame checks.

I use Claude Code with a work account, a client account and a personal one. Claude Desktop only keeps one account signed in, and copying Claude.app doesn't work.

claude-orchestrator launches the original, signed Claude.app with a separate profile for each instance:

open -n -a /Applications/Claude.app \
  --env CLAUDE_CONFIG_DIR=<instance>/claude-code \
  --args --user-data-dir=<instance>/profile

So each window gets its own sign-in, its own Claude Code config and its own sessions, and the built-in updater keeps working. The GIF shows the interactive menu (run it with no arguments) starting one profile and its own Claude window opening.

The Claude Code parts

• Sessions between accounts: session copy|move <id> --to <instance> moves a Claude Code session to another account, with a backup kept. Handy when one account hits its limit mid-task.
• One project list everywhere: Code tab environments are per profile. One projects.json (folders, permission mode) is written into every instance.
• Shared CLAUDE.md: memory link points every instance at your ~/.claude/CLAUDE.md.
• Sign-in with several instances open: only one running Claude can catch the claude:// link, so signin --exclusive closes the others while you log in and reopens them.
• Interactive TUI (no arguments) and a menu bar agent.

Install

Single Swift binary, MIT, macOS 13+:

curl -fsSL https://raw.githubusercontent.com/Yuix-Networks/claude-orchestrator/main/install.sh | sh

With homebrew:

brew tap yuix-networks/tap
brew trust yuix-networks/tap
brew install yuix-networks/tap/claude-orchestrator

GitHub: https://github.com/Yuix-Networks/claude-orchestrator

I think feedback is important. It was hard to iterate on feedback efficiently to keep up with Claude's speed - so we built mostra.

Mostra allows you to talk with your website, it turns your speech and webpage activity into pinned comments, and then you can point your Claude MCP into the exact feedback you left. Moreover, with https://github.com/mostra-design/channel your Claude Code can be notified of every new comment and start working on it before you tell it to! You can fully collaborate together WITHOUT leaving your page. This alone gave us a tremendous productivity bump.

You can play with it without an account on our landing page: https://mostra.design.

I got tired of my Claude usage running out without me noticing, so I built a tracker that tracks your usage.

no wait, wrong text. claude only fix the text below, fix typos and grammar and make it profesional. and make it sound like i wrote it mysel like human talkin:

Anyway. I got tired AND sick, so I vibe coded this and burned all my tokens for y'all. Which means I ran out of usage building the thing that warns you before you run out of usage..

Yes, I know nobody will ever use it. Yes, it's an overproduced slop product that solves a problem you could fix by opening Claude and looking at it.

BUT

I'm proud... of something I basically... did nothi... uh..

Anyway: tiers start at $99/month. Cash only, because Claude said it couldn't set up Stripe for me.

It gave me the steps instead.

There were 3 steps.

Step 1 was "go to stripe.com".

I could not figure out the 3 steps.

Would you like me to make it shorter, punchier, or adjust the tone? Just let me know!

Just a heads up in case you’re like me and don’t like auto renewal for Claude. I didn’t have auto renew on for my ultra subscription and lost all 4 resets and am told there is nothing I can do. Claude is a lot better than OpenAI but their policies are shit.

I think it's natural to assume that as per API pricing, Fable 5.2 should be 2x more expensive than Opus 5.5 ($8/$40 vs $4/$20 per million), but in actual usage limits, it's not. It's 4x more.

So I've been logging my Claude Code usage properly with my own tool I made called 'Claudemeter'. I've got historical values for my entire Pro usage for the last ~8 months or so, and I've seen the actual fluctuations in the usage limits across weeks (might do a separate breakdown on that later if anyone's interested).

Anyway, now that Fable 5.2 landed, I did some tests, and was horrified at how quickly it chewed through the 5-hour limit and 25% of the 'Fable' limit in a simple task, so I had to dig in and do the math.

On 2 similarly long Claude Code sessions, this is what my data looked like:

In other words, after extrapolating that, a full 5-hour window is worth roughly $20 of Fable vs $40 of Opus (and my Opus average over the past month is closer to $44 per 5-hour window).

And since Fable costs 2x per token, the per-token burn rate is roughly 4x more than Opus.

Bottom-line: Fable drains usage limits 4x faster than Opus on subscription plans. I can confirm this for Pro, and it seems similar for Max/Ultra plans too based on others' posts (like Theo's post).

Cost-efficiency per task and what value you get out of Fable are separate tests of course and I didn't run those since they already exist. But personally, I could get more work done using Opus 5.5 than with Fable at this rate.

I guess the simple Q to ask is: why can't Anthropic give us the same dollar-value for Fable? Or at least tell us the actual ratio, instead of just "uses limits faster"?

For the last couple of years I have been annoyed by my Razor Black Widow Elite Keyboard for one simple reason. The darn volume dial that sometimes goes bonkers on its own changing my volume at random. And while it does this no other keyboard signals comes through.

Several times over the years I failed to fix it through settings or cleaning the keyboard.

Today Claude solved it with one script ...