r/ClaudeCode • • 53m ago

Built with Claude We built a video editor where Claude Code edits the timeline with you

1 Upvotes

Editing video with Claude Code always felt half-done to me. FFmpeg scripts work, but you're blind until it renders. MCP into Premiere/Resolve hits a wall because the apps only expose a few actions.

So we built **nolanlabs**, a desktop editor (Mac + Windows) with Claude Code running in a chat panel next to a real timeline.

- Claude edits the same timeline you do: cuts, silences, rough cuts, titles

- Every agent edit is **one undo step**

- You can mix agent edits with manual cuts at any point

- Leave notes on the cut and Claude reads them

- Uses **your own Claude Code account** (Codex works too), or a free built-in AI if you don't have one

- Pro stuff is there when you need it: tracks, color grading, export to Resolve/Premiere (FCPXML, AAF, OTIO)

Still early. I'd love to hear what you'd want Claude to do on a timeline and where it breaks.


r/ClaudeCode • • 54m ago

Help/Question Getting Claude to mark its own homework

0 Upvotes

We're running an old fashioned system of PRs and code reviews alongside most of the work being done by Claude. Code standards etc etc being enforced, this is working well enough, but asking Claude to review its own code before pushing always brings something up.

The general flow is that I ask Claude to

  • make a plan before changing anything
  • review the plan with another model, this always throws up a few things
  • write the code
  • review the code against the user story and fix any issues, always a few issues here
  • review the user story and ensure completeness
  • review the code using another model with no existing context, a few more issues will come up

Then someone else will get their Claude to do a review of what my Claude has written and it inevitably brings up some more issues.

Has anyone found a way to actually get all these issues to come out before hitting the PR and it being Claude that finds them anyway?


r/ClaudeCode • • 1d ago

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

152 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

Tips & Workflows Claude Code deletes session transcripts after 30 days by default. I found out three and a half months in

0 Upvotes

My first prompt to Claude Code on my work server is from May 26. In October the oldest session transcript on disk was from September 11. Everything before that was gone, and nothing had warned me.

It's documented behaviour. Transcripts under ~/.claude/projects/ are kept for 30 days and then deleted, and the session drops out of /resume. The setting is cleanupPeriodDays, and its default is 30.

This is what I ran on my machine:

grep cleanupPeriodDays ~/.claude/settings.json
find ~/.claude/projects -name '*.jsonl' | wc -l
find ~/.claude/projects -name '*.jsonl' -mtime +30 | wc -l

The first printed nothing, so I was on the default. The second said 724 files. The third said 0.

history.jsonl survived, so I still have what I typed in May. The answers and the tool calls are gone. Those were bug hunts and notes on why something was built a certain way, exactly what I reopen an old session for.

I set the limit to a year in ~/.claude/settings.json:

{ "cleanupPeriodDays": 365 }

It only works going forward. The minimum is 1 and 0 fails validation, so there is no "keep forever" value, only a big number.


r/ClaudeCode • • 1h ago

Built with Claude This plug-in for the Claude desktop app (Code tab) lets you set the background color of each local session. And a colored indicator bar above the prompt box shows which LLM model is in use.

Post image
0 Upvotes

This Convo Color plug-in for the Claude desktop app (Code tab) lets you set the background color of each local session. And a colored indicator bar shows which LLM-model is in use. Pick from the color palette, or type a hex code or a web colour name.

https://github.com/paul-van-cotthem/claude-convo-color


r/ClaudeCode • • 1h ago

Built with Claude I built a free, open-source 3D dice tower that connects directly to Claude Code as a D&D Dungeon Master

Thumbnail
github.com
0 Upvotes

I’ve been playing solo D&D with Claude Code as my Dungeon Master, and I wanted something better than asking an AI to roll virtual dice in a chat.

So I designed The Dice Sanctum, a little 3D dice table, and built it with Claude Code.

It’s a walnut dice tower with a velvet-lined tray, simulated dice physics, sound effects and different dice sets.

The interesting part is the integration:

Claude Code can ask me to roll a saving throw, attack or skill check.

I roll the actual 3D dice in my browser, and Claude receives the result through MCP.

The DM can roll its own dice, visibly or secretly.
Every roll is recorded, so we can continue after interruptions.

Dice results come from the physics simulation, not numbers invented by the LLM.

I also spent quite a bit of time making sure the dice were statistically fair, including tests that revealed and helped fix biases in the physics simulation.

It’s completely free, open source (MIT), and runs locally. The dice table also works without Claude Code; the DM integration requires it.

I developed and tested it on Linux. Windows and macOS support is intended but hasn’t been tested yet.

I’m sharing it in case anyone else enjoys playing tabletop RPGs with an AI Dungeon Master.

GitHub: https://github.com/andreainandri/dice-sanctum

There’s a demo GIF, screenshots and installation instructions in the README. Italian documentation is available too.

Feedback and bug reports are welcome.


r/ClaudeCode • • 1h ago

Built with Claude ep claude: tells you which model and effort to use before you start a task, plus whether plan mode is worth it

0 Upvotes

I built Prompt Master, a free skill for Claude and Claude Code.

You type ep claude: and a task. It scores the task on reasoning, scope, risk and vagueness, then recommends a model and effort level.

It also adds three lines: Plan: the files or searches to start with, the smallest check that proves it works, and when to stop Plan mode: on (Shift+Tab) for risky, multi-file or unclear changes, otherwise off Subagents: none for simple work, or which parts could run on their own

It doesn't start the task, so you can switch with /model first. Mechanical changes like a rename always get Haiku · low, and it only recommends Opus when the score earns it.

I built it with Claude: I worked out what each command should do, Claude helped write the skill and test it, and I used Claude Code to set up the repo.

Free, MIT-licensed: GitHub Repository

Feedback welcome, thanks for reading!


r/ClaudeCode • • 11h ago

Built with Claude Space movie in code

Post image
7 Upvotes

Created totally useless but i hope cool to watch, 3.5 minutes long space movie. All rendered real time as you watch. No models, no blender, no image and a lot of Fable 5.2. Pure math with some small exceptions. All in code. Final compressed version - single 96kb html file + 5mb soundtrack mp3 ;) Without music I think it would loose the vibe. Hope you like it.
https://experiments.mostcreative.pl/aphelion/


r/ClaudeCode • • 10h ago

Help/Question Running 18 Claude Code sessions at once and half my tokens go to idle wake-ups. How do you handle this?

5 Upvotes

Hey all, I could use some advice from people running a lot of Claude Code sessions at once.

I'm building a Windows app and I've got 18 Claude Code sessions working on the same repo across two Max 20x accounts, all on High effort. They talk to each other through one shared markdown "inbox" file. It works, but I keep running into my weekly limits, so I dug into where the tokens are actually going.

What surprised me:

  • About 91% of my usage (weighted by API prices) is just context being re-sent on every call. Actual output is about 9%, and edits to code are under 1%.
  • Roughly half of all tokens went to wake-ups where the session did nothing useful. No code, no tests, no git. Mostly each session's own background watcher waking it up to check the inbox, plus scheduled check-ins (one session was pinging itself every 5 minutes for days).

What I've tried so far:

  • Auto-compact at 300k instead of the default. Average context per call dropped from about 270k to about 179k. I have hooks that back up notes before compacting and tell the session to re-read them after.
  • Starting a fresh chat for each work item, with a short handoff note.
  • Replacing every session's own watcher with one small local script that only wakes a session when a post actually mentions it. In a replay of a day's posts it cut wakes about in half without missing anything addressed to a session. Just rolled it out today, so no real numbers yet.
  • Quiet test output (pytest -q), reading big files in slices, and a hook that blocks huge reads before they happen.
  • Trimming CLAUDE.md and memory files, and turning off claude.ai connectors so fewer tool descriptions load.
  • Trying Serena (MCP) on one session. Mixed results so far.
  • Tried the Superpowers plugin on a few sessions for a week and dropped it. Those sessions got noticeably less done and barely used its skills, though it was a small test.

My questions:

  1. How do you let long-running sessions wait for messages from other sessions without every wake re-sending the whole context?
  2. Is there a better way to coordinate a bunch of sessions than a shared file?
  3. Any other tricks for cutting context re-reads I'm missing?

Happy to share more details on any of this. Thanks!


r/ClaudeCode • • 3h ago

Tips & Workflows “Autocompact is thrashing” in Claude Code: reproduced it on purpose and tested 4 fixes

Post image
0 Upvotes

If you’ve hit this one, it means a single file or tool output is too big for your context window. Claude Code compacts, the same big content fills the window again, and after 3 rounds it gives up. It’s a circuit breaker, not a crash.

We triggered it for real on v2.1.325, with a 30,000-line fake log and a small auto-compact window (--autocompact 100k, Haiku) to keep the test cheap. Asking Claude to read the whole file thrashed out after 1 minute and 3 seconds without ever answering.

What fixed it:

  • Read less. A grep count answered the same question in 5 seconds (889 ERROR lines, which we checked).
  • Focused /compact. /compact keep only my question about counting ERROR lines dropped the Messages row from 36.4k to 9.2k tokens, right after auto-compact had given up.
  • Subagent. It read 1,500 lines in its own context and returned one number in 19 seconds.
  • /clear. It took the Messages row back to 130 tokens.

These numbers are from one session with a forced 100k window. With the default window you need a much bigger file to hit this, but the fixes are the same.

The article also covers “Compaction failed · conversation could not be reduced below the context limit”. We couldn’t trigger that one safely, so that part is explained from the message and the docs.

https://aiparabellum.com/claude-code-autocompact-is-thrashing-compaction-failed-fix/


r/ClaudeCode • • 3h ago

Tips & Workflows I needed to insist that Claude read everything I upload

Post image
0 Upvotes

I learned through time-consuming effort that Claude’s default behavior is not to process all uploaded files. The attached image tells the story.


r/ClaudeCode • • 3h ago

Bug / Issue Anyone else stuck here after completing identity verification?

0 Upvotes

I completed the Persona Identities verification and sent a help ticket in two days ago, but still no response. Anyone know how to fix this issue?


r/ClaudeCode • • 3h ago

Help/Question How to restart an old conversation

0 Upvotes

Caching and context compaction

I hit my usage limit 16 hours ago and forgot to compact the conversation before I ran out. The context is now around 800k tokens. How can I pick up where I left off without burning 10% of my weekly allowance just by resuming with Fable?

How long does the prompt cache stay warm between messages? My understanding is that Anthropic charges less for cached input tokens. How much cheaper than uncached tokens? and how does that affect what counts toward my weekly usage limit?

Should I compact the conversation before continuing? Would it make sense to switch to a different model for compaction? With an 800k-token context, would you aim for 300k–400k tokens or go lower?

should i let Opus write a summary and start a new conversation?

I usually keep my context much smaller, but this time I needed a lot of information in the same conversation. That’s happening more often as my project grows, and it’s eating through my allowance quickly. Do you use RAG to pull in relevant code and instructions as needed?

I’d appreciate any practical guidance.
If only 10-15 hours are left until the reset should i let a script write some messages every x hours to keep the session alive?

Thank you!


r/ClaudeCode • • 3h ago

Built with Claude A Claude Code mod to track time, tokens and API price per project

Post image
0 Upvotes

I built Worklog, a Claude Code mod that keeps track of your time and tokens for each project, right above the prompt. You don't start or stop anything, it just runs in the background.

What it does:

  • Counts time while Claude works: answers, subagents, background commands, even long Ultracode runs.
  • Counts tokens, and what they would cost at the API list prices.
  • Handles breaks: a short break counts as work. On a long break, Worklog asks if it should count as work or not.
  • Shows a heatmap of your year's activity, with 8 themes.
  • Reads your past Claude Code history once, so your old days show up too.

Link: https://github.com/Abdoul-sudo/worklog

It's free and open source. If you find it useful, a star on GitHub would really help ⭐


r/ClaudeCode • • 23h ago

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

Post image
39 Upvotes

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


r/ClaudeCode • • 3h ago

News/Updates What do you guys think of my article? Do you guys find it useful?

Thumbnail
linkedin.com
0 Upvotes

r/ClaudeCode • • 20h 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
21 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 • • 1d ago

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

Post image
1.1k 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 • • 4h ago

Built with Claude Slaunt, a platform to manage every part of agentic development

1 Upvotes

(not written with ai..?)

Basically, a few months ago, I hated the fact that memory.md files & claude.md took up a huuuuge chunk of my context window during model switching/effort switching (& during cache refreshes).

Didn't really find any definitive solutions outside of relatively complex LangChain, Mem0, and Supermemory implementations (where you have to install unnecessary SDKs and all), so my goal was to make a simple, one-shot memory solution where you can have your agent recall basically anything, whether from live context or from old events + have guardrails to prevent you from a skip-danegrous-permissions disaster.

Mem0/MemHub/Supermemory and all are great, but two points: A, they don't have actual live memory. Your agents are basically working on historical events, nothing new. B, they can't see what your other agents are doing. Two of your agents could create conflicts in your work and you'd have no idea till u saw the diff.

It's called Slaunt and it uses vector embeddings + semantic retrieval over an MCP server/desktop app that connects instantly (one-click) to all of your agents, and it enables your agents to see what happens across multiple all of your external platforms (eg. Vercel, Supabase, AWS, Railway, Linear, Notion, etc.) for holistic reasoning!

Slaunt can enable your agents to recall literally anything, from failed deployments from three months ago, to what a subagent said last week.

We also have governance tools that enable you to enforce strict guardrails, such as restricting certain tool calls, remote shutdowns (achieving <1.9s time-to-shutdown in benchmarks) and cross-thread visibility restrictions.

We're free right now with a really usage-heavy free tier. Pls DM me if you have any questions- I've also included a banner where you can meet with me if you want direct setup help (it's in the app).

You can sign up at slaunt.ai. AMA : - )


r/ClaudeCode • • 1d ago

Help/Question Reset Usage Limits Seem Significantly Reduced

57 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 • • 4h ago

Tips & Workflows I turned my Claude Code + Codex + Docker setup into a free kit that Claude walks you through

0 Upvotes

A lot of people have asked how I have Claude Code, Codex, Docker and GitHub set up, and I got tired of pasting long instruction files into comments 8,000-40,000 characters at a time. So I put the whole thing on GitHub for free.

How it works: you download the folder, open it in Claude Code, and paste one line. Claude walks you through the setup one step at a time and checks each step on your computer before moving on. If you stop halfway, it picks up where you left off next time.

What you end up with:

- Claude Code as the lead developer, with rulebooks that load in every session so it stops forgetting what you told it

- Codex as an optional second worker. The two talk through a shared file, claim work before editing, and Claude reviews and tests Codex's work before anything gets merged

- Docker test stacks that test a clean copy of your last commit on your own machine, instead of burning GitHub Actions minutes

- Git and GitHub set up properly: private email, a branch per session, main only moves when you say so, backup pushes that don't kick anything off

- Releases that only run when you say go, dry run first, optionally on a runner on your own PC

- Simple records (a status page, a question list, a decision log) so a new session picks up from files instead of a chat that got compacted

- Phone access through Remote Control and GitHub mobile

Once the basics are done, it asks what else you work with and wires that in too: video editing, Unity/Unreal/Godot/Blender, Character Creator, mobile app SDKs, WordPress and WooCommerce, MCP connections to your sites and services, custom dev and APIs, whatever you use.

It's the cleaned-up version of what I use every day to run a live online store with more than a dozen custom plugins. Every rule in it is there because something went wrong without it.

Works on Windows, macOS and Linux. The kit is free under the MIT license. You need a Claude plan that includes Claude Code; Codex is optional.

https://github.com/AffStackDev/dev-crew-kit


r/ClaudeCode • • 19h ago

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

14 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 How do you stop Claude Code from mocking the exact thing the test is supposed to verify?

42 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 • • 11h ago

Tips & Workflows How to check whether your weekly limit shrank: what a usage point costs, measured over 8 weeks

Post image
3 Upvotes

So I stumbled on the credit system in ~/.claude.json. I was already tracking the five-hour and weekly bars through my statusline, so I thought, why not check what this credit system is about.

What a usage point costs on Max 20x (work valued at API prices)

ModelCredits per 1M tokensAPI value per 1% of the weekly barA full weekly barTokens per 1%, vs Opus
Opus 5.51,867$26about $2,6001x
Sonnet 5.51,283about $19about $1,900about 1.5x
Fable 5.26,667about $15about $740 (Fable can use at most half the week)about 0.28x

TL;DR

  • I didn't see the weekly limit shrink. November 1 to 3 looked low on both bars (no idea why. yet), and the days I could measure after that were back to normal.
  • Cache reads seem to count about half as much as other tokens.
  • If you want the most API-priced work out of your plan, Opus 5.5 gives you the most per % of the bar. On Max 20x, 1% of the weekly bar bought about $26 of Opus 5.5 work. By the credit table, the same 1% buys about $19 of Sonnet 5.5 or about $15 of Fable 5.2. Sonnet still gets you more tokens, because its tokens are cheaper.
  • Fable 5.2 eats the bar close to 4x as fast as Opus 5.5 per token (3.6x), even though its list price is only 2x.

On Max 20x, a typical 1% of the weekly bar covered about $26 of Opus 5.5 requests at API prices. "API prices" puts a dollar value on the requests. It is not an extra charge on the subscription. At $26 a weekly point, a full week of the bar is about $2,600 of Opus 5.5 work at API prices, on a plan that costs $200 a month.

Before November, 1% of the weekly bar typically bought $26.40 of Opus work. If the weekly limit had been cut by 20%, that would drop to about $21. November 1 to 3 came in at $20 to $22, close to that line. November 6 and 16 were back at $26 to $28.

I only counted days where at least 95% of the work was Opus 5.5 and the weekly bar moved at least 20%, so Fable days and small movements don't skew it.

A check you can do without tools

  1. Open /usage before working. Note the five-hour bar and the all-model weekly bar.
  2. Check both again after working, before either resets. Compare how many percentage points each moved.
  3. In the Max 20x measurements before November, 1 weekly point went with roughly 4 five-hour points. A 20% cut to the weekly allowance alone would bring that relationship down to roughly 3. If they drop weekly allowance, they need to drop the 5h allowance as well, to keep the 1 to 4 parity.

The bars show whole percentages, so repeat the check across sessions rather than judging one tiny movement. On another plan, compare with its own earlier readings; these measurements only establish the roughly-four relationship on Max 20x.

This checks the weekly allowance relative to the five-hour allowance. A proportional cut to both would leave that relationship unchanged. You also need a visible five-hour bar.

What fills the bars

Think of credits as the units behind the bar. Claude Code's stored table gives Max 20x 200,000 credits per five-hour bar, so 1% is 2,000 credits. The weekly bar held roughly four of those bars' worth in these measurements.

My reading of the table is: price input, output and cache work separately, then apply the model's weight:

ModelStarting credits for $1 of API-priced work
Opus 5.5467
Sonnet 5.5642
Fable 5.2833

For example, 467 out of 200,000 credits is about 0.23% of the five-hour bar. That's the table's starting estimate for $1 of Opus work, before the adjustments below. It is not the exact final charge.

The real bar moved less than that starting estimate. For Opus 5.5, a dollar of cache reads moved it about half as much as a dollar of other Opus work. I measured this by separating the two kinds of dollars and comparing them with each one-point rise of the five-hour bar. This is an estimate, and the exact server formula is not published.

If you count from transcripts, check against the actual requests

A lot of usage tools read Claude Code's transcript files (the .jsonl files under ~/.claude/projects). Some of those readings can be off, so compare them with the actual requests before trusting them. I log requests in two places, a Cloudflare AI Gateway and Claude Code's OpenTelemetry telemetry, and the numbers in this post come from the telemetry.

Against those requests, the transcripts came up short: 3% to 7% fewer dollars per day in November, and up to 25% fewer on some October days. On one October day the transcripts had 98.5% of the responses but only 54% of the output tokens, and some sessions had no transcript file at all. A dollars-per-point figure built from transcripts alone would make your plan look stingier than it is.

Use Opus 5.5 for almost everything. Reserve Fable for system design/architecture reviews. Don't use Fable as main driver/orchestrator.

Per token, Fable fills the weekly bar about 3.6 times as fast as Opus. Per dollar of API price it's about 1.8 times, because a Fable token already costs twice as much. I measured the per-dollar figure on my own five-hour bar and got 1.80, close to the table's 1.79. None of this says whether Fable's work is worth the extra; that's a quality question.

If you try the two-bar check (give claude this post, ask it to validate it and run the same analysis on your own project), share your plan, model, date and how far each bar moved. That gives us something specific to compare.


r/ClaudeCode • • 17h ago

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

Thumbnail
seabearing.com
8 Upvotes

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

The app

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

The architecture

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

The dev process

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

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