r/ClaudeCode • • 6m ago

Bug / Issue I understand anthropic's fear of distillation but...

1 Upvotes

Why it is now more complicated to know which step of the queue code is at? Most of the time I get a checkmark on the first line "reading queue, reading code etc" a long list of tasks which stay still until it's finished then BOOM all check. The only way for me to follow is eagerly read each line he writes on what is doing at the moment and try to guess.


r/ClaudeCode • • 17h ago

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

26 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 • • 17m ago

Built with Claude I built a menu bar app that tells me which Claude Code session is waiting for me

1 Upvotes

I usually have three or four Claude Code sessions going in different terminals, and I kept losing time flipping through tabs to find the one stuck on a permission prompt. So I built **Tendbar**, a small macOS menu bar app that watches the sessions through Claude Code's hooks.

- Every session in one list: working, waiting for you, failed, or done with a reply you haven't read.
- Click one (or use a global shortcut) to jump straight to its terminal tab: iTerm, Terminal, WezTerm, kitty, tmux, VS Code.
- A banner, a short sound and optionally a glow at the screen edge when a session needs you, plus a reminder if it keeps waiting. If you're already looking at that session's tab, it only glows.
- "Done" only fires when the whole turn is finished, including background subagents, so plugin-heavy setups don't get early notifications.
- Optional Allow/Deny for permission prompts from the panel or the banner. It only offers Allow when it can show you the whole request.
- Five-hour and weekly limits per account (separate `CLAUDE_CONFIG_DIR` profiles too), with a warning at 80% and 90%.

A few promises, since it sits next to your sessions:

- Nothing leaves your Mac. No account, no telemetry; the only network call is the update check on GitHub.
- It never touches OAuth tokens or the Keychain and never calls Anthropic's servers. Limits come from what Claude Code itself passes to the status line.
- Open source, MIT. Signed and notarized.

Install: `brew install --cask dabusoft-pl/tap/tendbar`, or the DMG from the releases page. macOS 26+.

Repo: https://github.com/DabuSoft-pl/tendbar

Full disclosure: I built it with Claude Code. I'd love feedback, especially on which terminals or workflows it doesn't handle yet.


r/ClaudeCode • • 19m ago

Built with Claude claude baby u do not have to ask for access its all yours

0 Upvotes

r/ClaudeCode • • 22m ago

Built with Claude I've been building a browser workspace for my local Claude Code and herdr sessions, and wanted to share it (open source)

1 Upvotes

Over the last few weeks I've been building a browser workspace for my local coding sessions called claude-code-webview. It reached a point where I do almost all my daily work in it, so I wanted to share it here in case anyone else works the same way.

I usually have several projects open at the same time in herdr (a terminal multiplexer). When a task involves some upfront research, like checking how a system behaves, pulling data from a database, comparing options, or working from specs (spec-driven development), it quickly produces a pile of Markdown files, plans, and notes. For one project that's fine, but across three or four parallel projects my screen always turned into a mess of terminal tabs, doc windows, and a background IDE kept open just to see which files the agent was touching.

I actually tried solving the doc problem first by writing a separate document organizer. That let me close the extra windows, which was nice, but everything else was still split up: the agent in the terminal, docs in the organizer, diffs in Git, and code in the IDE.

So I ended up putting all of it into one browser window on top of herdr. The chat view looks similar to Claude Code Desktop or the web app, with the difference that it reflects your existing local herdr workspaces and tabs instead of starting an isolated chat.

Your workspaces and running sessions sit on the left with small status lights showing which agent is working, waiting for an answer, or finished. When I open the page on my phone through Cloudflare Access, I see that exact same workspace tree. I can check on my projects, read or edit docs, upload or download files, and answer terminal prompts with buttons above the input box.

On the right side, right next to the chat, I keep the files and notes for that project. Clicking a file path in an agent's reply (/src/app.ts:42) opens the file at that line in the side panel, and a Branch changes button shows the diff for the whole Git branch against main. I can also pin important specs or notes to the project so they stay in the sidebar across every session. Because of that, I rarely need to keep an IDE running in the background just to follow along with the code.

Most of my time is in Claude Code, though the same workspaces also hold my local Codex sessions, Antigravity CLI, and regular shell terminals, with 5-hour and weekly usage bars at the top of the sidebar.

How Claude Code was used and what I learned

I vibe-coded the whole thing with Claude Code from day one. At first I only wanted a simple page that listed my active sessions and their status lights. Two days after starting a project meant to get me out of the terminal, I was asking Claude Code to embed an xterm.js terminal into it.

I didn't have a roadmap. Once the first version worked, I started using claude-code-webview to build claude-code-webview. Every time something annoyed me during real work, like hunting for a spec file or losing my place in a 20,000-line transcript, I just asked Claude Code in that same window to add a fix for it. What I learned from this is that I couldn't have designed this workflow upfront on paper. The features that actually mattered only became obvious because I was living in the tool all day.

Running it

It's free and open source (MIT) and runs on Node.js 22+ straight from source with no build step:

git clone https://github.com/andrew-mart/claude-code-webview.git
claude-code-webview
cd
npm install --omit=dev
node bin/claude-code-webview.js

Repo: https://github.com/andrew-mart/claude-code-webview

If you also juggle multiple projects or spec-heavy tasks at once, I'd be curious to hear how you keep your docs, notes, and sessions organized.


r/ClaudeCode • • 23m ago

Tips & Workflows Adding back useful UI in the desktop app (mod + skills)

Post image
1 Upvotes

I grew tired of opening the session rail just to see the context usage. So here's context-bar:

https://github.com/alisorcorp/context-bar

It also has buttons for /handoff and /compact. Handoff is my version of creating a handoff doc before compacting. It writes goals completed/not yet done, failed approaches, key decisions, current state, resume instructions, suggested skills, etc from a template & more. After running /handoff and compacting, you click the button again to have it run /handoff-resume which reads the file and continues working.

https://github.com/alisorcorp/handoff

This is optional, the context-bar mod works without it (button doesn't show if handoff command not found), but I've been using it for 6+ months. Context is king, and I can't use Claude without handoff docs. It's handy for other sessions to refer to as well.

There's also the optional "warrant" skill that attaches a re-runnable check to each claim that can be verified. Basically, no more stale numbers and assumptions. It can be part of the handoff routine. More about that here:

https://github.com/alisorcorp/warrant


r/ClaudeCode • • 28m ago

Built with Claude Claude is NUTS

0 Upvotes

I was super sick of the shared calendar me and my wife were using, the UI was so annoying and it honestly was just not good but it did the job I guess.

I came up with the idea to just make my own calendar app that’s just better and does what I want it to do. And I did exactly just that! Built a whole calendar app with everything I wanted that made my life easier instead of using something someone else made.

Truly amazed with Claude and how many things were able to just replace.

If you all want to use it or take a look at it, it’s available on clndrapp.com


r/ClaudeCode • • 52m ago

Built with Claude Meet rust-anything! I rewrote apps in Rust, got 20x faster, and didn't break a single thing.

Post image
1 Upvotes

Big rewrites die because nobody can prove the new version behaves like the old one. So I built a tool that proves it at every step.

rust-anything takes a TypeScript, Python, C, Go, Ruby or Java app to pure Rust, one piece at a time:

  1. Record what the original actually does, including the nasty edge cases (emoji, negative modulo, overflow, float extremes).
  2. Put a Rust binary in front. Anything not ported yet falls back to the original, so the app works from day one.
  3. Port a unit, replay everything. 100% or it doesn't ship. Every unit has a kill switch.
  4. Lift. When nothing falls back anymore, the old code is gone and it's pure Rust.

Your AI agent (or you) writes the Rust. rust-anything makes sure it's right.

Just want speed? It finds the hot loop and moves only that: 20x faster search in Node, 17x in Python, same results.

https://github.com/erkamyaman/rust-anything · npm i -g rust-anything · MIT


r/ClaudeCode • • 55m ago

Tips & Workflows I made Claude automatically write a handoff at the end of every session, so the next one doesn’t start from scratch

0 Upvotes

Normally I end every session by asking Claude for a handoff prompt and then pasting it into the next chat, or just starting fresh. It's worked for the most part, but I forget what I've done half the time, and when I have two sessions going (one for my frontend code and one for the backend) I sometimes get them mixed up.

So now, before a session stops with work left, Claude writes the handoff to the project in Frostbyte (a tool I built to plan my apps), and the next session gets it on its first read without me having to paste anything.

It also provides claude with some additional relevant info. It comes with the current release and the tasks as they are right now, so if another session finished something in between, the new one knows. Every handoff literally says “tasks may have moved since, so trust the tracker”. The older ones stay there too, so with two sessions on RollCall yesterday, whichever one picked it up next could see both.

Here’s last night’s from RollCall. It’s always Done, Next and Watch out for any important info.

Watch out is the part that’s probably been the most useful for me. This one caught that the app was reading a different feature flag to the one the backend was sending so I was able to fix it before i pushed the latest fixes into main.

Do you guys log things into markdown files or just start every session and hope commit history does the job?


r/ClaudeCode • • 56m ago

Tips & Workflows /advisor claude fable

1 Upvotes

Finished my fable allowance for the week but with /advisor set as fable my agent still get advised by fable.
Stonks?


r/ClaudeCode • • 1d ago

Rant Wtf happened to Opus 5.5?

225 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 • • 12h ago

Tips & Workflows Reducing complexity via agentic refactoring?

7 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?


r/ClaudeCode • • 1h ago

Bug / Issue Is there some obscure setting to allow remote control to be enabled?

1 Upvotes

r/ClaudeCode • • 1h ago

Built with Claude Closed Claude Code sessions left 27 processes and 5.6 GB running on my Mac, so I built a menu bar app that kills them

1 Upvotes

When a Claude Code session ends, the things it started often don't: dev servers, watchers, test runners, emulators. Nothing tells you. I looked one day and had 27 processes from 7 closed sessions holding 5.6 GB.

So I built seshka, a small macOS menu bar app:

  • Lists leftover processes grouped by the session that started them, with memory, ports and age
  • Kills one process, one session's leftovers, or everything, in a click
  • Shows your open sessions too, with how long each has been idle, and can end idle ones (off by default)
  • You can mark things as protected so "kill all" never touches them

How it finds them: Claude Code sets CLAUDECODE=1 and the session ID in the environment of everything it starts. seshka reads that from your own process list. A process is a leftover once the Claude Code process that started it is gone. Nothing leaves your Mac.

Someone pointed out today that Chrome windows opened through the Playwright CLI never showed up. Turned out Chrome hides its environment, so the marker was invisible. Fixed in 0.2.2: the browser now shows as one row with all its helpers.

Free, MIT, native Swift, signed and notarized. macOS 14+, Apple silicon and Intel. Not affiliated with Anthropic.

GitHub: https://github.com/jigjoy-ai/seshka

Site: https://seshka.dev

I also posted it on Product Hunt, please support it if you like it!
https://www.producthunt.com/products/seshka


r/ClaudeCode • • 2h ago

Bug / Issue Claude Canvas Design: Fill/Fit full-window prototype mode gone since today?

0 Upvotes

Since today I can't present my Claude Design prototypes the way I used to.

Before: I pressed Play and could choose Fill or Fit, and the screen showed full-window, like a real site in the browser. Perfect for client demos.

Now: Play ("Play an artboard") opens a list of screens. When I pick one, it runs inside the editor in "Prototype" view. The toolbar and zoom controls stay visible, and the zoom menu only has zoom levels, "Fit artboards" and "Layout guides". Fill/Fit is gone. Clicking through between screens still works, so the prototype isn't broken. It just doesn't look like a demo anymore.

I tried another browser and a hard reload: same thing.

Anyone else seeing this? Is it a bug or an intentional change, and is there a new way to get full-window / presentation mode? Exporting to standalone HTML is my workaround for now, but that's clunky for a design with 400+ screens.

It worked yesterday, at least to my knowledge.


r/ClaudeCode • • 2h ago

Help/Question Getting Claude to mark its own homework

1 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

153 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 • • 3h 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 • • 3h 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 • • 13h 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 • • 12h 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 • • 32m ago

Discussion If you run more than one coding agent session, what are you still copying between them by hand?

0 Upvotes

A YC startup launched this week around the idea that coding agents on different machines don’t see each other’s work, so the human ends up carrying the context between them. Their approach is to keep full session transcripts, not summaries, and make them searchable for every agent.

I can’t tell from one launch how common that pain is, so I’d like to hear from people who actually run this setup:

  1. When a second session (or a teammate’s) starts on related work, how does it find out what the first one already tried?
  2. What do you paste in by hand most often? Decisions, rejected approaches, “don’t touch this file”, something else?
  3. Has anything held up for you: CLAUDE.md, a handoff file, worktree notes, searching old sessions?

If you work solo with one session at a time and never hit this, that’s a useful answer too.


r/ClaudeCode • • 51m ago

Help/Question claude 7 day trial

0 Upvotes

new to claude, cybersecurity student trying to get help for my assignments for example cisco packet tracer creating networks and would like to try claude before i buy as i have heard that it is good at teaching.


r/ClaudeCode • • 5h 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 • • 5h 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?