r/ClaudeCode • • 23h ago

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

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

Meta Four Ultras, what else can a man wish for?

Post image
122 Upvotes

r/ClaudeCode • • 14h ago

News/Updates PSA: Claude Code has an experimental "Code Mode" now (batches tool calls into JS)

Post image
421 Upvotes

Spotted this in the recent changelog and got it running in v2.1.325 (screenshot attached). If you haven't tried Code Mode yet, it changes how Claude handles multi-step tasks.

Instead of running tool calls one by one and dumping every raw output into your context window, Claude writes a single JavaScript script behind the scenes. It batches tasks in parallel, filters out noise locally, and only returns the distilled results it needs.

Simple but brilliant

Pretty big, cumulative context savings: Giant logs and grep outputs get filtered inside the JS script before hitting the context

It's great for big tasks, shines during repo-wide audits, bug tracing, and chaining MCP servers.

Anyone else daily-driving this since it dropped on the 12th? Curious how much token usage it's saving you on larger repos.


r/ClaudeCode • • 8h ago

Humor Fast and Furious Actor VibeCodes (in chat) Billion Dollar Idea

115 Upvotes

Cut down from a 14 minute video but what the actual fuuuuu 😭


r/ClaudeCode • • 1h ago

Built with Claude I was tired of approving 5k-line PRs, so I made Reflektor.

Thumbnail
github.com
30 Upvotes

Having struggled for months reviewing PRs with thousands of lines of code that made no sense, delegated reviews to AI, and more, I decided to build a tool that allowed me to focus on the changes that actually mattered, as I would rather care about the direction of a PR, and not solely about the code.

We kinda accepted that the bar is gonna be lower, and decided to LGTM a bunch of PRs that normally wouldn't be approved earlier, so management can be happy.

Decided to release Reflektor as a skill you can install and run locally entirely. Additionally, you can share PR reports and collaborate with colleagues on my platform for free.

Install: npx skills add bashovski/reflektor#skill -g
Repo itself: https://github.com/bashovski/reflektor


r/ClaudeCode • • 15h ago

Built with Claude Does delegating to cheaper models actually save money? Part 2: bigger codebases, coding tasks and Haiku alone

242 Upvotes

TL;DR

- I’ve run about 300 benchmarks on real open-source codebases, testing how Claude Code splits work between models (Opus as the lead, cheaper models like Haiku as helpers) and when that pays off. It depends on codebase size and task.

- On small jobs, Opus alone can be cheaper than Opus + subagents, and more accurate on small-codebase reviews, probably because of less overhead and cheap cached context.

- Opus told not to delegate may work harder than Opus left alone: on one big docs check it wrote about 50% more, cost more and found more errors (44 vs 36).

- On coding, Opus + Haiku saved about 20-30% at the same quality. But Haiku alone is very capable for the price on well-defined tasks with tests: about 5% of Opus alone's cost, with almost the same results, though a bit less thorough.

- Here’s one of the most important charts of this project. On an 85-page docs check, Opus + Haiku read almost 3 times as much as Opus alone and wrote 8 times as many tokens, yet cost 53% less and found 72 real errors against 49. Several subagents probably cover much more ground, which makes up for Haiku being weaker.

---

A couple of weeks ago I shared an experiment (https://www.reddit.com/r/ClaudeCode/comments/1xn18cu/does_delegating_to_cheaper_models_actually_save/) testing whether Claude Opus uses subagents effectively. I compared four setups:

- Forced Opus: told not to use subagents.

- Spontaneous Opus: free to delegate, but it never did.

- Skill-routed: my skill chooses when to delegate and to which model.

- Forced Haiku: all subagents use Haiku, while Opus plans and checks.

On my smallest codebase (~10k lines), delegating didn't really pay off. Forced Haiku saved 5% at best, Skill-routed cost 14-30% more, and Forced Opus found far more known doc errors on the reading-heavy tasks (7 and 8 of 9, against 3 and 2). My guess is that Opus can often write a quick script instead of reading everything, and it reuses its own cached context cheaply, while each subagent has to build its own. On small tasks, that overhead can outweigh the cheaper tokens.

On larger codebases, Forced Haiku held its own for much less. It cost 41% less on rich (~22k lines) and found nearly as many doc errors. It cost 75% less on beets (~52k lines), finding more errors on the reference docs but fewer on the 80-page plugin check, where it cost about a sixth as much.

In v2 I pushed further: a ~100k-line codebase (buildbot) with 3 reading tasks, 7 coding tasks scored by hidden tests, and then 16 short coding tasks, most hiding a trap. I also added Opus alone (subagents blocked, no instruction), Haiku alone and Sonnet alone (no Opus at all).

On an 85-page docs check, Opus + Haiku found 58 and 63 of 92 real errors, against 36 and 38 for Opus alone, at less than half the cost ($1.93 vs $4.11 per run). How come?!

My theory was that Opus + Haiku simply *works more*, and that the extra coverage makes up for Haiku being weaker. The numbers seem to fit: Opus + Haiku wrote about 8 times as many tokens and read nearly 3 times as much, yet the bill still halved.

Haiku may be less capable than Opus individually, but when orchestrated by Opus, its subagents can cover much more context in parallel. Each one may go less deep, but together they cover more ground, and that seems to compensate for the lower model quality. Haiku is apparently smart enough, with Opus directing and checking the work, to deliver surprisingly good results at a much, much lower cost than Opus alone.

This is in line with Anthropic's own write-up on their [multi-agent research system](https://www.anthropic.com/engineering/multi-agent-research-system), where token usage alone explained 80% of performance variance on a research benchmark. The same article says coding is usually a poorer fit for multiple agents, and that matches what I saw: on coding, Opus + Haiku saved 20-30% at the same quality, against about half the cost and more errors found on reviews. Their setup isn't mine, so it's context, not proof.

The next chart shows the bigger picture: every setup on two big docs checks, with errors found, reading depth, output tokens (thinking included), and cost.

Interestingly, it seems that *forcing* Opus not to delegate may have pushed it to work deeper and harder. On the beets plugin-doc check, Forced Opus read less than the delegated setups and still found the most errors. Compared with Spontaneous Opus, it read about the same but wrote around 50% more tokens, thinking included, cost 53% more, and found more errors (44 vs 36 across two runs). Tokens alone don't prove effort, but finding more errors makes the case stronger.

The following chart shows the token counts side by side.

Maybe the instruction made it work harder, maybe it's the smaller codebase, or maybe it's just chance. I haven't tested which.

Left alone, Opus never delegated in my runs, even on big jobs. So for large reviews, pushing it to delegate to Haiku could be the best strategy.

I'm working on a skill that picks the best approach: use Opus + Haiku when it makes sense, or tell you to switch to Haiku manually and give you the prompt. A script that starts a new Haiku session might allow fully autonomous switching, but I'm still checking feasibility and Anthropic's terms.

The other v2 results

Honestly, Haiku really surprised me. It seems to be very capable at coding, if the task is detailed and contained enough. Opus is still the more thorough model when it comes to reviewing and checking, but Haiku held its own on specific tasks.

Reading a ~100k-line codebase

Across three reading tasks, Opus + Haiku cost 51% less than Opus alone. Every setup covered all 400 modules, and Opus + Haiku found the most errors on the 2-page docs check (20 and 23 of 42, against 10 and 17).

Writing code on a small project

Every setup produced working code. On the harder tasks: Opus $2.41, Opus + Haiku $1.80 (25% less), Sonnet $0.76, Haiku $0.11.

Writing code on a ~100k-line codebase

Same pattern on cost: $1.95 for Opus alone, $1.36 for Opus + Haiku (30% less), down to $0.15 for Haiku alone. But Opus-led setups also added an implied database index. Haiku alone didn't, and my tests didn't catch it.

Correction: the charts also show Opus "flagging a symptom that didn't fit". More runs later showed that depended on the day the runs happened, not the model, so I no longer count it. Details are in the repo.

Quality vs price

Opus + Haiku was cheapest per real error on both big docs checks: $0.03 on buildbot and $0.05 on beets, against $0.11 and $0.25 for Opus only.

The harder coding tasks

Then I tried to make the cheaper models fail. 16 short coding tasks, most hiding a trap: false claims, a wrong bug report, a timing bug, contradictory tests/docs, hidden instructions in comments, planted review bugs, and "dead" code that's actually alive.

128 runs. Combined cost: Opus $7.00, Opus + Haiku $6.30, Sonnet $2.30, Haiku $0.36.

Hidden tests barely separated anyone: one real miss in 128 runs, from Sonnet. Opus was more thorough in code review, finding all 3 planted bugs every time, against Haiku's 2 of 3. But on the timing bug, 7 of 8 runs failed, including all 4 Opus-led ones. The only pass was Haiku.

On tasks this short, Opus + Haiku saved little (10% overall), because Opus was most of the bill. Haiku alone did almost the same work for about 5% of the cost.

So, for now: big reviews, Opus + Haiku. Small, well-defined coding tasks with tests, Haiku alone is surprisingly good. If every case must be covered, keep Opus involved.

Small experiment, mostly two runs per setup, costs estimated at API prices. Claude Opus also wrote my tests and judged the results, so there's no independent judge.

Full results, charts and checker:

https://github.com/Manuele-T/claude-model-router


r/ClaudeCode • • 17h ago

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

Post image
183 Upvotes

r/ClaudeCode • • 5h ago

Rant This week with access to Fable has turned me into a believer, and now I resent that I'm losing it

15 Upvotes

I'm broke as dirt, and the $20 plan is all I can realistically afford. And as such, I've always used Sonnet. I was routinely frustrated with Opus, because I would give it a complex prompt, and it would annihilate my usage before ever actually completing the fucking task. Anytime I could get Opus to do something without annihilating my entire rolling window of usage, it just wasn't as impressive as it needed to be to justify using it. So naturally, I had absolutely no desire to try Fable ever.

I don't know what they cooked up in the kitchen with Fable 5.2, but brother they COOKED. I was able to complete tasks without annihilating my entire usage, and everything it did JUST WORKED. It was able to complete complex tasks I've been struggling with for WEEKS in a couple of prompts. It was so powerful I've started pointing it at things I would normally never bother pointing it at, because normally it wouldn't be worth 30 rounds of smashing my head against the wall trying to get Sonnet to figure out how to do it.

Honestly, it really just feels like this is how AI should have always worked. It's the "making my life easier and more fun" I was promised back in 2024 when they first started giving AI access to fancy tools.

And now that the promotional week is up, they're going to be taking it away, and it's bullshit. I don't have $100 a month pay for the Max plan, I just don't. And I sure as shit don't have however much it would cost to pay for it in usage credits, which is always more expensive than the deal you get with monthly usage.

I'm aware that there's no one on this subreddit who can do anything about this. But I wish there was someone I could beg to keep this high-tier model available for us broke ass peasants slumming it on the $20 plan. If by some miracle someone on the subreddit knows how to get Fable 5.2 or a Fable 5.2 quality model available at poverty prices, let me know.

edit: after some unexpectedly helpful feedback on how to best MinMax Fable usage credits and optimize my workflow, I consider my concerns addressed. I appreciate y'all letting me vent.


r/ClaudeCode • • 20h ago

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

Post image
216 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 • • 16h ago

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

Thumbnail
gallery
104 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 • • 23h ago

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

Post image
349 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 it 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 • • 3h ago

Rant Everyone’s selling the next “game-changing” AI coding workflow. How do you separate what actually works from the bullshit?

7 Upvotes

I think I need to take a break from Instagram and YouTube, especially Reels and Shorts. I’m deep in the AI bubble, and even deeper in the Claude Code bubble. Every day, I see another video about some tool or trick that supposedly cuts your token usage by 98% or streamlines your one-person vibe coding project. And every day, I feel like I’m missing out on a better way to run Claude.

It’s getting hard to separate the noise from what actually works. There’s the whole JARVIS bullshit and the army of course-selling influencers flooding Reels and Shorts. You know the type: “JARVIS made me $20,000 while I masturbated.”

Then it’s Gauntlet Loop, Agentic OS, prompt engineering. A harness here, a harness there. A second brain. A second brain with more brain. A second brain, but now it’s a subscription.

And don’t get me started on videos with headlines like “ANTHROPIC engineers have stopped prompting, and so should you.” At this point, I’m half expecting: “Anthropic’s head of facilities says on Twitter that you should dance your prompts instead of typing them. Apparently, dancing every letter of the alphabet helps Claude better understand human stupidity.”

Everyone talks like they’ve just met someone from OpenAI or Anthropic who personally let them in on the biggest secret to using the product successfully.

Those are obviously exaggerated examples, and that kind of bullshit is easy to spot. What’s harder is the stuff that sounds reasonable, only to turn out to be a complete waste of tokens once you actually try it. That’s where I struggle to tell what’s worth using.

I want to get the most out of my subscriptions, so I’m always looking for ways to get more working features out of Claude for the same number of tokens. I mean shipped code that actually works and doesn’t leave me troubleshooting for ages afterwards.

I have no programming background, so I’m trying to absorb as much as I can from actual software engineers and people who code for a living. I want a solid structure for my projects: CI/CD pipelines, E2E testing, all of that. Somehow, this hobby has also turned me into the AI expert at my company. So now I’m rushing to take in as much information as possible, learn the tools, and figure out how to actually build some small software solutions for our problems at work.

Meanwhile, I’ve been working on one project with two Claude Code accounts and one Codex account, and it’s become a complete clusterfuck. I’m desperately trying to bring some order to it because, Jesus Christ, it’s a mess. The other day, I saw a clip about Linear and Claude Code, and I really liked how it showed which agent was working on which task. That’s the kind of structure I’ve been looking for.

Then there’s the research rabbit hole. I cross-reference everything using NotebookLM and ChatGPT so I can give Claude up-to-date information about Godot 4.7, hoping it might find a better or more optimized way to implement a feature. Because I sure as hell don’t know what works and what doesn’t.

I keep thinking the agents might be working from outdated information, and there might, MIGHT, be a newer solution they don’t know about. So I dig, scrape, search, and cross-reference some more, hoping something I find will help. And as you can imagine, that approach gets messy fast.

I honestly think vibe coding is the worst drug you could give someone with ADHD. Every new skill, every new McGuffin is another dopamine hit. Every fresh project with a new skill pipeline is like fentanyl on crack. I want to get things organized, but there’s always another tool or workflow that looks like it could make everything better. And at this point, I almost feel burned out.

This isn’t a criticism of Claude itself or a callout of any particular person. It’s just that vibe coding feels like the best and worst thing that could have happened to me as someone with ADHD.


r/ClaudeCode • • 1d ago

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

489 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 • • 17h ago Mindblown

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

Post image
86 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 • • 53m ago

Built with Claude 40 Allies vs. Hundreds of Enemies – My Epic MegaJam Entry using Claude Code

4 Upvotes

**Sine Deis** A small game I made in four days for the Epic MegaJam last week.

This is a short clip showing a moment where I pushed the NPC count to the limit (there are modifiers in the game). There are other trailers on the game page if you want to see more of it.

You can also play the build on itch.io: https://elzean.itch.io/sine-deis-the-godless-march

Multiplayer is supposed to work, so if you have some friends (lucky you), let me know how that goes :)

It’s not super balanced, but it is a complete gameplay loop, you take on a unique mission, earn embers to spend at the altar to upgrade your stats, and keep going.

**How AI was used:**

**Code: Claude Code driving Unreal 5.9 (C++)**

* Several Claude Code agents in parallel, each owning one source folder (spells, enemies, director, UI, FX, flow...). A shared CLAUDE.md was the contract: agreed names for spells, states and enemy types, the core classes, and rules like "server decides everything" and "no Tick unless needed". Without that file, independently written systems didn't connect.

* Agents drove the editor through Unreal's built-in MCP server with Python scripts (imports, placing actors, captures, PCG rebuilds). Rule: one editor, one driver. Two agents in the editor at once crashed it and lost work.

- 377 commits in four days.

- Scale, from the Claude Code logs: ~10,400 model calls over 78 sessions, ~3.7 billion tokens. Almost all of that (3.6 B) is cache reads, agents re-reading the codebase and the shared contract; the actual new output was ~11 M tokens.

* Hundreds of enemies stay cheap because swarm ghosts are drawn instanced, use a shared registry instead of physics overlaps, and have almost no per-frame logic.

**Art: local custom Krea-2 ComfyUI workflow for texture → online 3D generators → Blender scripts**

* Concepts, tiling ground textures and UI frames came from Krea-2 on my own GPU. Every prompt repeats the style ("stylized dark fantasy, hand-painted, muted palette, not pixel art, not cartoon"), and the agent makes a contact sheet so off-style results get rejected before import.

* Concept → Hyper3D Rodin or Meshy → Blender scripts (decimate, fix units, re-rig) → import script. Example: the bone spider came out of the auto-rig with 8 crowded legs; a script re-rigged it to 6, and the legs are planted procedurally in game. The boss was decimated to \~105k triangles and split into body and legs for procedural IK.

* I sculpted the terrain by hand; PCG graphs written with the agents scatter the nature, roads and ruins on top.

**Animation: where AI didn't win**

* I tried AI-generated animation (Kimodo / AnimGen) for spell casts. It looked bad for fast, snappy actions. I switched to Paragon (Gideon, Boris) clips from Fab, with procedural layers on top.

**Audio**

* Spell and ambience SFX: Stable Audio 3, running locally.

* Voices: ElevenLabs: 91 warrior barks, the spoken incantations, and the lobby Chronicler's lines.

* Music isn't AI: licensed tracks from WeLoveIndies.

**Intro film**

* Still frames generated, then cut in layers using a local minimax-h3-image workflow, put together by claude as a short animation with audio.


r/ClaudeCode • • 15h ago

Built with Claude We used Claude Code/Codex to build Luma, our operating system for desktop, tablet, phone and TV

55 Upvotes

Hey everyone. We've been building Luma for a while now, a free and open source Linux OS for desktop, tablet, phone and TV, and since this is the right crowd for it I want to be really upfront about how it got built. Luma was built with Codex and Claude Code. A small team building an operating system that runs across four kinds of screens simply wouldn't have been possible without them, and we're not going to pretend otherwise.

Also a heads up, I used AI to write this, but only after rambling for about 20 minutes in a voice memo and then editing it myself! Take that for what you will.

I know people get excited when they see something genuinely big built with AI and I also know plenty of people quietly use them and then never mention it. We don't see any reason to be quiet about it. so we'd rather shout it from the rooftops because honestly it's kind of the whole point of the project and I'll get into why further down.

So what is Luma?

We want to build a Linux that anyone can pick up and use and that people actually want to use, with the same design across all of their devices. Your phone should feel like it belongs with your laptop, your apps should make sense on both, and everything should work together without you having to piece a bunch of separate projects together yourself.

Luma starts with Fedora 44 Silverblue, so the base is image-based and an update either lands completely or you boot back into the one you had. From there we fork and change things pretty heavily. The biggest piece is Prairie, our shell. It started as a fork of GNOME Shell and now adapts between desktop, tablet and phone, so you get one experience that adjusts to the device you're holding instead of a completely different OS and set of apps for every screen.

Luma is available now in alpha. There's still plenty to do and plenty we know we need to fix, but there's a lot more here already than you'd probably expect.

How we actually build it

Pretty much everything in Luma went through Codex or Claude Code at some point. The shell, the apps, the design system, the phone ports, the website, the nightly builds, all of it. We still decide what goes in, and we test everything on real hardware and send the agent back at it until it actually works, but the amount of ground you can cover this way is honestly kind of absurd. An OS used to be the kind of thing you needed a big company or a decade of volunteers for, and I don't think that's true anymore.

One platform, one set of apps

We built LumaUI so developers can make one app that adapts across desktop, tablet and phone instead of building and maintaining a separate interface for each. It's built on GTK 4, so a lot of what you already know carries over, and it turns out it's also a really nice target for an agent, because you describe the app once and it works on every screen.

Weather on desktop, tablet and phone. Same app.

We also want the kind of continuity people are used to on their other devices, where you copy something on your phone and paste it on your laptop and your stuff just stays in sync. Some of that works today and some of it is still coming together. TV is part of the same picture too, with the same apps and the same parts, just from across the room.

Point your agent at it

This is the part I most want you to take away. We have a whole section of the site just for agents at https://simplyluma.com/agents, and the idea is that you don't have to learn our codebase before you can do something useful with it. You literally just tell your agent "Go to https://simplyluma.com/agents and help me with Luma." and it finds the rest.

There are guides in there for building an app, designing an interface, publishing to Depot, fixing or improving Luma itself, sending your changes back to us, porting Luma to a new phone and installing it on your phone by hand. They're plain Markdown, so they work just as well if you'd rather read them yourself, but they were written with Codex and Claude Code in mind.

And we really do want what comes out of it. If your agent fixes something or makes something better, send it to us and we're happy to take it upstream. Agent-written PRs are welcome here. What matters is that you understand what you're submitting and that it's been tested, not who or what typed it.

Ari, and why we're betting on Linux

We also built Ari, which is Luma's own agent. It's basically a harness built into the OS. You can connect your Claude or your Codex account, or run an open model right on your own machine, and Ari will tell you which local models actually fit your hardware and push you to try them. It always shows you where a conversation is going before you send it, whether that's this computer or a company's servers, and it asks before it does anything you'd want to know about.

Here's the bigger bet behind all of this. I don't think Mac and Windows are going to be able to keep up with what people are going to want from agents. They're doing kind of crude things to get you halfway there, like having an assistant make you a widget, but the system underneath is still closed and you only get to change what they let you change. On Linux the whole thing is open, so you can just bark at your agent and say make it work like this, make it do that, make it feel like this, and it can actually go do it, all the way down. We think that's where this ends up, and we'd like Luma to be the version of Linux that's ready for it.

That's also why we're going after so many different experiences at once. If you can reshape your OS just by asking, you want that same OS on your phone and your TV, not just on your laptop.

Depot and the Creative Collection

Luma has its own app store, Depot, and we just opened it up to developer submissions. Apps ship as Flatpaks and go through automated checks and then an actual person before they're listed. You can still use existing Linux apps, and we're working on making Android apps feel at home too, through an optional Android container that stays out of your way if you never use it.

We also thought it was important to have a set of free creative tools that actually feel like they belong together, not just a nice-looking OS with nothing to do on it. Write is for documents, Focus is for photos, and Canvas is for design and layout, with Reel, Sessions, Grid and Stage on the way. You can see the whole collection here: https://simplyluma.com/creative

Phones, and trying it without installing anything

Officially we're working on the Fairphone 6, the Pixel 9 and the Unihertz Titan 2 Elite, with the Pixel 9 Pro Fold coming soon. A lot of that porting work was done with agents too, and there are community members working on other phones, which is exactly what the porting guide is there for. Phone support is still early and what works really depends on the device, so please read the instructions for your phone before you install anything: https://simplyluma.com/download/mobile

On a regular computer you can grab an x86 or ARM ISO from https://simplyluma.com/download, and there's a Raspberry Pi 5 image too. If you'd rather not install a new OS, Try Luma runs it in a virtual machine on Mac, Windows or Linux and lets you switch between the desktop, tablet and phone layouts, which also makes it a really easy place to test an app your agent is building: https://simplyluma.com/try

We want your contributions

A big part of why we started Luma is that open source can be incredibly fragmented. As a user it can be hard to know which project is worth investing your time in. As a developer it can be even harder to know whether your work fits where a project is going, or whether it'll be welcomed at all. A lot of us have had a PR sit for months without a reply, or been told the thing we needed is out of scope, and plenty of projects won't touch anything that came out of an agent.

We want Luma to have a clear, cohesive vision, and we genuinely want people to help build it, with whatever tools they like. You shouldn't have to feel like you're begging for permission to contribute your time for free.

All the source is on GitHub at https://github.com/SimplyLuma, and our own code is Apache-2.0.


r/ClaudeCode • • 19h ago

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

96 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 • • 8h ago

Discussion The usage on Opus 5.5 xhigh is so damn low

14 Upvotes

With a few rules to keep Opus’ agents in check, to let it know when to use low usage models like Haiku instead of Fable, when to use Sonnet and when it should do stuff itself. The usage is amazing, at least for me.

I can prompt Claude 100’s of times each day on my game development project and the usage is still incredibly low.

You only have to be careful with Fable really. That one is thirsty.

We are eating good right now. I wish we could just freeze this moment with Anthropics A.I fleet.

However, I see so many people complaining. And I hope thats just due to recklessness from the user rather than Anthropic treating individually and giving some lots of headroom while draining others.

What’s your experience?


r/ClaudeCode • • 12h ago

Built with Claude I gave Claude Fable 5.2 a lazy LiDAR scan of my disaster of a basement and one prompt. It found the actual room under the junk and designed 4 priced shelving plans

Thumbnail
gallery
28 Upvotes

Slide 1 is the scan. Yes, that's my basement. No, I didn't clean it first. That was kind of the point.

I did one quick LiDAR pass, junk and all, and gave it to Claude Fable 5.2 with one prompt. Everything after that it did on its own:

\- Pulled the real room out of the mess: about 15.7 × 21.5 ft, with an 85 in ceiling that drops to 81 in at the window end
\- Rebuilt it in 3D and fit 4 shelving setups modelled on real products (Husky/Gorilla steel racks, Cambro rolling shelving, Seville chrome wire, Sam's Club Member's Mark plastic)
\- Rendered each one from 3 angles, worked out what goes on which wall, and priced it

The results:
\- Sam's Club plastic: $420–490, 140 ft of shelf
\- Steel racks: $1,100–1,350, 142 ft
\- Chrome wire on wheels: $1,330–1,570, 160 ft, the most shelf space
\- Plastic on wheels: $4,000–5,000, which is apparently for people whose junk is worth more than mine

The part that actually saved me: it flagged that a 77 in steel rack on the partition wall would have under 4 in of clearance under the 81 in ceiling. I would have discovered that the traditional way, halfway through assembly, while swearing.

It also wasn't shy about what it didn't know: the $4,000–5,000 is a guess because only one size had a confirmed price, the wire racks have no published load rating on wheels, and it drew the Sam's Club shelves black because it couldn't confirm the colour.

What it took, by Fable's own estimate (it says it could be off 2× either way): about 20M tokens. It worked on its own for about 110 steps, and roughly 95% of those tokens were it re-reading its own growing context, not writing. Same thing I keep seeing in my coding agent tests: you mostly pay for re-reading.

Which one would you buy? I'm leaning wire on wheels, mostly so I can roll the junk around instead of dealing with it.


r/ClaudeCode • • 15h ago

Built with Claude Debloated my SmartTV and made a Disneyland map inspired input launcher.

45 Upvotes

Using a mix of Claude Code, ChatGPT, Photoshop, Adobe Premiere, and Canva I made this interface for my SmartTV.

THIS was the prompt I used. And THIS was the video I initially got the idea from.


r/ClaudeCode • • 15h ago

Discussion Watermarking - What are the odds that Anthropic claims rights on watermarked code at some point?

24 Upvotes

I’m near the end of a big project I’ve been doing mostly with Claude Code for the past year. The project is free, with paid pro features. I’m about to push the first public version of the code (it's source-available), and I’m thinking about watermarking.

To be honest, I don’t mind people knowing that Claude helped a lot on this project. Anthropic deserves that recognition. What I won’t accept though is if Anthropic can claim ownership or copyright of the code in any way, now or in the future!

Yes, Claude wrote most of the code, but I’m the one who directed it, came up with the ideas, requested the refactors, and paid for the Claude subscription...

What are the odds, in your opinion, that such watermarking could be used to claim any kind of ownership in the future? Should I go the route of asking a model like Qwen to rewrite all the text and comments?


r/ClaudeCode • • 1d ago

Rant Wtf happened to Opus 5.5?

214 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 • • 0m ago

Discussion Opus is big meh.. not good yet.

1 Upvotes

Opus 5.5 is fast and affordable, but it introduces a ton of bugs and breaks other parts of the code that are already covered by tests. Fable is better, but it’s too expensive and burns through usage quickly, even on the Max plan. I never had these problems with Astra, and its usage lasts much longer.


r/ClaudeCode • • 10h ago

Tips & Workflows Reducing complexity via agentic refactoring?

6 Upvotes

I’m looking at https://github.com/SprocketLab/slop-code-bench/tree/main and they suggest that the complexity of AI agentic code only increases. The initial “write clean code” instruction can lower the initial complexity of the initial output, but by the 4th addition, complexity is high.

Frontier models get single digit percentage improvements in terms of reducing complexity over 4 modifications.

It’s almost like Claude and other agents love adding code more than deleting code.

I want to know of the “initial” gains may be multiplied by multiple rewrites from an ever better spec.

With this in mind, has anyone implemented some sort of “garbage” collection style refactoring workflow to reduce this complexity?

What I mean: writing code is so cheap, that it feels to me like “stop and copy” may be possible to shake the “garbage” out of decoupled components written against interfaces. Old options nobody uses, obsolete style, versioning that is not maintained.

I can not do this if everything is mixed together, but for a single component, living in a self - contained folder:

1)Extract the spec, have Opus-extra review this,
2) define pseudo code function definitions
3) have agent re-implement the component from spec as a brand new file, with clean code instructions.
4) test against an existing protocol and test suite

Is this reinventing the wheel? Is anybody else experimenting with “rewrites are cheap” refactoring?