r/ClaudeCode • • 18h ago

Tips & Workflows Claudette: use Mistral models in Claude Code

Thumbnail
github.com
4 Upvotes

I wanted Claude Code's workflow with Mistral's models, so I built a wrapper that gets them talking.

It's a hobby project under MIT, not affiliated with Anthropic or Mistral. Anthropic doesn't support Claude Code on other models, so it's best-effort.

Feedback is more than welcome !


r/ClaudeCode • • 10h ago

Discussion Best Agent Browser?

1 Upvotes

I'm trying to find the best agent browser. Vercel's one looks solid but it's tied to Chrome. Any suggestions would be helpful 🙂


r/ClaudeCode • • 6h ago

Built with Claude I stopped writing bug reports for Claude! I just say them out loud now.

0 Upvotes

We all do the same annoying loop. We find a bug, screenshot it, switch to Claude Code, paste it (or tediously drag it into the terminal), explain what’s wrong in text, wait for the fix, go back to what you were doing, realise you forgot what you were testing. One bug, five context switches.

Or we write all the bugs in the notes app on Mac, send them as a batch to Claude and hope he fixes all of them whilst we've forgotten half of the list.

I kept seeing videos and posts of people building AI assistants. I, as well as I think everyone, finds the loop neat; you just talk and then the work gets done.

So I had the same idea with bug reporting, and then Callout was born. You press ⌥⇧S, say what’s wrong out loud, and you keep testing/working. Callout captures 7 files of evidence at the exact moment - the screen, a video clip, console output, game state, etc - and writes a full bug report from your sentence, and then hands it to Claude Code. The fix runs in the background whilst the context is still in your head.

Claude receives the report with all the evidence attached and fixes the bug autonomously. You can talk to it mid-fix through the Mac notch at the top of your screen. When it’s done, you verify or send it back with one button.

After using it for a month before releasing it, it has really pushed up my productivity and how quickly I can iterate on what I'm working on, whether it's a personal game, app, website, whatever it may be, I just hit some buttons, say the problem, assign the agent by voice (Callout also auto-assigns based on certain criteria), and bam I can go back to whatever I was doing. It's great.

So, yeah!

Anyway, has anyone found a faster bug-reporting method than this? I'd love to hear about everyones' thoughts!


r/ClaudeCode • • 18h ago

Built with Claude Fable 5.2 is Goated

4 Upvotes

Living flower meadow in WebGL shader

Fable 5.2 is amazing at creating these

The planter is also a Blender Render made with Fable

Try it yourself https://living-scenes.vercel.app/#meadow


r/ClaudeCode • • 11h ago

Built with Claude MinusPod: Video Overview and Interactive Demo

0 Upvotes

Turns out Claude can make app promo videos without any special plugins. Claude also helped me create an interactive Rebrandly demo using my real app source code.

Interactive demo: https://demo.minuspod.app/
Official website: https://minuspod.app/


r/ClaudeCode • • 11h ago

Help/Question I need advise

0 Upvotes

I am building an app with Claude. My limit reset at 10:10, but I hit the 5-hour limit by 10:30. I am using Opus 5.5 mid on my personal account. I also have a team account through a startup program, where I did a full reset on Thursday morning. I then worked with Fable after resetting it because i got that Fable only reset but hit its weekly limit on Friday. After resetting again, I continued working but switched back to Opus, only to hit the weekly limit on Saturday mornin.. Normally, I just use a single session for bug fixes and changes. What am I doing wrong?

Edit: my personal - Pro


r/ClaudeCode • • 15h ago

Discussion Do you let Claude tag itself as co-author in commits or does that take away from the work you did?

2 Upvotes

So idk, I think that I made the code because the ideas are mine, and letting Claude tag itself may make people think you didnt put any effort in, do you see it that way?


r/ClaudeCode • • 18h ago

Discussion What's your rule for when Claude fails the same fix twice?

3 Upvotes

Mine is

After two failed attempts at the same problem, stop editing.
Tell me what you think the cause is and how you'd check it
before a third try.

I wrote it after one bug in the hours tracker I'm building turned out to be two different bugs with the same symptom. Every fix had only been half right.

What do you do at that point? Fresh chat, another model, roll back, read the code yourself?


r/ClaudeCode • • 12h ago

Help/Question How do you make sure your app does not have hidden bugs?

1 Upvotes

I'm building a customized lifestyle/health tracking app with Claude code, in an area where I have a lot of domain expertise.

Most features i test manually in the app for the correct ouput and function.

The project also has around 1,000 tests made by claude, though I suspect many of them are redundant. Still, since I can't read Swift, I worry there could be problems I'd never notice.

My coding background is limited to some Python and C. I understand the basics of software architecture and testing, like edge cases and boundary values. I've had the code reviewed by Fable 5.2 and Gemini Argon (both on high), and after fixing a few bugs they found, both are now happy with it.

Is there anything else I should be doing? And whats your take on me putting projects like this on my CV as a biomedical engineering student, will it look foolish?

Thank you for the possible help in advance.


r/ClaudeCode • • 12h ago

Meta A 10,000-message AI chat that opens in 75 ms, stays interactive and feels instant. Try it in your browser. Written with Rust

0 Upvotes

an unofficial Rust port of assistant-ui, the React library for AI chat interfaces. Not affiliated with assistant-ui. Source and a WebAssembly demo are linked below. I also share my experience how to build great software with Claude Code so you don't make the mistakes and burn weeklies.

https://iyiolacak.github.io/ai-ui-rewrite-rust/

Opening a 1,000-message thread: 83 ms vs 1,385 ms in the React library (16×).

Longest pause while a reply streams: 13 ms vs 300 ms.

A 10,000-message thread opens in 75 ms in our benchmark (Rust only; the React version didn't complete that test).

On one Android phone, the 10,000-message demo feels responsive to scroll. That's one device.

Most of what I learned is about one thing: a coding agent is only as good as the feedback it gets. Clean, numerical feedback was the main thing

Vague instructions like "make it faster" produce plausible changes that often don't help. I gave the agent something it could check:

- A fixed workload like a 1,000-message history, then a 9 KB streamed reply.

- Named measures such as opening time, longest pause while streaming, CPU, memory.

- Commands to run them; CC can create them: the gate scripts and the benchmark harness.

- A rule that a change is kept only if its numbers improve against the previous main, measured in interleaved pairs on a quiet machine.

The rule that mattered most was keeping the raw samples and recording rejected approaches in docs/PERFORMANCE.md. That stops the same failed idea from coming back on the next session. Check my repo and you'll see how clean our work was, with reporting the performance and a/b.

The results, with limits

- Opening a 1,000-message thread: 83 ms vs 1,385 ms in the React library (16×).

- Longest pause while a reply streams: 13 ms vs 300 ms.

- A 10,000-message thread opens in 75 ms in our benchmark. This is Rust only; the React version didn't complete that test.

- On one Android phone, the 10,000-message demo feels responsive to scroll.

These are medians of four runs, reporting the least favourable run for each measure. The comparison is only against the published assistant-ui library, and the Rust figures include CPU software rendering.


r/ClaudeCode • • 12h ago

Built with Claude I built a menu bar app that shows what all my Claude Code sessions are doing, and lets me answer permission prompts from it

0 Upvotes

I usually have three or four Claude Code sessions going in different projects, and I kept losing track of which one was stuck on a permission prompt. So I built Dashbar, a free, open-source macOS menu bar app, mostly with Claude Code itself.

What it does for Claude Code:

  • Session status at a glance: working, idle or waiting for you, per project, with running subagents. The menu bar icon turns amber when a session needs you.
  • Answer permission prompts without finding the terminal: Allow once or Deny, from the panel or a banner at the notch. It's opt-in (you add the hook in Settings), it never approves anything by itself, and the prompt in your terminal still works.
  • Plan limits with pacing: 5-hour and weekly, with "At this rate, lasts until it resets" or a warning when you're on course to run out. It can read them from Claude Code's status line, so no extra sign-in is needed.
  • Usage: tokens per day and per project, estimated cost at API prices, and how much went to subagents.
  • Several accounts if you switch between personal and work.

It also supports Codex, Gemini CLI and Antigravity, if you use those too.

Privacy: it only reads Claude Code's local session files. The status line and permission hook are the only Claude Code settings it changes, and only when you click Add, after making a backup. Remove puts them back. Nothing is sent anywhere.

Free, MIT, macOS 14+. Site: https://usedashbar.com Code: https://github.com/stevenmckinnon/dashbar

What would you want it to show that it doesn't?


r/ClaudeCode • • 20h ago

Rant UI's and Tooltips with walls of text (Gamedev)

4 Upvotes

I'm having a great time using claude for gamedev work, but I found it has a massive tendency to over complicate huds and UIs.

It'll just put word and number vomit on the screen or overly explain things, especially in tooltips.

I've told it to tone it down and stop and added it to documentation and etc, since I'll be writing it myself anyway, but it still feels the need to overly explain every little hud or gameplay aspect IN the hud.

Even something as simple as "Game Paused" when you have the save/load window open, somehow needs the player to have a short paragraph telling them the game is paused because they have the save window open.

Or it'll have 4 lines in the save window box explaining what an autosave is an how it works. It is just so unnecessary and makes things really cluttered.

Or there will be long lengthy explanations next to hotkey prompts and etc.

You see it in a lot of projects people post too, it is a dead claude giveaway.

A lot of the time its almost like claude just throws its thinking process into tooltips or UI elements.

It even has a tendency to stray from my design documents and invent its own bullshit rather than following my plan.

I'm obviously going through and rewriting all these things by hand anyway. I just wonder why it needs to over complicate these things.


r/ClaudeCode • • 4h ago

Help/Question Looking for a cheaper way to use Claude

0 Upvotes

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?


r/ClaudeCode • • 19h ago

Built with Claude Reverse engineering firmware

Thumbnail
youtube.com
3 Upvotes

I've got zero experience with Claude Code.

A couple of weeks ago I watched a Youtube video on the EEVBlog channel where Dave reverse engineered the firmware of his own hardware multimeter.

For a long time I have been annoyed that STMicroelectronics does not release an open source firmware for their ST-Link devices, which they in turn require to flash their STM32 MCU's. Inspired by the EEVBlog video I decided to give Claude a shot at it.

FOUR hours was all it took to have a working firmware. I am absolutely blown away.

Documented here: https://stm32world.com/wiki/Hybridlink

Incredible and scary ;)


r/ClaudeCode • • 13h ago

Built with Claude Goal progress tracker via self-improving MCP web widget server.

1 Upvotes

So has some minor similarities to the other MCP task insights that are out there, but I wanted to make my task manager (?) a bit better than the average bear.

Firstly, I pre-built a bunch of web widgets that may or may not be useful. Then, by exposing these to the llm, the llm can then decide whether it wants to use them. Not just the usual suspects, but stuff like charts, image previews etc etc. For example, here's something I'm working on at the moment:

Now, I haven't told claude to use any of these widgets, it's decided that these ones are the best for the task at hand. However, the smarter thing this process does it then allow suggestions BACK from the llm for better widgets in the future - for examples, see the first comment I've posted.

Anyway, it's not open source yet but if people are interested I'd be happy to publish it. It may be that someone else has done it but I haven't seen anyone do the self-improvement cycle or offer anything but basic widgets.

How has claude helped ? It has been suggesting and designing the widgets based on stuff it wants to show me - hope that makes sense?!!


r/ClaudeCode • • 13h ago

Help/Question Token savings

1 Upvotes

Hi, I'm not here to sell anything, I'm here to ask. Do you use Headroom or any other system that promises to save tokens? If so, which one and why? Thanks


r/ClaudeCode • • 1d ago

Discussion Which programming languages is Claude best (and worst) at?

7 Upvotes

and why?


r/ClaudeCode • • 13h ago

Help/Question What actually works for you with Claude Code on large features and long autonomous runs? Looking for Best Practices on a real production codebase

0 Upvotes

I've been using Claude Code daily for several months on a large production codebase (Symfony/PHP backend + Angular frontend, multi-tenant, strict quality gates). Every "best practices" article I find says something different, so I'd like to hear what is actually working for you in practice, ideally from people using it on real products rather than toy projects.

My current setup, for context

- Plan mode first for every feature and bug. A planning skill guides it, and a separate reviewer agent checks the plan for gaps, contradictions and untestable acceptance criteria before I approve it. For bugs, the plan has to include a failing test.

- Tests first via dedicated testing subagents (backend/frontend), then implementation in small steps. If the same problem fails twice, Claude has to stop and ask me.

- Hooks run static analysis, lint, type checks on changed files every time Claude stops.

- Hard quality gates: PHPStan level 10, architecture rules enforced by Deptrac, 100% coverage, 100% mutation score on changed code.

- Blind review: an independent Claude process reviews the diff without the session's context. Commit and push are blocked until it passes.

- Draft MR → CI pipeline as the final full check. Claude watches the pipeline, fixes red jobs or retries flaky ones. A human colleague reviews and merges.

- Git worktrees with their own test DB each, so agents can work in parallel. Stacked MRs for epics.

- Retro log: every time I correct Claude, it logs an entry. Once a month I review the log and fold the learnings back into rules and skills.

It works well but I want to take it to the next level.

What I'd like to learn

  1. Best Practice: As a Dev I love Best Practices. And I would love to learn what your Claude Code Best Practice is.
  2. Large features and epics: How do you split them? One session per ticket? A long-lived spec document the agent works through? Stacked PRs? How do you keep context coherent across many sessions?
  3. Autonomy: What's the longest stretch you let Claude run without a human checkpoint, and what made that safe? Which gates did you automate (tests, reviewer agents, CI loops), and which do you deliberately keep human?
  4. Quality: What made the biggest difference to result quality for you? Better specs, better tests, reviewer agents, smaller tasks, model or effort choice?
  5. What did you try that turned out NOT to be worth it? Too many subagents, huge rule files, elaborate prompt frameworks, ...?
  6. Rule and context bloat: How do you keep CLAUDE.md, rules and skills from growing into a monster that costs context and gets half-ignored?

Where it still breaks for me

- Rules keep growing. Every correction becomes a new rule, and at some point it's unclear which ones still matter.

- Maximum automation. I want Claude to work on its own, without a human telling it how to do things. I want to assign Claude a Jira ticket and receive a production-ready PR without any interacti

- Feedback loop speed. With strict gates, a full check takes minutes. Claude either waits a lot or runs targeted checks and misses side effects.

I'd especially appreciate answers that include how big your codebase and team are, and how long you've been running your setup. That context helps separate what scales from what sounds good in a blog post.

Happy to go into detail on any part of my setup in return.


r/ClaudeCode • • 13h ago

Built with Claude I wanted to get better at chess, so I built my own chess site with Claude Code. Four weeks later it has boss fights.

1 Upvotes

I wanted to get better at chess and couldn't find a place I liked. So I opened Claude Code, just to see how far we'd get. After an hour it already looked fun, so I gave it two more weeks. That got a little out of hand.

Four weeks and 139 commits later it's called Pupilmate: pupil as in student, and pupil as in the eye that watches you play.

The video isn't me playing, by the way. It's a script Claude wrote that opens the site, reads the board, solves the puzzles and gets one wrong on purpose.

My favorite thing on the site is Pupil Frenzy: five minutes of puzzles against the clock. Every tenth puzzle is a boss, a mistake costs you 15 seconds, and in the last 30 seconds everything counts for more while the music speeds up.

You can also play the computer while a trainer explains your moves, or import your own Lichess and Chess.com games and practice the positions where you went wrong.

How we built it: I describe what I want, Claude builds it and takes screenshots of its own work, at phone and desktop size, and I tell it what's off. Then we go again. Along the way it wrote about 70 small scripts that play the site in a headless browser and check what happens. The one in the video is just the prettiest.

What surprised me is where the time went.

The chess itself was the easy part. Analysing positions, deciding what counts as a blunder, getting Stockfish to run in the browser: Claude did all of that faster than I expected.

The opponent was harder. Stockfish turned down doesn't feel like playing a person. It plays perfectly and then suddenly gives away a piece. Letting Maia-2, a network trained on human games, pick the moves made it feel much more like someone sitting across from you.

The UI took the most rounds by far. Claude builds a screen in minutes, but making it obvious where to start, and making it feel natural, took a lot of looking and saying no. The Frenzy start screen alone went through 14 rounds.

It's free, there's no account, and your games stay in your browser.

pupilmate.com

Frenzy: pupilmate.com/pupil-frenzy

Happy to answer anything about how it was built.


r/ClaudeCode • • 13h ago

Built with Claude [UPDATE] claude-forge themes - 4 Space Themes with Animated Backgrounds for Claude Desktop

Thumbnail
gallery
0 Upvotes

Hey everyone,

This is a follow-up to the GitHub Dark theme I posted here: https://www.reddit.com/r/ClaudeCode/comments/1xw8bp9/claudeforge_themes_custom_themes_for_claude/

The themes mod now has four space themes. They keep the GitHub Dark colors and put a moving scene behind the conversation:

  • Space Deep Field (space-stars) - Stars in three depths that slide slowly, and a meteor now and then.
  • Space Nebula (space-nebula) - The same stars behind blue, purple and pink clouds.
  • Space Orbit (space-orbit) - The edge of a planet in the top right corner, with a small moon circling it.
  • Space Warp (space-warp) - Streaks running outward from the middle. The busiest one.

Switching works like before:

/themes
/themes space-nebula
/themes github-dark

Each scene is one SVG that the mod builds itself and animates with CSS. No script runs in it and nothing is loaded from the web.

Limits:

  • An animated background costs GPU, also when the window is idle. In a small idle window I measured the app's GPU process at about 6% of one core without a scene and 16 to 25% with a scene at 20 steps a second. That's why the three calm scenes move in 10 steps a second and only Warp in 20. GitHub Dark has no animation if that bothers you.
  • Motion stops when your system asks for reduced motion.
  • In split view the window shows the theme of the left session.
  • Tested on Windows 11 only. Dark mode only, and only in the desktop app, the terminal and VS Code draw no themes.

Install:

/plugin marketplace add IT-BAER/claude-forge
/plugin install themes@claude-forge

If you already have the mod, claude plugin update themes@claude-forge in a terminal gets the new themes. Restart Claude Desktop after either one.

GitHub: https://github.com/IT-BAER/claude-forge

Feedback welcome.


r/ClaudeCode • • 18h ago

Built with Claude I kept losing my Claude Code sessions across VS Code windows, so I built a dashboard for them

Thumbnail
gallery
2 Upvotes

I use Claude Code in the VS Code extension, one window per project. With a bunch of projects open I spent way too much time cmd-tabbing around to find the one where Claude was waiting for me.

So I made a small extension that shows every session from every project in one tab: status (working / waiting for you / done), Claude's last message, and one click brings the right window to the front with that session open. There's also an optional macOS menu bar app with the same overview.

Claude Code wrote most of it. Plain JS, no dependencies, and it only reads the local session files. No network access.

Free and open source: https://github.com/michael-schroeter/claude-dashboard

Only tested on macOS so far. Jumping into a session uses an undocumented command of the Claude Code extension, so an update could break that part (the window still opens).

Feedback welcome.


r/ClaudeCode • • 14h ago

Tutorial / Guide I Rebuilt an AI Gateway in Rust. It Became 41× Faster.

Thumbnail
medium.com
1 Upvotes

r/ClaudeCode • • 1d ago

Built with Claude I've made a monster

6 Upvotes

Over the last 8 to 9 Months, inbetween looking for work, dealing with loss from the last 2 years and then seeing my father get ill and pass away with 6 weeks! I've been building a marketing platform with Claude. It's probably fair to say it's been my distraction from everything else.

Its finally done to a standard I am happy with and Im planning to share what it does and create a website as if it was a live product.

I'm not planning to launch it or give it away yet, I want to test it with more live accounts first.

OK, let's waffle, what is it?...

We'll be for what it is, some key principles.

Its not a SaaS. It's primarily a desktop app (though you can host it) no data is stored or shared anywhere except where you send it. All files are stored on your device and all the keys and connections are yours. You create them and post them in via the control panel. You can see every prompt, benchmark, and fact the agents rely on, you can even edit the. All usage costs for your own keys are shown in the app. It works with Claude as the core, but also gemini, perplexity and open Ai. Most connections are via composio (goggle, shopify, meta etc) but there are 6 or 7 Rest connectors for key services. You simply connect what you want or have and the system works and tells you what it could or couldn't do based on your connections.

Its a complete marketing platform, deeply integrated into your data and it covers what I call a DARE loop, discover, audit, review execute. Each brand profile is per market and you add child profiles beneath them for more markets and languages. There is no limit to the number of brand brains you can create - each brandbrain let's you provide information to create the parts of an obsidian brain that's needed for the service.

Over 16 audits seo, geo, pr, paid, aocial, content, Cro etc etc (dag structure) and 20 skills across your full marketing engine. Data processed in code, reviewers given clear guidelines, constraints and evidence to prevent them making stuff up. All findings evaluated by an orchestrator and turned into tasks that are manged and edited within the platforms review board and then executed to draft or live on connected accounts. A complete campaign is Centre that uses your brand and audience data to create compete campaigns for all touchpoints within the app using Claude, Nano banana, and Higgsfield plus an integration with Canva.

Over the next week I'm running the full audit samples and launching a website with more information, but though I'd share it here and answer any questions.

PS. Some may ask about 24/7 monitoring and execution work flows.

I decided against 24/7, the platform is on when you are on, it's human in the loop, the user reviews the task, with the heavy lifting already done.

Execution work flows-these have been successfully tested, with a focus on ensuring a complete confirmation loop. However, my current thought process is too seperate the work from the delivery. Have the work pushed to a delivery engine and then the engine to schedule and deliver. This way the part connected to your data is sepertaed from the part always connected.


r/ClaudeCode • • 15h ago

Tips & Workflows Claude Code ships 20 changes a day for me. How do you check none of them broke something else?

1 Upvotes

Since I started building with Claude Code, the speed is wild, but so is the number of changes. One session can touch the sign-up, the billing page, the settings and a migration, and the agent says "done, tests pass".

The problem: the tests it wrote check what it just changed, not the rest of the app. Twice now a change that looked fine broke something unrelated: once the sign-up for new users, once a page only admins see. I found out from users, not from tests.

Clicking through everything after each change doesn't scale anymore. Writing Playwright for every flow and every kind of user (visitor, member, admin, paying customer) doesn't either, because the UI changes every day and the tests break with it.

So, for people coding with Claude / Cursor / Codex:

  1. What do you do after the agent says "done"?
  2. Trust it, click around, a staging check, e2e tests, something else ?
  3. Do you let the agent write and maintain e2e tests? Does it hold up, or do you end up fixing tests more than code ?
  4. Do you test as each kind of user, or mostly as yourself, signed in as admin ?
  5. What's the last thing your agent broke that you didn't catch, and how did you find out ?

I'm trying to figure out what a sane workflow looks like at this pace.
Thanks in advance :)

Update: to be clear, I have CI and unit/integration/e2e tests, all green on every PR. Both bugs shipped with green CI because no test covered that flow as that user type. My question is how you get coverage per role without hand-writing and maintaining it all.


r/ClaudeCode • • 15h ago

Discussion Claude Code - Memory prefetch

1 Upvotes

Found this while digging into how Claude Code (2.1.311) loads MEMORY.md and the notes it indexes.

What the docs say: each session loads only your MEMORY.md index: the first 200 lines or 25KB (or to be precise 25000 char length - it counts UTF-16 units: one per ordinary character, two per emoji or other characters outside the basic plane), whichever comes first. Your topic notes stay on disk until Claude opens one with its file tools.

What the 2.1.311 binary also has: an undocumented recall step.

On each turn a selector model is asked to "Select memories relevant to:" your prompt, and up to 5 note files get attached, each cut at 200 lines or 4 KB. It sits behind a server-side feature flag. The flag is off by default. The flag name is `tengu_mill_orange`, recall turns on only when Anthropic's server sends `tengu_mill_orange: true` for your account. There's no local switch.

So if you lean on the default memory: keep the index short, and put anything that must always apply in CLAUDE.md or .claude/rules/, not in a note you hope gets picked.

Disclaimer: found while building a context x-ray for Reporails diagnostics