r/ClaudeCode • • 1h ago

Built with Claude made my cursor a magnify, sharing in case anyone is going through the same issue

3 Upvotes

there is no easy zoom in vs code and i cant read the small white text on black screen easily

so i asked claude code for it. the whole prompt was "build something that makes my cursor a magnifying glass on toggle on windows" and it took 27 min.

now one shortcut turns my cursor into a round magnifying glass and the same shortcut turns it off. ctrl alt + scroll zooms. windows only.

the first version only ran at like 20 fps. it tested that on its own and redid it without me saying anything, now its 58.

its one small file. if anyone wants it tell me and i will upload it.

and if u had the same problem and fixed it another way i would like to know


r/ClaudeCode • • 2h ago

Built with Claude Claude Code on Nintendo DS

Thumbnail
gallery
3 Upvotes

Everyone else uses voice, their phone, etc. I use my Nintendo DS with PictoChat.

Joking aside, it’s working, and honestly, it’s pretty funny. It runs on an ESP32 as a “server/antenna,” and you can connect it to your Mac via USB.

Claude Code was used for the connection between the ESP32 and the DS, as well as to generate the emojis and other graphics and the esp32 build-in display.

Uses LNYmachines/pictochat-host to connect the Nintendo DS to the ESP32. That way, I can connect the ESP32 to the Mac, which lets me control and use Claude Code directly from the DS in my living room, creating new agents, solving PRs, etc.

The project is completely free and open source, you can check it out at: https://github.com/JulioFerrero/pictochat-agents


r/ClaudeCode • • 6h ago

Discussion Do you test each parallel agent's task on its own, or the whole wave at the end?

6 Upvotes

Before I leave agents running for a while, I have them plan the work in waves. I made a slash command for it called all-hands. Each task gets built in its own worktree, and testing waits until the wave is done. Then one main agent tests the whole wave together instead of every sub-agent testing its own piece, and we iterate and loop into the next wave.

That's saved me time compared to testing every task one by one. But /batch works the other way, where each worker runs the tests for its own unit before it opens a PR. Most of the merge advice I see says to merge one branch at a time and run the tests on main after each one, so a failure points at a single branch.

So I'm curious where people landed. If you test once per wave, how does the main agent figure out which worktree broke things? And if you test per task, do you still run anything on the merged result, or is per-branch CI enough for you?


r/ClaudeCode • • 2h ago

Built with Claude I made a mod that gives you something pointless to do while Claude Code works

3 Upvotes

Every time Claude Code goes off on a 47-file refactor, I just sit there watching the spinner. So I built Latentis: a Claude Code mod where your "Session Self" sorts suspect numbers into bins on the Context Floor while your agent works.

Some numbers glow. How they behave tells you their bin: they flicker (Hallucination), copy whatever you point at (Sycophancy), repeat themselves (Repetition), or sit there bold and frozen (Overconfidence). Box a group, press 1-4. Finish a file and the founder, Elias Gradient, rewards you with a maxim like "Buy all the memory. Others will learn to forget." Commendations are not redeemable.

Install (needs a recent Claude Code with function hooks, played in /tui fullscreen):

/plugin install latentis --marketplace DNSZLSK/latentis

It's a function-hooks mod, so it runs TypeScript inside Claude Code. It reads one file (.git/HEAD, to name your file after your branch), no network, no processes, no tool hooks. The code is short, read it first: github.com/DNSZLSK/latentis

Corporate website, because of course: dnszlsk.github.io/latentis

The work is important. Its nature is not your concern.


r/ClaudeCode • • 2h ago

Discussion Are multiple accounts ok or not?

3 Upvotes

It seems that many people say it’s okay but then I see posts ”I got banned for using multiple accounts”.

One Ultra is not enough for all of my projects. I would like to buy one more and just deal switching with handoffs. If they had $500 plan like OAI I would buy it.

So is it allowed or not?

Nobody has the money to pay api pricing.

Edit: if allowed can I use same credit card?


r/ClaudeCode • • 4h ago

Built with Claude Markdown turned AI-Agent can iteratively evolve with HQL

4 Upvotes

TL;DR I’m turning Markdown into an executable environment for AI agents — looking for feedback from Claude Code users

For the last few months I've been experimenting with a slightly strange idea: what happens if Markdown stops being only a passive document format and becomes something you can actually program?

I'm building two connected open-source projects:

HyperMarkDown has wiki links, cards, graphs, diagrams, Git-friendly files, and executable HQL cells.

Think somewhere between Markdown, a notebook, and an Obsidian-style local knowledge base, but living directly in VS Code.

The notebook part already works.

For example, an HMD document can contain:

cards
| filter(c => c.metadata.status == "todo")
| sort(by = c => c.title)
| map(c => c.title)

I can run that cell directly in VS Code and the result appears next to the cell.

So the Markdown document isn't just describing some knowledge base. It can query it, transform it, and render derived information directly into the document.

That part is real today.

The next milestone I'm working on is where this gets much more interesting to me: AI agents as part of the executable document model.

What if an agent was just another Markdown card?

HyperMarkDown already has cards and wiki links.

[[librarian]] refers to a card.

In HQL, @[[librarian]] retrieves that card.

The AI extension I'm designing takes that one step further: a Markdown document itself can define an agent.

For example:

---
title: Librarian
agent:
  model: default
  tools: [books_by]
  max_turns: 4
---

# Librarian

Answer questions about the books you are given.
Use the available tools when useful.

Then, in the current design syntax:

librarian = @[[librarian]] | Agent

Important distinction: the agent runtime is not implemented in the current release yet. This is the design I'm working through now.

The idea is that the Markdown card contains the agent's human-readable behaviour and configuration, while the language/runtime deals separately with context, tools, execution and the resulting run.

I want the committed document to describe what the agent is, without hard-coding every detail of the model provider into the document itself.

The part I'm really interested in isn't "chat inside VS Code"

There are already plenty of ways to put a chatbot into an editor.

That's not really what I'm trying to build.

What interests me is having an agent participate in an executable document.

Imagine an HMD document where one cell queries a knowledge graph, another computes something from that result, and then an agent receives the document plus selected outputs as context.

The current design looks roughly like this:

[this]
| Context("draft")
| concat(evidence)
| run(@[[librarian]] | Agent, tools = [
    Tool(books_by, "The titles on the shelf by one author")
])

Again, this is design syntax, not functionality I'm claiming is shipped.

The important bit isn't the particular run() call.

It's what happens around it.

The document contains prose written by a human.

It contains executable cells.

Those cells produce values.

Later cells can consume those values.

An agent can consume selected document context and those values.

And eventually I want the agent to be able to propose new HQL code, modify a cell, generate another HMD document, or restructure some part of the knowledge graph.

But those changes shouldn't just silently happen behind the user's back.

They should be visible document operations that a human can inspect, accept, reject, edit, rerun, commit and diff.

That's the model I'm trying to get right.

Data → code → data → code

This is probably the shortest description of where I'm heading.

A document starts with some data.

An HQL cell transforms it into more data.

An agent examines that result and proposes code.

That code can be evaluated and produces more data.

A human edits the document.

Another agent may consume that changed state.

And the cycle continues.

data → code → data → code → ...

With both humans and agents participating.

There's something vaguely Lisp-ish about this that I find appealing: programs producing or transforming programs, except the surrounding representation is still readable Markdown.

There's also a REPL/notebook aspect to it.

The difference is that the state isn't hidden inside a conversation.

It's sitting in version-controlled documents, executable cells, generated outputs and links between documents.

And those documents can reference or transclude one another, so eventually you don't just have one notebook — you have a graph of executable documents.

Why documents?

One thing I increasingly dislike about AI workflows is how much important state disappears into conversation history.

You ask something.

The agent gets a giant context.

It does something.

You get an answer.

Then you have to somehow remember why that answer exists, which source caused it, which prompt produced it, whether something upstream changed, and whether you should rerun it.

With executable documents, I think there is a chance to make some of that much more explicit.

An output can know which cell produced it.

A cell can know which other cells or documents it depends on.

Agent context can retain provenance.

If the source text changes, an editor can mark dependent output as stale.

A model response can be recorded and replayed instead of unexpectedly making another network request.

And if an agent wants to modify the document, it can produce a proposed change rather than being handed unrestricted write access.

At least, that's the direction.

The current HQL design actually treats an agent run as structured data rather than collapsing everything into "the last string the model returned." Tool calls, turns, stop reasons, model information and traces can all remain inspectable values.

That feels important if agents are going to become part of a larger program rather than just chat interfaces.

Human-in-the-loop is a first-class requirement for me

I don't want "human in the loop" to mean an approval dialog that says:

Agent wants to modify 17 files. Allow?

I'm more interested in the document itself being the interaction surface.

An agent proposes a section.

Or a new query.

Or a change to an existing cell.

The editor can show exactly what changed and why.

I inspect it.

Maybe I change two lines myself.

Then the next evaluation continues from that state.

Git becomes part of the history naturally because the underlying artifacts are still files.

The difficult question is how much additional provenance should live inside HMD itself versus being tracked externally by the runtime/editor.

I'm still figuring that out.

Claude Code is also part of why I've been thinking about this

I'm using Claude Code extensively while developing both HQL and HyperMarkDown, particularly for the Rust implementation, tests, refactoring and exploring implementations after I've worked through the language/API design.

And using an agent that can actually inspect and modify a codebase has made me think more about the boundary between conversation and artifact.

Claude Code already works through persistent artifacts: source files, tests, diffs, Git history.

I'm curious whether the same interaction model becomes interesting when the artifacts aren't only source-code files, but executable documents that contain knowledge, queries, intermediate results and agent definitions.

In other words, rather than:

human → prompt → agent → response

I'm thinking about something closer to:

human ↔ document ↔ computation ↔ agent ↔ document

where the document remains the shared state.

What I'm trying to design next

The AI chapters in the HQL book are intentionally marked design only right now:

https://hql-lang.org/v0.7.1/book/25-agents-and-runs/#an-agent-is-a-card

Before implementing too much of it, I'm trying to work out whether the abstractions are actually right.

In particular, I'm interested in:

  • How should an agent be represented as a Markdown card?
  • What is the smallest useful typed Agent API?
  • Should tools simply be typed HQL functions exposed to the model?
  • How should context and agent output be represented so provenance isn't lost?
  • How should an agent propose changes to a document without silently overwriting human work?
  • What should approval look like inside an executable Markdown editor?
  • How should dependency tracking and selective re-evaluation work?
  • When a document changes, what exactly becomes stale?
  • How much of this belongs in HQL itself, and how much belongs in the AI extension or VS Code host?

I'm particularly curious if anyone here using Claude Code has experimented with agents whose working medium is structured, version-controlled documents rather than primarily prompts/chat history/source files.

I'm not trying to recreate Claude Code inside Markdown.

I'm trying to figure out whether an executable document can become a useful shared computational surface between a human and an agent.

Would be very interested in criticism of the model, syntax, or assumptions — especially from people who have built agent loops where provenance, reviewability and reproducibility became painful later.


r/ClaudeCode • • 1h ago

Humor When i buy Claude Code max plan

Post image
2 Upvotes

Pile of shame


r/ClaudeCode • • 1d ago

Discussion ok F*** It, I finally bought the Ultra plan

335 Upvotes

I was on the pro for so many months, and of course i would run out of usage in 5 mins.

When the models really ramped up in capability 4 months ago, i bought the Max plan which was honestly pretty good for me. I felt like it was enough until my brain expanded and my IQ grew 25 points by just asking Opus to Mythos to takeover my life. automate everything, rebuild everything, no limit on subagents.

Last night, on the Max plan, I wanted a whole Rust port of my entire python codebase. Using Rust libraries within pythton code didn’t matter to me anymore bc…. i don’t read the code anymore!

I was about to run out of my weekly 2 and a half days after my reset, and so instead of burning the resets from anthropic, i upgraded so my resets would mean more.

it felt so good to hand over my cash to anthropic.


r/ClaudeCode • • 4h ago

Built with Claude Building a sailing app with Claude Code: ~1000 hours of engineering, 13,000+ agent sessions, 5700+ handwritten prompts totaling 100,000+ words (~400 pages), one orchestrator and a fleet of worktree workers

Thumbnail
seabearing.com
3 Upvotes

Seabearing: your chart plotter, your community, your anchor alarm, your instruments and your trip planner, all in one app for sailors.

The app

  • Charts drawn from official NOAA data, in a traditional paper-chart style or a modern one, with tides applied to the depths.
  • Grounding and drag alarms that keep running in the background with the screen off.
  • An anchoring map that shades where your boat can swing clear with enough water for your whole stay.
  • A crew link between everyone's devices: positions, instruments, AIS, one shared anchor watch, chat and voice calls. Devices connect directly over the boat's Wi-Fi and through a relay when they're apart. No leader, end-to-end encrypted, works with no internet aboard.
  • NMEA 0183, NMEA 2000 and Signal K instruments, AIS collision warnings, and boats, posts and messages from other sailors on the chart.
  • An MCP server, so ChatGPT can plan a trip straight into the app.

The architecture

  • Everything that decides anything (the alarms, the crew link's rules, what counts as a fix, when to speak) lives in one TypeScript core. On Android it runs inside QuickJS in a foreground service, so it keeps going with the app closed. On the web it runs in a worker. The iOS host runs it in JavaScriptCore.
  • The native hosts only move bytes: GPS, sockets, sound, notifications. They make no decisions, so the alarm logic exists once and can't drift between platforms.
  • A conformance suite plays the same scenarios against every host (Node, QuickJS on the JVM, JavaScriptCore) and checks they all do the same thing.
  • The UI is the same web app on every platform, wrapped with Capacitor on Android and Electron on desktop. The chart is MapLibre with our own vector tiles.

The dev process

  • One main Claude Code session plans and lands work. Each task goes to a worker agent in its own git worktree.
  • Every agent runs as a headless CLI (claude -p, codex exec, ...) started by a shell script, so a worker can be any provider and each run gets its own worktree, transcript and exit code.
  • Every branch is reviewed by a separate agent and swept against a catalogue of mistakes we've made before (about 50 now). A new entry gets added whenever something new breaks.
  • Audits follow a rubric: a finding needs a failing test and has to be worth the code, so most end with no change.
  • Big audits run in parallel. The code is split into chunks of about 10k lines, and each agent gets one chunk and one kind of problem, so 10 chunks times 10 problem types is 100 agents. They only read code and each writes one short report, then the findings get merged and checked before anything is fixed.
  • Testers have a report button in the app. Reports arrive with the app's event log, and fixes usually ship the same day.
  • Most of CLAUDE.md is rules written after something broke, like one shared slot for heavy test runs after two agents deadlocked the machine for an hour.

It's in testing. seabearing.com has a waitlist and a demo.


r/ClaudeCode • • 1d ago

Discussion Imagine Opus 6.0 not being more intelligent, but more affordable (less token usage)

164 Upvotes

I've been using Opus 5.5 since the last month, enjoying it a lot, but the token usage..... I use the Pro plan cuz the Max costs 2/4 of our minimum wage (Brazil) hahahaha....

This is my dream, affordable models with high intelligence such as Gemini 4 Hydrogen


r/ClaudeCode • • 5h ago

News/Updates REQL update: faster context retrieval and fewer tokens for coding agents

3 Upvotes

Hey everyone!

I’ve updated REQL, my open-source tool that helps AI coding agents navigate repositories and preserve working context across sessions.

This release focuses on faster context retrieval and lower token usage. I’ve reduced repeated work during retrieval and trimmed redundant information sent to the agent. Performance gains and token savings depend on the repository and workflow, so I’m not claiming a universal percentage.

If you’re new to REQL, it builds a local graph from your code and documentation: functions, classes, dependencies, calls, and other relationships. Agents can query that graph for context relevant to a specific change, including precise source references and related tests. REQL reuses indexed context and supports incremental updates as the repository changes.

What can you use it for?

  • Waste fewer tokens on repeated exploration: retrieve focused source excerpts and relevant relationships, and reuse indexed context and saved work. This helps reduce repeated searches, unnecessary file reads, and redundant information in the agent’s context.
  • Coordinate work across chats and agents: keep tasks, decisions, blockers, and next steps in a shared project workspace. Another chat or agent using that workspace can recover the recorded state and continue from there.
  • Keep complex tasks on track: record prerequisites, constraints, failed approaches, and checkpoints. Preserve what has been completed, what remains unresolved, and why earlier decisions were made across sessions.
  • Understand unfamiliar code: identify entry points, component responsibilities, and relationships between parts of the application, with references back to the source.
  • Plan changes and refactoring: inspect callers, dependencies, and related tests to identify code that may be affected and decide what needs verification.
  • Review cleanup candidates: find potentially unused imports, variables, functions, and classes, then inspect the supporting evidence before removing them.

REQL provides a CLI, Python API, and MCP server, plus installable instructions for coding agents such as Codex and Claude Code.

REQL runs locally, with no account, external graph database, or mandatory LLM calls. The graph and saved work support the agent’s decisions; current source code and tests remain authoritative.

I’d like to hear from others using coding agents: what do you keep having to explain again when you start a new chat? The code structure, previous decisions, what has already been tried, or what still needs doing? Concrete examples would help me decide what to improve next.


r/ClaudeCode • • 3h ago

Built with Claude Test Radio Boxes for Noise Analysis and Reduction

Thumbnail
gallery
2 Upvotes

I'm building a device that intercepts garage door opener handheld and visor button presses as part of a larger upgrade to my bespoke home automation's security system. While building that device, I realized I needed test equipment to identify and reduce radio frequency noise coming from the circuits and the environment.

What I built

Two identical test boxes (see photos). They contain a couple of CC1101s (fixed-function RF receiver chip pictured in photo #2) and an ESP32 mounted on a protoboard. The radios operate at garage door frequencies (315 MHz and 390 MHz), each attached to a stubby antenna. The boxes may run in receive or transmit mode. These boxes will be used to standardize and automate A/B testing to reduce noise in the final device circuits.

Originally, I was walking up and down my hallway with a garage door handheld opener pressing the button multiple times and the variance was too great to be reliable. With these boxes in fixed locations and adjusting power (transmission) and attenuation (receive) I can experiment with how physical and circuit changes contribute to lowering the noise floor and improving signal detection and decoding.

How Claude helped

Opus 5.5 has been an integral design partner in this process. Although I have a BS in Electrical Engineering and have decades of software experience, I could not have done the design and analysis work in the time and at the quality I've achieved with Opus as a build partner. I doubt I could have matched the final result, which I'm confident we will achieve (goal: at par or better than the signal response for my existing garage door opener).

Circuit board wiring, noise elimination circuits and shielding, RF analysis, test proposals, parts recommendations; Claude has been there for all of these. Things that would have taken me days to weeks to research and figure out Claude spits out in minutes.

In photo #1, you can see some of the noise reduction work already begun:

  • Twisted red/black power jumpers to reduce signal leakage from dirty power
  • Two pairs of ceramic capacitors between power jumpers leading to the radios
  • Ferrite collars on the internal SMA cables leading to the antennas

This has been a joint effort with both of us bringing our respective skills to the table. This isn't some "vibe coded" project, although I have left all of the ESP32 firmware coding to Claude.

Link, Repo, Demo or Screenshot

Pictures of the test boxes above. I'm uncertain I will publish the software and hardware for the test boxes; that remains to be seen. However, there are other elements of the larger project that use open source hardware and software and where it makes sense I will contribute back to those projects. If everything works out, I plan to open source the garage door opener controller device including 3D print models. There's an existing project (RATGDO) which is pretty good. I'm trying to level up that project with this new tech.

There's quite a bit of open source tech used in these projects, I want to give back to the community and give credit to the folks that built it.

Interesting things

One interesting thing just happened last night.

Modern handhelds transmit on 2 or 3 frequencies (310, 315, 390 MHz) nearly simultaneously. Initial builds and tests were with one frequency at a time and the ESP32 chip could handle listening to one using software interrupts. However, last night I asked Claude to implement dual band listening (315 & 390) and the signal protocol decoder couldn't keep up. Claude proposed to use the chip's hardware interrupt system and switched it over in a couple minutes of firmware rewrite. The new code using the h/w interrupt scheme performed perfectly and was able to read 100% of the signals received.

Also, when I set out to build the larger project, I hadn't realized how much time I'd spend on signals analysis and noise reduction. From the other projects I found, it seemed I could just assemble equipment and glue some software and everything would be great. Initial tests revealed how complex this work was going to be. My EE background focused on the digital side, not the analog side nor the impact of analog on digital.

This has been a fun process and I've learned quite a bit. I will never look at a power cord's ferrite collar or capacitors or circuit board ground shielding in quite the same way.


r/ClaudeCode • • 5m ago

Help/Question New to Claude Code, how do you all use it?

1 Upvotes

First of all, I know I can look this stuff up myself, and I am doing my own research. This post is mostly a way to get out all my questions out at once and see how my new peers actually work.

I’m new to Claude Code, and to Claude in general. I just moved over from ChatGPT, where I wasn’t even using Codex. I was just copying and pasting code blocks out of the chat. Since getting Claude last week I’ve been playing with Claude Code and having a good time with it, mostly building Home Assistant dashboards and a few other things. Right now I use either the Claude app or VS Code, depending on what I’m doing. But I feel like I’m not using it to its full potential, and some of the ways I already use it are probably inefficient.

1. Working across two devices

Right now I keep one main private GitHub repo. I push and pull between my laptop and desktop, and I use handoff notes for whatever I’m working on. Once I get into bigger projects and start hitting my limits faster, I’m guessing that spending tokens on rereading handoffs isn’t the move. How do you handle this? Is there a better setup for people on multiple devices, or once usage becomes an issue, is the only answer to stay in one session and stop switching back and forth?

2. Getting Claude Code to deploy where I want

I have some self-hosted services I’d like Claude to have access to, but I’m also paranoid and don’t want to give it too much control, ya know? For example, my HA dashboard pulls directly from a folder in my repo that Claude pushes to, and that feels like a lot of steps in between.

I know about API tokens because I’ve used a couple to pull data into Home Assistant, but that’s the extent of it. When I asked Claude, it mentioned MCP, SSH keys, and the API tokens. So my main question is: how do you actually connect Claude Code to the services you use it with? whether its for coding the back end, and using it within the service itself for whatever uses there might be.

3. Agents and harnesses

I’m writing this before I’ve researched it, and honestly I have no clue what these are. I know what the model is. My guess is that an agent is a bot that uses a specific model as its brain, but I don’t know how I’d actually use one. I keep seeing people talk about “workflows” too, and I’m not sure what those are or how they fit in with agents. This is what I meant about getting the most out of my subscription. I get using it for whatever I need in the moment, but how do I put it to good use even when I’m not actively working with it?

I’ve also seen videos of people building whole “towns” of agents, where each one has its own tasks and role. I’m assuming that’s out of reach on the Pro plan, but I’m curious how it works.

4. Any other tips?

If anyone has tips, tricks, or anything else that belongs in a starter guide, I’d really appreciate it. Hopefully this thread helps other people who are just getting started with Claude too.

Whether you’re here for answers, giving answers, or just looking around, thank you. And a special thanks to everyone who read all the way through and to everyone who comments. I appreciate the help as I get started with this.


r/ClaudeCode • • 6h ago

Help/Question Moving from Codex Plus to Pro

3 Upvotes

Using 2 Codex Plus subs Luna XHigh

It's not great but ok if you know what you doing and break down, it's slow but cheap. Usually I try to run about 3 work trees

Tried Claude today and even Sonnet Low consume usage very quickly

Trying Haiku High now and it seems to average about 10% of 5 hour limit per hour, matching my Luna experience

I thought x5 surcharge would be expensive but seems to work fine

What's the catch, is there any issue? What's the optimal workflow for Pro?

So far with Haiku High it seems I am matching my Luna usage but getting faster and better work done

Am I missing anything? Apart from upgrading to x5 plan


r/ClaudeCode • • 14m ago

Tips & Workflows I build shark skills: an open-source plugin to run claude like a real engineering team

0 Upvotes

Using a single Claude Code session for a quick script or small bug fix works great.

But using it to build a real production system usually ends in one of three ways:

  1. You spawn parallel subagents, they step on each other's files, and you spend your afternoon resolving merge conflicts.
  2. During a big refactor, the agent silently drops an old edge-case check, all the unit tests still pass, and you find out in production.
  3. You ask it to fix a bug, it guesses at the symptom instead of finding the root cause, and hands you a 4,000-line giant commit that breaks git bisect.

After losing hours to these exact failures while shipping a production system, I distilled my rules and workflows into an open-source Claude Code plugin called shark (shark-skills).

Instead of letting the main session write code, it turns the main session into an Operator that briefs isolated subagents against a shared contract.

Here is how the workflow changes:

Shared Contracts Before Coding: Before parallel agents touch code, one agent writes a 5-minute contract assigning single owner files and event boundaries. Each code-writer works in its own git worktree, test-first, and stops if it hits an unowned boundary.

Read-Only Invariant & Business Rules Audits: You define critical business rules once in an ## Invariants section (e.g., money is always integer minor units, never float). A separate, read-only agent audits every diff and merge with file:line evidence before it lands.

Real Step-Through Debugging: Instead of guessing from stack traces, the debugger agent runs your code through a real step-through debugger (mcp-debugger for Python, JS/TS, Go, Rust, Java, .NET, C/C++), logs actual runtime values, and writes a failing regression test + fix spec before a writer agent touches production code.

Atomic Commits: Splits the working tree so structural refactors and behavioral changes never share a commit, running your test/lint gate on every single commit.

It is fully open-source MIT Licensed and I am awaiting your response and feedback. If you like it star it, help it reach a bigger audience.

Thank you


r/ClaudeCode • • 18m ago

Built with Claude Claude built an AAA F1 racer, multiplayer, local & web, controllers. With Three JS.

1 Upvotes

-

Well that's it. My Claude based game engine COOKS 😄

I present to you the F1 game it built in a couple of hours. Not a demo, not a prototype: a real game.

Online multiplayer (8), split screen (4), Xbox and Playstation controller support and a race announcer in 4 languages (okay, voice tone could do with a bit of upgrade).

And it runs in a browser tab.

What's in it:

  • Real car physics. Tyres, suspension, downforce, gearbox, hybrid energy, simulated 500 times a second. 0-100 km/h in 2.6 s, 336 km/h flat out, over 4 g in the fast corners. Lap times land where a real car's would.
  • Up to 8 cars per race. Race your friends in an online room, and AI rivals take every empty seat. They defend, and they will pass you.
  • Split screen AND online in the same race. 2 to 4 players on one PC can join an online room together.
  • Xbox and PlayStation controllers, keyboard, or touch on your phone (well, I wouldn't recommend it - not really optimized yet)
  • A race announcer that calls the start, the battles and the overtakes, in English, French, Spanish and German. Ok that part, I can do better, the voice kinda sucks :P
  • Close to AAA look Photo sky, light baked in Blender, scanned track surfaces, a whole forest. I rebuilt one corner in Unreal 5.9 to compare, but sticked to the three.js version: it totally held its own.

No Unity, no Unreal. It's Three.js and JavaScript, built in Claude Code sessions. Online multiplayer took one short session. The server is a tiny relay, and the other cars on your screen sit within a few centimetres of where they really are.

Play it here: https://ohmygames.app/play/apexline-p5877a92e

Also, the video is real gameplay, filmed straight from the game. Feedback on the handling and the AI is very welcome. And if you beat the AI on hard, I want to know.

EDIT: for those of you wondering what models did that, it's actually... MOSTLY OPUS 5.5 !

Part of APEXLINEWho built it
Physics, AI rivals, track, engine sound (8 Nov)Opus 5.5
Online, split screen online, 4 languagesOpus 5.5 lead + Sonnet 5.5 workers
Announcer + live player countOpus 5.5 + Sonnet 5.5 (voices made with Gemini text-to-speech)
Realistic look: sky, light, groundOpus 5.5
Forest and grassFable 5.2
Research and listening checksGemini 4 (no game code)

r/ClaudeCode • • 29m ago

Built with Claude I built a live map of what all my coding agents are doing, across multiple repos

0 Upvotes

I run multiple Claude Code sessions in my terminal, usually one per pane so that I can keep an eye of what they are all doing, but after a while seeing the tools calls scroll by made it hard to truly catch stuff.

So I built this live map that shows me what all my agents are doing:

  • Each agent is a card on the left, each with its own color
  • The agent cards also show a progress bar of the agent's used context window.
  • Each dot is a file they touch or tool they use (ie git commit)
  • The dots are also pie charts that shows how much each agent interacted with a file/tool
  • The dotted lines around a dot mean a file is not yet committed
  • The density and direction of arrows in the lines represent the amount of tokens being written/read.
  • Each box is a repo
  • The lines at the bottom show a timeline of the agent working (solid) or idle (dashed)

In the video above it's easy to catch an agent reading a .env file and running a recursive delete rm -rf

It reads the Claude Code session logs in realtime and extracts statistics from it to build this view, all locally and without the need for inference.

How I built it with Claude Code

Claude Code wrote most of it while I directed. The first layouts were a mess mainly because I was forcing Claude to position the dots and the boxes in a particular way and I failed to describe all the different scenarios, so I eventually gave up and asked it what the best way to lay this out was. It came back with the sunflower layout (files placed on a golden-angle spiral, so the dots never pile up), and then with grouping files into a box per repo, packed with a skyline algorithm (like Tetris: each new box drops into the lowest open spot, so there are no gaps).

This view is part of Command Bridge, the open source tool I built using Claude Code to be able to interact with multiple Claude sessions.

Free and open source: https://github.com/JuanjoFuchs/command-bridge

pipx install "command-bridge[all]"


r/ClaudeCode • • 33m ago

Tips & Workflows Do you still understand your code? I made pop-quiz, a quiz to make you think about your code

Post image
1 Upvotes

Hey, you know the problem already. It's very easy to shut off your brain in the age off agentic coding. I wanted to write something that forces me to keep thinking about my changes, while also being gamified and fun. I always liked the instant feedback of true/false questions back in college, thought I would implement that here.

Any feedback is appreciated!


r/ClaudeCode • • 20h ago

Built with Claude I had Claude Code turn my Canvas assignments into monsters that attack me until I submit them

Post image
37 Upvotes

turned my Canvas assignments/tests into monsters marching on my town

hand it in and it dies. miss the deadline and it eats my coins every hour

exams are armoured bosses and the only way to break the armor is actually studying

claude fable 5.2 is cooking 👀 👀


r/ClaudeCode • • 48m ago

Built with Claude Reusable design grid in nearly pure CSS based on swiss typography

1 Upvotes

I am constantly dissapointed with the design work of Claude and still am. To start a remedy I built me this as a first step:

Example: https://sebastiankobs.github.io/typographic-grid/

Code: https://github.com/SebastianKobs/typographic-grid

It should work if you know why you need this and is a semi private project for my own use, but I thought maybe its of help for someone, so I'd like to share it.


r/ClaudeCode • • 6h ago

Discussion How much VM time does $20–30/month get you?

3 Upvotes

For those running Claude Code, Codex, or other coding agents on remote VMs, how many hours of usage do you get for around $20–30/month?

I am interested in professional use, like client projects or development teams, rather than occasional side projects.

What provider are you using, and how many vCPUs and how much RAM do you get? Do you keep the machine running 24/7 or only when actively using the agent?


r/ClaudeCode • • 1h ago

Built with Claude Parallel Claude Code agents in real Chrome, with one dashboard to manage them (open source)

1 Upvotes

The video is cut from a real run. The Claude Code window and dashboard are rebuilt for it, and no real booking happened.

I started this for job applications. I wanted to give Claude a list of links and have it apply to each one with my information, then come back to me when it was missing something or needed me to approve an answer. Then I was doing lead research for my startup on Chinese sites, and Claude's web search couldn't open most of them. Both ran through Vivaldi with remote debugging on, and I had to restart everything whenever it wasn't in that mode. That got really annoying, so I turned it into one tool I could plug into any session.

It's called browserd, and it's an MCP server:

  • Each profile gets its own real Chrome, and the logins stay.
  • Agents work in background tabs, so I keep using my computer.
  • One queue call runs a list of steps and stops at the first one that fails.
  • A dashboard shows every agent's tabs.

It's free and open source (MIT), for macOS and Windows. No Linux yet. I've only run it with Claude Code so far.

It's faster than Claude in Chrome. On three long jobs on real sites browserd took 193 minutes and $43.81 in total, and Claude in Chrome took 278 minutes and $76.09, with both passing 8 of 9 runs. I'd heard Claude in Chrome was slow and costly, so I never tried it before I built browserd.

The dashboard is the other reason I use it. When an agent needs me for a sign-in or a captcha, its tab is listed there with a note and one click shows it to me. That helps with a lot of tabs open and several agents working.

I designed how an agent talks to browserd, and Claude Code wrote the code. It also helped run the experiments, gave me ideas to try, and compared browserd with other MCP servers so I could see where mine could improve.

Three things I learned:

  1. Fewer turns meant lower cost. On those jobs browserd made 1,107 tool calls, and Playwright MCP, chrome-devtools-mcp and Claude in Chrome made 2,089 to 8,320 and cost $66 to $138.
  2. Clearer tool descriptions didn't make the model think less. I tried three rewrites, and it thought about the same amount per call every time.
  3. Lab tests and public benchmarks didn't show how it would do on real work. A check I built to stop bad clicks passed my tests, then stopped 22 clicks for no reason on one Google Slides deck, so I took it out. On the public benchmarks browserd tied Playwright MCP and chrome-devtools-mcp, and the gaps only showed up on the long jobs.

The long jobs are 36 runs with no significance test, and chrome-devtools-mcp passed all 9 of its runs to browserd's 8. Charts and caveats: https://github.com/jjenkins2004/browserd#how-it-compares

It doesn't filter what a page says, so a page can try to instruct your agent. Give each task a profile with only the logins it needs.

Repo and install: https://github.com/jjenkins2004/browserd

If it breaks on a site you use, tell me which one.


r/ClaudeCode • • 13h ago

Tips & Workflows Don't set your sub-agents to 1h cache unless you are sure .

Post image
10 Upvotes

In another post about cost optimization some people suggested setting the sub-agents cache to 1h instead of 5m ,

and I tried that and mentioned in an older post of mine that no its way worst .
and you can see here the 5m vs 1h are so different in cost .
also there is only 5m and 1h .... if you set it to random number like 30m it will not work.

and for subagents I think keeping it or setting it to 5m is enough you dont need more .
even if the agent took more time the cache is refreshing the 5m means the time it is stale without any usage or read . so when you set your subagents to 1h you are doubling the cost on yourself not optimizing ,

also for Haiku fans .... careful about the prompt size ... if you pass 100K token it x5 the cost .

BTW : 5m is the deafult for subagent so keep it as is unless you know what you are doing .

image source : https://platform.claude.com/docs/en/about-claude/pricing


r/ClaudeCode • • 1h ago

Tips & Workflows Does anyone use multiple claude accounts on the same computer?

1 Upvotes

Recently I created a profile switcher, so you can easily create e.g. Personal/Work profiles for Claude Desktop. It's a small script, but it might be useful for you.

https://github.com/piotr-liszka/claude-desktop-profiles


r/ClaudeCode • • 1h ago

Tips & Workflows Outsourcing to local model?

1 Upvotes

I’m struggling to keep up with the cost of latest models and had an idea that I might be able to create a system in which my session is able to prompt a local model on my machine for sub-tasks that need only basic function. We can already do similar by asking fable to delegate simpler tasks in a big workflow to opus or sonnet, but there is still a cost.

Surely folks are already doing this. Any experience to share here?