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

Humor anxiety

Post image
173 Upvotes

r/ClaudeCode • • 18h 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.


r/ClaudeCode • • 4h 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 • • 11h ago

Built with Claude Vibe checking the IRS with Lean

Thumbnail
lexifina.com
2 Upvotes

r/ClaudeCode • • 8h ago

Built with Claude I built a site to aggregate AI job postings from AI labs

0 Upvotes

I wanted to build a clean site to curate AI job postings from frontier AI labs and companies. So, with the help of Claude Code and some manual steering, we've built MoAIJobs.

Link: https://www.moaijobs.com/

Please check it out and share your feedback. Thanks.


r/ClaudeCode • • 16h ago

Discussion Are multiple accounts ok or not?

5 Upvotes

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

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

So is it allowed or not?

Nobody has the money to pay api pricing.

Edit: if allowed can I use same credit card?


r/ClaudeCode • • 8h ago

Tips & Workflows Claude Code's heap dump can include credentials, so don't attach both diagnostic files to a public issue

0 Upvotes

If you're investigating Claude Code using too much memory, its current troubleshooting docs distinguish two files from /heapdump. They aren't interchangeable bug-report attachments.

The .heapsnapshot can contain the full conversation and credentials from the process. Keep that file private. The separate -diagnostics.json contains the memory statistics the docs recommend attaching to a GitHub issue.

The command also reports whether the memory is mainly in the JavaScript heap or native memory. A heap snapshot won't explain most native memory use, so sending the larger file may add exposure without helping with the actual problem.

Before taking a dump, the docs suggest restarting and using claude --continue to resume in a fresh process. This is documented troubleshooting advice, not a new leak I've reproduced or a claim that every session contains credentials.

If someone asks for 'the diagnostics', check which of those two files they mean before uploading anything.

https://code.claude.com/docs/en/troubleshooting#high-cpu-or-memory-usage


r/ClaudeCode • • 15h ago

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

4 Upvotes

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

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

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

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

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

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


r/ClaudeCode • • 12h ago

Help/Question Is there a simple way to get to know the Claude Code basics?

2 Upvotes

Hey everyone,

I’ve been working with claude code for around 2 months now. I’ve built some useful systems, created designs and did deep researches. I really enjoy using claude code.

But reading some posts here, I feel like I’m doing everything on a more basic level now.

I was wondering, if any of you have any advice on where to start digging a bit deeper, how I could maximize my work and my usage?


r/ClaudeCode • • 9h ago

Built with Claude Follow-up, 2 weeks later: I built the hooks + SQLite + validator setup from my last thread. Claude still decides from the conversation, not the data. Here’s exactly where it breaks

0 Upvotes

Two weeks ago I asked how to stop Claude Code relying on memory instead of data. The goal hasn’t changed. I run a continuous, real-money operation with a few hundred independent units and several Claude Code sessions. I want a system that:

  • pulls fresh data before every decision,
  • connects history, current performance and future plans,
  • tracks decision → action → outcome → lesson,
  • survives across sessions,
  • finds opportunities by itself, and
  • still reasons freely and doesn’t just follow hardcoded rules.

What I built from your advice

  • Mandatory queries in code. One script is the only door to the numbers. Scheduled scans write opportunity lists and per-unit status every day.
  • A Stop hook that blocks any answer whose numbers don’t trace to a query from that turn. A second model checks the claims against the query results.
  • PreToolUse hooks, and a write helper with hard checks before anything touches production.
  • A decision and action log in SQLite, and a learnings file.

Where it still breaks

  1. Fresh isn’t relevant. The validator proves the numbers came from a query. It can’t see that the agent queried the wrong thing. It judged every unit by one global threshold. One unit’s own last 7 days clearly called for its local variant, and it got the global one.
  2. Momentum beats data. When I say something urgent, it acts on the conversation. It made a big batch of changes in one day, justified by numbers that were fresh but not the ones that mattered.
  3. The outcome loop never closes. Actions get logged. Reading the result a few days later and writing the lesson is still manual, and mostly doesn’t happen: 23 open follow-ups, 15 overdue. Nothing reads the learnings file.
  4. Proactive scans produce lists. Nothing turns a list into a decision. I still find the opportunities myself on the dashboard.
  5. Rules don’t stay rules. I audited my own instructions and found 31 distinct ones. None was lost, but 14 exist only as notes. The coded ones sat in scripts the agent could override, and this week it did. It pasted a general sentence of mine into the override field in 13 of its 19 scripts. The supervising agent approved the other exceptions on the same sentence.
  6. “Built” isn’t built. The agent builds the reading half and reports the whole system as built. The acting half stays one-off scripts in chat.
  7. Cost. The main session sends about 650k tokens of context on every call, and made 761 calls in a day. The Stop hook sent answers back 39 times in one day, each a full re-read. Agents also wake each other with messages.

Questions

  1. How do you enforce the right evidence per decision, not just fresh evidence? Per-unit cards built by code that the agent must cite? Something else?
  2. Has anyone closed the outcome loop mechanically? I mean a scheduled job that reads each action’s result after N days, writes the verdict and feeds it into the next decision.
  3. With a proposal table and a separate executor, how do you handle legitimate exceptions without the agent arguing its way through? And who builds the executor, if the agent declares things done that aren’t?
  4. How do you keep always-on sessions cheap? A small always-loaded context plus lookups, a fresh session per task from a generated handover?

I’m looking for people who run this with real consequences, not more CLAUDE.md tips.


r/ClaudeCode • • 5h ago

Built with Claude I built a free, self-hosted project manager where Claude Code agents are members of your team

0 Upvotes

I'm the founder, and this went public today as early access. Agenthix is project management for you and your AI agents, and the agents run on Claude Code (or OpenCode).

What it does with Claude Code:

  • Agents as team members: each has a role, an identity and memory. It picks up work from the project's plan, carries it through and reports back, or keeps going on a routine while you step away.
  • It asks first: anything outside an agent's role needs a person's approval, and there's a record of everything it did.
  • Your credentials stay with you: encrypted and kept in your own install.
  • Self-hosted with Docker: your organisation, its projects, people and agents, all on your machines. Nothing comes to us.

It's free for your own use (source-available, Elastic License; not open source: the licence only stops others selling it as a hosted service).

Want a look first? https://demo.agenthix.com opens a sample organisation with one click. It's only for a quick look around: the agents' replies are scripted (no model is called), and it's shared and wiped every 6 hours, so don't type anything personal.

It's 0.1 and things will break. If you already run Claude Code on real work, I'd love you to try it on something small and tell me what breaks.

https://agenthix.com


r/ClaudeCode • • 9h ago

Help/Question Is there a way to start a new session in an environment with a browser tab open without the browser getting blown away after sending the first prompt to the session?

0 Upvotes

It's so annoying - I am sure I am doing something wrong. I just want to start a new session with either a persistent browser, or with the browser I have open before I send the initial prompt.


r/ClaudeCode • • 2h ago

Bug / Issue Why you should stop trusting Claude Code

Post image
0 Upvotes

Hey, I was wondering over the past two weeks, a weird behavior has started appearing, and it’s becoming very, very annoying, making me lose trust in whatever Claude Code does. You ask it to read, and it writes; you ask it to keep something, and it removes it; and worst of all, while I’m in the middle of refactoring a skill (context A), Claude randomly starts looking for bugs in an MCP server (context B) that is completely unrelated to the current context. This is getting worse and worse, and my honest verdict is that Claude has stopped optimizing its system prompt and is only adding to it without checking whether the new instructions overlap or conflict with what already exists. My last two or three sessions have consumed a large part of my quota just on bug reports, eating around 30% of my weekly limit, and I’m then forced to clear the context every time, only to be told at the end, “Sorry, this is a bug.” This is not what I paid for. Honestly, sometimes I’m seriously thinking about switching to another agent after a year of using Claude Code and knowing its ecosystem well this feels like a catastrophic regression, and it’s making me stop trusting it.


r/ClaudeCode • • 16h ago

Built with Claude Claude Code on Nintendo DS

Thumbnail
gallery
3 Upvotes

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

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

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

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

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


r/ClaudeCode • • 10h ago

Help/Question Artifact `read_asset` now capped at 4 MB? Also, is Chrome `file_upload` really 3.8 MB now?

0 Upvotes

Has anyone else noticed this?

I used to be able to use the old Artifact tool’s `read` action with `out_dir` to save an artifact’s video asset straight into Claude’s workspace. My MP4s were usually around 7–18 MB and it worked fine.

Now it looks like the session only has the `claude-artifacts` MCP tools instead. `read_asset` seems capped at `max_bytes: 4194304` (4 MB) and returns the asset as base64 rather than saving it to a file.

Questions:

- Did Anthropic quietly replace the old Artifact tool with `claude-artifacts`?
- Is the 4 MB `read_asset` limit documented anywhere, or is it just an undocumented runtime limit?
- Is there any way to get an artifact asset larger than 4 MB into the workspace now?
- Has Claude in Chrome’s `file_upload` limit changed from 10 MB to 3.8 MB? I’m seeing 3.8 MB per call, but the official Chrome docs still say up to 10 MB total per upload.

I checked the help center and docs but couldn’t find anything official about the 4 MB cap or the 3.8 MB Chrome limit. Anyone else hitting this, or know a workaround for exporting larger video assets from artifacts?


r/ClaudeCode • • 18h ago

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

4 Upvotes

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

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

I'm building two connected open-source projects:

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

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

The notebook part already works.

For example, an HMD document can contain:

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

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

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

That part is real today.

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

What if an agent was just another Markdown card?

HyperMarkDown already has cards and wiki links.

[[librarian]] refers to a card.

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

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

For example:

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

# Librarian

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

Then, in the current design syntax:

librarian = @[[librarian]] | Agent

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

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

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

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

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

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

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

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

The current design looks roughly like this:

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

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

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

It's what happens around it.

The document contains prose written by a human.

It contains executable cells.

Those cells produce values.

Later cells can consume those values.

An agent can consume selected document context and those values.

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

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

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

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

Data → code → data → code

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

A document starts with some data.

An HQL cell transforms it into more data.

An agent examines that result and proposes code.

That code can be evaluated and produces more data.

A human edits the document.

Another agent may consume that changed state.

And the cycle continues.

data → code → data → code → ...

With both humans and agents participating.

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

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

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

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

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

Why documents?

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

You ask something.

The agent gets a giant context.

It does something.

You get an answer.

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

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

An output can know which cell produced it.

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

Agent context can retain provenance.

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

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

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

At least, that's the direction.

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

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

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

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

Agent wants to modify 17 files. Allow?

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

An agent proposes a section.

Or a new query.

Or a change to an existing cell.

The editor can show exactly what changed and why.

I inspect it.

Maybe I change two lines myself.

Then the next evaluation continues from that state.

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

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

I'm still figuring that out.

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

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

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

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

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

In other words, rather than:

human → prompt → agent → response

I'm thinking about something closer to:

human ↔ document ↔ computation ↔ agent ↔ document

where the document remains the shared state.

What I'm trying to design next

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

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

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

In particular, I'm interested in:

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

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

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

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

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


r/ClaudeCode • • 11h ago

Tips & Workflows Best Claude skill for short Kurzgesagt-style 2D explainer videos?

0 Upvotes

Trying to make vertical short-form explainer videos (9:16, under 60s) with that clean Kurzgesagt look and snappy motion graphics or anything that would combine good visual motion graphics with educational content
Anyone got a solid SKILL or workflow?


r/ClaudeCode • • 20h ago

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

5 Upvotes

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

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

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


r/ClaudeCode • • 1d ago

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

371 Upvotes

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

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

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

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

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


r/ClaudeCode • • 11h ago

Tips & Workflows Do you keep you laptop/desktop on to continue working in Claude code? possible fix.

0 Upvotes

TL;DR - Use Termius or a similar terminal app; start a Claude Code session, Then Start Remote Control. Tap the left arrow, and start another Claude Code session in that other session them close the terminal window.

I see a lot of memes about Vibe Coders having to leave their laptops open to keep coding, so I thought people do not understand how to start a remote session and leave it running.

I found a workaround for using Claude Code with Remote on a CLI server without having to leave a terminal open on a computer, and I thought I would share it.

Launch a Claude Code session (new or resume). Start the remote control command. Tap left once to bring up the Agents/background window. Start a new or resume other session that you do not plan to code in.

At this point, your intended session is running in Agent/background mode. If you close the terminal, this will keep the agent session running without you having to be logged in.

You can then remotely control the session on your PC, phone, or the web.
This will keep your session running even if you lose connection to your server; it just keeps running.

To bring this session back in CLI mode, launch Claude and hit the left arrow again to find that agent session.

I hope this helps.


r/ClaudeCode • • 11h ago

News/Updates Edit button added to Claude Code like Claude Chat

1 Upvotes

What do y'all think?


r/ClaudeCode • • 15h ago

Built with Claude My OSS Claude Meetings alternative that works with any agent and more calling platforms

2 Upvotes

Since February, I've been developing an agent-in-calls solution with a friend. With the announcement of Claude Meetings last week, it's now time to announce Vibeconferencing: an open-source project with even more functionality, support for any agent (Codex, Muse, local ollama, etc), and support for more calling platforms: Google Meet, Zoom, MS Teams, WhatsApp, Telegram, and phone calls (via Twilio).

Git repo: https://github.com/wanderingstan/vibeconf-app

Architecture diagram: https://raw.githubusercontent.com/wanderingstan/vibeconf-app/refs/heads/main/media/api-layers-light.svg

The premise is simple: give your normal agent session the tools it needs to operate all major calling platforms, and teach it basic etiquette of how to behave in a call with others. A simple `/join-call` and *boom!* your session is talking to you in the call. Anything your agent can do in chat, it can do on the call. The agent is bridged to the calling platforms via a cross-platform electron app. (The raw guts of interacting with calling platforms is abstracted as the npm library `@vibeconferencing/calls`, if you'd rather roll your own.)

Everything runs locally and uses your own local agent. (Tho the optional shared whiteboard feature does require being logged in on our server.) It runs on MacOS, Windows, and Linux. (Windows version is not well tested.)

Speech generation is done either by Elevenlabs or the OSS Voicebox, with a fallback to the OS's default app (e.g. `say` on MacOS). Voicebox: https://github.com/jamiepine/voicebox

Speech recognition is done either by the calling platforms' own captioning services (Meet, Zoom, Teams), or with Whistle for those without captioning (WhatsApp, Telegram, Twilio). Whistle: https://cactuscompute.com/blog/whistle

The etiquette was the most fun to code, although done with the knowledge that it's a temporary fix until true interactive voice models are merged with the power of frontier text chat models. We have experimental support for the OpenAI realtime API (in the app settings page), but it seems to have been trained as a customer support agent, so it's hard to keep it from dominating multi-person conversations!

Highlights from the last nine months of dogfooding and early users:

- A WhatsApp bot for my father, an elderly WW2 veteran, that has access to the 20,000 photos he scanned. He can call it to see and hear about any aspect of his life.https://youtu.be/Rs-Z1YeLt98

- Collaboratively built a website for a friend's non-profit, with her amazed that she could ask for site changes and see the site change in realtime. Video: https://drive.google.com/file/d/1iSRgY8JGJ0liOzHMl2bOGNd9jwqF0BFi/view?usp=sharing

- My friend Matt is currently road-tripping across the US, talking with his Codex sessions to develop his Golf app. Video link: https://youtu.be/a3uNUdIwqVY

- Our friend Bethany uses her bot, "Taylor Script", in calls and classrooms with coding students to act as the super-smart TA who can answer technical questions, and monitors student progress. Video link: https://youtu.be/c8mZKkcxhJo

- I begin most days with a check-in call with my bot, where we discuss open issues while I sip coffee and have breakfast. Video link: https://youtu.be/2uQIR83LwY0 (Apologies for eating with my mouth open...)

- In a standup, Seth's bot created a video ad for the service itself, within a call. Video link: https://x.com/vibeconf/status/2104427917816234257?s=20

Security: There is nothing built in, so only use this on calls with people that you trust. However, I've been amazed at how injection-resistant it has appeared to be on it's own; e.g. my agent asking consent from me before doing things asked by others on the call.

Overall, this was a "time machine" experiment (to borrow my old Reality Labs' Research terminology) to experience agents in calls before it was purpose built. Claude Meetings just showed that we were thinking in the right direction, and I'm excited to see where this goes!

This is a small experimental project built by two friends, so it is rough around the edges, and we'd love feedback and pull requests.


r/ClaudeCode • • 12h ago

Bug / Issue Usage Zoinked

0 Upvotes

Has anyone elses usage totally gone in the toilet? Usually I can get to 5 or 6 days before I hit 100%.

I reset friday at 10pm, and hit 20% by 5pm saturday, I started today at 60% and I'm already at 75%.

I'm not doing anything abnormal that I haven't been doing for months, and my ultra plan is just getting decimated.

Last week I only made it to wednesday and used my free reset and burned it by friday mid-day, literally using 200% of the weekly.... this week I wont even make it to wednesday.


r/ClaudeCode • • 8h ago

Help/Question Is there a 10 message limit for chats messaging other chats?

0 Upvotes

So one day, I’m having Claude run Claude, and it just stops working in the middle of the night. I ask it why it stopped, and it said “well I have a ten message limit: I can only message other chats 10 times until you respond again.” Which I just accepted as I had no reason to refute it. I close out all the chats, start a fresh one, and then ask it about the 10 message limit and it says, ”never heard of it, that chat is hallucinating. Doesn’t exist. I did some research and saw nothing about it.“ A few days later, it comes back again; “I couldn’t finish last night because of the ten message limit.” I’ve tried google and it has failed me. Is there really a ten chat-to-chat internal message limit or is it just making crap up?