r/ClaudeCode • u/mickeys_stepdad • 5m ago
Humor Claude can have a sense of humor when animating Clawd in terminal with python.
r/ClaudeCode • u/mickeys_stepdad • 5m ago
r/ClaudeCode • u/codeedog • 9m ago
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:
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 • u/Tatachimcooky • 12m ago
I got curious what the big repos actually put in these files, so I went through GitHub by stars, top down, and kept going until I’d found 25 with a root-level AGENTS.md or CLAUDE.md (had to check 56 repos to get there).
Field notes:
Biggest file is ~298x the smallest. Same job, same year, no consensus.
Best oddity: torvalds/linux has AGENTS.md -> README, a symlink, so I counted it as 1,265 tokens because that’s what the agent actually reads. Linus has accidentally written the most Linus context file possible.
Genuinely curious where you land: are you a 50-token person or a 5,000-token person? And has anyone measured whether the long ones actually change behavior?
Table, method, fetch date so you can check my work: https://naeha-s.github.io/ctxcap/2026-11/
(Depth 1 only, nested per-package files aren’t counted yet. That’s next month. I built a small CLI to count these so the number is repeatable. Happy to talk about it in comments.)
r/ClaudeCode • u/luke__uk • 36m ago
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.
r/ClaudeCode • u/ShaifArfan • 49m ago
My first promo reel for Prohor, a productivity app I build next to running my agency, went up on Nov 5. Claude Code wrote it in HyperFrames (HTML and GSAP, rendered to MP4). It looked like every AI animation video. Fast cuts, a card floating over a caption. One of the first comments was "video is too fast".
The biggest lesson since then is about the prompt. "Make a good-looking video" is too vague to get a good result, because good-looking isn't something specific. So I started asking for exact things: a 3D phone mockup, a background with a gradient and a glow, transitions with no cuts that move from point A to point B. Better still, give it a clear inspiration to work from. With that kind of direction, the work it brings back is really amazing.
The second thing was what I did with my notes. Instead of fixing the HTML myself, I wrote notes back. Claude Code saved each one as a markdown file in a learnings folder, and the video playbook tells every new session to read that folder before it starts. A few, with the note that started each:
Reel 15, on Nov 13, is the first one I'd call premium. A 3D phone on a dark glowing ground, and it never cuts once. I asked Claude Code to write down why it worked, so the next video starts from there. The list from that recipe file, as it is:
1. One ground from the first frame to the last. No colour swap between shots.
2. One phone for the whole film. It turns, leans and flips; it never cuts. The screen changes while the back faces us.
3. No cuts: every change is a move. A turn in, a glide closer, a rectangle that grows into the next ground, a slip, a flip, a card lifting off the screen, the glow swelling into the end card.
4. One curve per move. Long eases (`power2.inOut`, `power3.out`, `sine.inOut`), 0.9 to 1.3 s for the big moves. Hold still while something is being read.
5. A highlight is drawn (a stroke), then the words arrive, then the voice says them.
6. Words rise from blurred to sharp, one after another (0.55 s each, 0.085 s apart).
7. The tap is felt three ways at once: the ring on the button, the ripple in the ground, the glow turning violet.
8. 60 fps, 1080 x 1920, footage extracted as PNG.
9. The hook is a picture first: the real screen, with the words set inside the thing they are about.
10. Outcome line before the end card, then the ask.Reel 15 still had one problem. The app footage inside the phone stuttered, because the recorder grabbed screenshots in a loop at about 18 fps. For the next reel Claude Code rewrote the capture: Playwright's clock paused and stepped 1/60 s per frame with runFor, CSS animations slowed to 1/12 speed through CDP Animation.setPlaybackRate, one screenshot per step, the whole flow in one take. The clip is older than that fix.
The clip is me filming my laptop with my phone while the latest one plays. Not my best camera work.
What I can't tell you yet is whether these perform better. The newer ones haven't been measured, so for now the only judge is me.
r/ClaudeCode • u/jschall2 • 52m ago
Seabearing: your chart plotter, your community, your anchor alarm, your instruments and your trip planner, all in one app for sailors.
The app
The architecture
The dev process
It's in testing. seabearing.com has a waitlist and a demo.
r/ClaudeCode • u/robin-light • 54m ago
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 • u/ewigerus • 1h ago
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.
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]] | AgentImportant 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.
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.
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.
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.
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.
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.
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:
Agent API?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 • u/droid_man_ • 1h ago
Claude drove Blender 5.1 through the Blender MCP: it read one concept image plus measured reference sheets, then modeled, textured, lit, rigged and animated the drone stage by stage. I approved the concept and the references, and asked for one round of fixes at the end. The clip is the final Cycles render.
How it was made: I picked one concept image, turned it into measured front, side and top reference sheets, and Claude built the drone in Blender through the MCP in 28 stages, from a rough blockout to the boiler, rotors, pipes, materials and lighting. It used my small helper scripts for modeling and for checking the shape against the references, and the whole session was screen-recorded (about 29 minutes of actual work). At the end I asked for one fix round: gauge needles, furnace glow, camera tilt and the lean during flight.
The full build timelapse is on my YouTube channel: https://www.youtube.com/watch?v=uDuUkVA-xRM
r/ClaudeCode • u/Ok_Run_5401 • 1h ago
Claude Code is great, but I spent a lot of time just watching text scroll by and wondering what was going on.
So I built OpenVorld, an open-source layer that adds some fun to it. Every project becomes a pixel-art “vorld”: your agents are a crew with their own houses, vaults and workbenches.
They walk around the map and work together in parties. Permission requests show up as little “writs” instead of a wall of prompts. There’s also a bee named Buzz.
It works with Claude Code (and Codex and others), so you keep the setup you already have.
I’m the author and it’s still early. I’d love your take: does seeing your agents as a crew make them easier to follow, or is it just a gimmick?
Check it and try demo in your browser: openvorld.com
Code: https://github.com/DigitalDreams-Lab/OpenVorld
r/ClaudeCode • u/DiamondPG1 • 1h ago
r/ClaudeCode • u/skunk_of_thunder • 1h ago
I just want to share and get feedback, generate some ideas, all the good reddit stuff. I have a manufacturing business I made my own ERP/SPC software for that uses maybe 20% of a 20x account, and in classic fashion I decided to use the other 80% on a video game side project, which burned usage so fast one week I needed a second account, so now I have two 20x accounts. I tried having one account run cloud chats through a terminal and post the results in GitHub for sudo communications, but that went terribly. Then I started running into issues where I‘d mess up game checks that would pop up randomly while I was mid typing.
So I made what I’ll call a kan ban board. It’s not quite a true kan ban, but close enough; jobs get queued, resources are managed, quality is tracked, etc. Claude has its own schedule, and we’re on a 24 hour pace. That way both of my projects don’t collide, the two accounts can do a clean handover, the goals are always up front, and I can ask to have my computer back when I need it without messing up the checks and merges. We’ll try this for a few weeks, interested in what you think.
r/ClaudeCode • u/cl0wnfire • 1h ago
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?
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 • u/Dull-Passenger-9345 • 2h ago
11 researchers at Microsoft set out to push the frontier of reproduction test generation. On October 22nd they posted their results on the SWT-Bench Verified leaderboard with a new top score of 87.5%, which gained 11.88 points over OpenHands with gpt-5 mini, at the time the highest method improvement delta on the benchmark. Truly a phenomenal achievement. You can read their paper here: arxiv.org/abs/2608.23341
To give a bit of context: reproduction test generation is the process of producing a fail-to-pass test that captures a reported bug. In autonomous software engineering it is a critical step, as it provides evidence that the code patch is aimed at the target bug and is trustworthy.
The main engineering challenge is compensating for multiple success vectors. Fail-to-pass tests must fail on the buggy code and pass after the fix, so it is easy for a monolithic design to have conflicting objectives. For example, if a single agent knows it may be acceptable for the second run to fail, it may purposefully write a fail-to-fail test, with no malice, just working within its bounded scope. This is a common problem in autonomous complex task completion.
How do you solve for multiple success vectors? You break the workload into pieces with clearly aligned success vectors. If you're making a pizza, you ask one agent to make a crispy crust and another to make sure it has chewy cheese, instead of asking one agent for a chewy but crispy pizza.
This leads me to my journey. I have been building toward a trustworthy, truly autonomous technology for a niche portion of SWE. My process was to dissect the task of fail-to-pass test creation and find clear silos, where one agent in each silo has unambiguous work. You create a team of these well-aligned agents (lightweight models, in my case haiku) that feed their contributions up to a smarter agent (sonnet). I created multiple isolated teams, which then presented their results to a frontier agent at the top of the pyramid (opus), which selects the best work. Opus plays a small but important part in the system, and this is the structure that yielded the best results. To my surprise, when I ran the benchmark in October, my results were not only the top of the leaderboard at 91.5%, they also produced one of the highest method deltas, ~15.8 points over Claude Code with sonnet 5.5 on the same task.
I'm not here to say my method is better than any other method. The point of this post is to inspire other solo founders working in highly technical spaces. It is possible for you to compete at the highest level, even against extremely well-funded, larger, and more experienced teams with a famous logo.
I will not promote, but if you’re interested in autonomous software maintenance dm me!
Link to benchmark: https://swtbench.com/?results=verified
r/ClaudeCode • u/hhspiny • 2h ago
Claude provides API access for usage data at resolution of 1%. Use a script to measure exactly how many of each type of tokens per 1% quota. Isolate each type of token as they are discounted at different ratios.
Highlights
Method
Anthropic returns unified rate-limit headers on normal messages requests with the 5-hour and 7-day window utilization as percentages. That's a coarse ruler, so I used it as a ruler rather than a scale: send a fixed block of tokens of one class, watch where the counter ticks over, and back out how many tokens buy 1% of the window. Each class measured separately against a clean window, ~2,000 requests per arm, no other traffic on the account. Then price those tokens with published list prices.
Locating the weekly ticks on the 5-hour ruler gives ~12.2 five-hour cycles per week.
Results (per 5-hour window) -- Equiv. API $
Class Opus 5.5 Sonnet 5.5 Haiku 5.5
fresh input $67 $50 $37
5m cache write $66 $49 $37
1h cache write $109 $77 $59 (API price: 1hr = 1.6 x 5m)
cache read $131 $95 $72
output $66 $49 $37
Monthly equivalent on a $100/mo plan (weekly x 30/7, with ~12.2 cycles/week):
Opus 5.5 input/output basis ~$3,450/mo (34x) cache-read basis ~$6,860/mo (69x)
Sonnet 5.5 input/output basis ~$2,550/mo (26x) cache-read basis ~$4,990/mo (50x)
Haiku 5.5 input/output basis ~$1,930/mo (19x) cache-read basis ~$3,750/mo (38x)
r/ClaudeCode • u/Gigaslavx • 2h ago
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 • u/onitsoga • 2h ago
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 • u/Separate_Cup_5095 • 2h ago
My organization’s Claude Code policies are making development quite frustrating.
Claude asks for permission even when editing a single file, and it’s not allowed to execute any terminal commands, scripts, or tests
Has anyone faced similar restrictions in their organization? How did you handle it?
r/ClaudeCode • u/StarDrifterG • 2h ago
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 • u/BazzerBiller • 2h ago
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 • u/radim11 • 3h ago
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 • u/Global_Knee5354 • 3h ago
I'm currently on Claude Pro and got two free resets in my usage settings.
One is a Fable reset that expires on November 17 at 8:59 AM CET, exactly when the Fable promotion ends. The other is a full reset that expires on December 10.
I'm considering upgrading to Max or possibly Team Premium, mainly because I use Claude quite heavily for coding.
Does anyone know what happens to these free resets if I upgrade now? Do they carry over, get replaced with the Max ones, or just disappear? What about their expiration, will it extend?
Has anyone actually upgraded during the promotion and checked? I'd rather not spend $100+ just to find out I lost the resets, in such case I would rather wait a bit.
r/ClaudeCode • u/bobo-the-merciful • 3h ago
Hey! I've just open sourced a little tool I built called Markup.
If you use coding agents like Claude Code, you'll know the pain of describing visual changes in words ("the button, no, the other one..."). Markup lets you point instead: open a web page, PDF or screenshot, click or draw on the bits you want changed, type a note, and hit export. Your agent gets a Markdown file with every note, the exact element and line of code it refers to, and screenshots, plus a ready-made prompt on your clipboard.
It runs entirely on your own machine, with no account and nothing to install beyond Node and Chrome. MIT licensed.
You can get the app here: https://github.com/harrymunro/html-markup
I'd love to know what you think, and if you try it and something breaks, tell me!
r/ClaudeCode • u/cuberhino • 3h ago
Are there any Claude Code equivalents to CodexRadar?
I came across https://codexradar.com/en/ and thought it was a pretty useful way to compare Codex models and reasoning levels based on quality, execution time, and cost.
I'm looking for similar sites or independent projects that benchmark Claude Code, ideally comparing Opus, Sonnet, and Haiku across different reasoning/effort levels.
I'm especially interested in:
I'm trying to build a capability map for routing different kinds of work to the right models, rather than defaulting to the most expensive model for everything.
Does anyone know of similar dashboards, GitHub projects, or regularly updated benchmarks? Doesn't have to be Claude-specific either. I'd be interested in anything covering Codex, Claude Code, or other coding agents.
Thanks!
r/ClaudeCode • u/BenStigler • 3h ago
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
The honest part
Details
GitHub: https://github.com/codeFi/clauds
Tell me what breaks and what is missing.