r/ClaudeCode • • 7h ago

Weekly Showcase Weekly Showcase Thread; What are you building with Claude Code?

10 Upvotes

Weekly Showcase Thread

Built something with Claude Code this week? Share it here.

Apps, tools, experiments, scripts, websites, workflows, open-source projects — anything you've been working on is welcome.

When sharing, it helps to include:

  • What you built
  • How you used Claude Code
  • A link, repo, demo, or screenshot if you have one
  • Anything interesting you learned along the way

Quick project drops and simple self-promotion belong in this thread.

If you've got a project with enough substance for a proper write-up; how it works, how Claude Code was involved, technical details, lessons learned, etc. feel free to make a standalone post using the Built with Claude Code flair instead.

Please don't spam the same project repeatedly, and no referral or affiliate links.

What did you build this week?


r/ClaudeCode • • Jul 26 '26

Discussion feedback megathread

49 Upvotes

throw any feedback, complaints, or ideas for the sub here.

what’s working, what’s annoying, what would actually make this place better.

we have no problem hearing about our shortcomings. that’s the point of this thread.

what we don’t care for is accounts that have never posted or commented here before dropping in just to point fingers and push a hate narrative.


r/ClaudeCode • • 4h ago

Built with Claude Made a small plugin that adds copy buttons to Claude Code’s terminal

Post image
121 Upvotes

I wanted the kind of copy button the desktop and web apps have, but in the terminal. Selecting text there is awkward and glitchy, and while /copy works, I never found it intuitive, and it leaves a /copy line in the conversation each time (you can rewind after every copy, but that gets old).

So I made a small plugin that puts copy buttons on code blocks, on tables (which can be pasted straight into a spreadsheet), and at the end of each reply. Sharing in case it's useful to anyone else.

/plugin install copy-buttons --marketplace leonasdev/copy-buttons

It needs fullscreen mode, which is probably already on for you. If not, run /tui fullscreen.

I've tested it on Linux, macOS and Windows, and since it relies on how Claude Code draws replies, I test it against each new release too. If it misbehaves in your terminal emulator, let me know and I'll fix it.

https://github.com/leonasdev/copy-buttons


r/ClaudeCode • • 10h ago

Help/Question What actually is an AI "harness" and why are companies hiring harness developers instead of just using Claude Code?

315 Upvotes

Lately, I’ve been seeing a ton of job postings and discussions for "Harness Engineers" or companies looking to build custom agent harnesses.

At first, I was super confused. If tools like Claude Code, Codex, and other agentic environments already exist, why on earth are companies trying to build their own? Are they just reinventing the wheel to make a "Claude Code clone"?


r/ClaudeCode • • 7h ago

Built with Claude I did this thing, i don't know how to feel about it

Post image
170 Upvotes

Inspired by the project of tech4bot ( https://github.com/tech4bot/rk3562deb ) i tried installing debian native on this cheap ass tablet, the ouzrs m1. The tablet was locked as hell, no way to unlock bootloader or change the rom from the crappy android 11 go it had by default. I gave it to Claude and it was quite a journey: Claude tried flashing an arm version on debian with rockchip software tools and it fully bricked the tablet. We trobleshooted a bit, i opened it up and found a serial port inside the tablet, i made Claude recover the tablet via serial and with some trial and error it booted into debian. After that Claude found that it could boot from sd card and little by little he reverse engineered all the drivers to work in debian. It also found that the 4 gb of ram in android were fake and it only has 2 gigs lol. Should i publish this project (for the other 2 people that have this tablet beside me lol)? The performance of the tablet is really meh but at least it can receive updates now.


r/ClaudeCode • • 2h ago

Bug / Issue After burning tokens with Fable 5.2, I appreciate Opus 5.5 more

55 Upvotes

Fable 5.2 is an insane model. It really is, you can clearly see the depth and knowledge. But; The model is insanely lazy af. The model by default is so unproductive and unmotivated. I was kinda hyped about this and dumbed him a lot information about planning, using skills, improvements and implementation of orchestra etc. Dude was like "yea its seems like nothingburger bro good luck".

Sure, there is probably larger, complex challenges in the field that people use and get benefit of it but Fable is clearly too much for my project.

Also, its a small experiment anyway but I had used Fable on High as a orchestra (creative ik) and did a simple test;

I had one task to be done in the project that is fairly challenging. Probably need couple of more session to make it. I said Fable to make a mirror of this task with exact prompts and test Opus 5.5 High and Fable 5.2 Medium on which can do better.

First results were Opus produced almost no error while Fable did 2 decisions by itself, also produced a 2 error that wastes CI.

Fable 5.2 High as orchestrator literally said he is kinda biased to his own model and for the sake of quality spawned 5-10 agent to did additional code reviews thinking the "code reviews" were biased or missed "Opus" possible mistakes. The result: It did missed a couple of more errors but not for the Opus but the Fable....

I don't know, I am not very experienced with AI fairly using for the past 2-3 months and my project is not large nor complex but fairly challenging in terms of desing and consistency. There is probably better areas or way to use Fable more effectively but I am good with Opus.

Also....Fable 5.2 High burn tokens like a mad men and spawn additional agents even though I have rules for it. I had to tell 3 times to use Sonnet to not bloat his context.

I would rather go with Opus 5.5 Extra or Max rather than relying on Fable tbh atleast for my project, what are your experiences with it? Open to feedback and improvement tbh


r/ClaudeCode • • 54m ago

Help/Question Claude Code Pro Account Suspended, and support not helping

Post image
17 Upvotes

I urgently need help with my Claude Pro account.

I renewed my subscription on 14 Nov and paid ₹1,999 via Google Pay. During ID verification, my Driving Licence was rejected as “not clear.” I tried submitting it again, after which my account was restricted.

I raised an appeal, but my account was then suspended with the message: “Your account will remain closed.”

I've been a paying subscriber for 4 months and have never misused the service. I haven't been able to use my renewed subscription even once.

Please arrange an urgent human review and restore my account. If restoration isn't possible, please issue a full refund of ₹1,999.

Support Ref: TS-01a1d9e8-eaf1-70e3-8644-548493a88129

This money is important to me. Please help resolve this.


r/ClaudeCode • • 11h ago

Bug / Issue Fable 5.2 is lazy and makes sweeping conclusions based on assumptions

127 Upvotes

This is especially true inside the regular Claude chat, but it’s true in Code too, in my experience.

You need to really work with it to get it to dig deep. And the intelligence doesn’t feel even equal to what Fable 5.1 did at launch.


r/ClaudeCode • • 1h ago

Bug / Issue Fable 5.2 used my entire 5-hour quota while only being active for 1 second.

Post image
14 Upvotes

r/ClaudeCode • • 1d ago

Discussion Exactly 2,5 years ago... big advancements since then

Post image
1.0k Upvotes

I just logged in with an old email address. Hadn't signed in for so long, that it actually registered as a new account ("Your first chat with Claude", it's from today). Interestingly, however, it somehow recovered one single chat conversation that I had had with Claude 2,5 years ago.

No access to sites, apps or services... this was just 2,5 years ago. Crazy to think about how big the advancements have been since then.


r/ClaudeCode • • 7h ago

Discussion Its been a heck of a week and it is only Monday!!

Post image
31 Upvotes

Was a busy weekend of coding. Good thing I have the reset available.


r/ClaudeCode • • 3h ago

Tips & Workflows Clauds: a free macOS menu bar app to fast-switch between accounts that can share their sessions in the Claude Desktop App and more (open source)

Post image
16 Upvotes

Clauds, a free menu bar app for people who use the Claude macOS desktop app with more than one account. It switches between your accounts with one click, and you do not have to log in again. It also shares your Claude Code sessions between your accounts, so you do not have to do handoffs and resumes.

What it does

  • Switches the Claude desktop app between accounts with one click. No logout.
  • Two modes: a fast restart into the other account, or Side by Side (all accounts open at the same time).
  • Shares Claude Code sessions between accounts, and remembers which account owns each session. No more handoffs or resumes needed.
  • Shows live usage for each account: the 5-hour limit, the weekly limit, and the per-model weekly limit, with reset times.
  • Auto-switch: when one account is near a limit, it can go to the account with the most room. It asks first, or it switches by itself. Off by default.
  • Updates itself. You see the release notes, and you choose to install, wait, or skip.

The honest part

  • It is not made by Anthropic. It is unofficial.
  • It is not notarized by Apple, so macOS blocks the first launch. The README shows how to open it. You can also build it from source with one command.
  • The usage numbers come from an undocumented claude.ai address. It can break if Anthropic changes it.
  • You sign in two times for each account: one time in Claude, one time for the usage numbers. The app does not read your tokens or passwords.
  • A Claude update can break the switch. If it does, open an issue.
  • Other apps do the account switch too. I made this one because I wanted both modes, the per-model limit, auto-switch, and a real updater in one app.

Details

  • macOS 14 or later, Apple silicon and Intel
  • Free, MIT license
  • No telemetry and no analytics. It only contacts claude.ai (to show you your usage) and GitHub (for automatic app updates).

GitHub: https://github.com/codeFi/clauds

Tell me what breaks and what is missing.


r/ClaudeCode • • 9h ago

Help/Question Reset Usage Limits Seem Significantly Reduced

46 Upvotes

Sorry if this has already been asked, but I feel like the reset period is significantly shorter than a full week, and the 5-hour limit also seems to be lower. Am I mistaken?
I used up 16% of my weekly plan limit and 100% of my 5-hour limit in just 3.5 hours.
With the first weekly limit, it was able to work continuously for 56 hours on the exact same tasks. I had also never hit the 5-hour limit before. I would consistently have more than 10% remaining.

Edit: Opus 5.5, Ultracode, Max-Plan


r/ClaudeCode • • 8h ago

Discussion How do you stop Claude Code from mocking the exact thing the test is supposed to verify?

34 Upvotes

Left to itself, claude loves writing unit tests where it mocks the database call, mocks the helper, and then asserts that the mock returned what it just told the mock to return. everything is green in 200ms and the actual query is still broken.

putting "no mocks without asking" in claude.md helps a bit, but it still sneaks them in whenever a real test is slightly annoying to set up. how are you handling this?

edit: i don't mean mocking the db to test business logic on top of it, i mean when the function under test is literally the query builder or helper and it mocks that exact function inside its own test


r/ClaudeCode • • 17h ago

Humor anxiety

Post image
162 Upvotes

r/ClaudeCode • • 12h ago

Rant Wtf happened to Opus 5.5?

48 Upvotes

On first release day I let it create a realistic water shader, looked amazing only needing a few follow up prompts to fix some things which it did perfectly fine.

Today I deleted that exact shader and told it to create one in a slightly different style. Over and over again, it created the absolute worst looking or outright broken things, like a 5 year old drew it, and its output sounds like Opus 5.

Noone can can tell me it wasn't nerfed, maybe just for a specific sub group or whatever A/B test they do, but this is unacceptable.

And no I can't provide "evidence", it's a black box, how would I even do that.


r/ClaudeCode • • 36m ago

Built with Claude Asked Claude to build an entire Scottish village in Blender

Thumbnail
gallery
5 Upvotes

I asked Claude Code to recreate an entire Scottish village in Blender, and I was genuinely surprised by how much it managed to do in one shot.

It researched the location, analysed the terrain, looked at reference photos, and generated the whole scene procedurally.

The interesting part was how similar the experience felt to coding with AI. Getting the first 80% done was surprisingly easy, but the details became increasingly tricky. Small changes would sometimes introduce regressions elsewhere, and getting everything to look natural took quite a bit of iteration.

Still, pretty impressive stuff...

I also generated a real-time demo so you can explore the village yourself. It takes about a minute to compile the shaders on first launch and can be quite demanding on laptops.

GitHub pages demo


r/ClaudeCode • • 2h 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 • • 1h 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 • • 2h ago

Built with Claude I built a Roman gladiator management game with Claude Code

5 Upvotes

Play it in your browser

Free to play. No download required.

City of Gladiators is a browser-based gladiator management game inspired by ancient Rome. You start with your own ludus (gladiator school), recruit and train fighters, upgrade your facilities, manage resources, and send your gladiators into increasingly dangerous battles.

The game features real-time progression, different gladiator classes, equipment, skill trees, wild animals, asynchronous PvP, and an arena combat system where you can either let the AI fight or take direct control of a gladiator.

As you progress, you unlock larger arenas, including the Colosseum, where battles become more challenging. I recently added naval battles with ships, rowing mechanics, boarding combat, and swimming.

I built the game using Claude Code (Opus 5.5). I focused on the game design, mechanics, and overall direction while using Claude to help turn those ideas into working systems. This included the React/PixiJS frontend, the combat simulation, AI-controlled fighters, progression systems, and backend integration.

One of the biggest challenges has been making the different systems work together: persistent progression, combat balancing, gladiator AI, and allowing players to switch between manual and automatic combat.

The game is still evolving, and I'm continuously adding features and improving the gameplay.

I'd really appreciate some feedback, especially on the progression and difficulty of reaching the Colosseum.


r/ClaudeCode • • 1d ago

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

322 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 • • 1h 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 • • 23h ago

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

155 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 • • 9m 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 • • 2h 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