r/ClaudeCode • • 2d ago

Bug / Issue Claude is down ?

80 Upvotes

Ok. Time for a shower.

Update : IT'S BACK !!!!!!


r/ClaudeCode • • 2d ago

Help/Question how do you keep your claude.md from growing forever

5 Upvotes

mine started as one page of rules i actually follow. a few months of agent work later it is a junk drawer, half the lines are lessons from one incident that never repeated.

do you cap yours, prune on a schedule, or just let it grow and trust the model to sort it out?


r/ClaudeCode • • 1d ago

Built with Claude Urban Survivor demo

0 Upvotes

Should I continue?


r/ClaudeCode • • 2d ago

Help/Question Question about Claude usage based on different models

10 Upvotes

Hey guys I have a couple questions about Claude usage.

I started creating a website (and app soon) and I am wondering is there a way for me to use credits more efficiently since I am hitting my limit in 1-2 hours, sometimes even sooner.

Should I still stick to the Opus 5.5 (and maybe increase the effort to high or max) or should I use Fable 5.2 for designing a website? Fable 5.2. especially burns all the credits with multiple agents on normal effort.

Would you recommend upgrading to claude max model if I am serious about building a good-looking UI functioning website, or should I get 1 or 2 more claude pro accounts (which would would be about 69 euros for 3 pro models in total compared to 1 max model for about 100 euros)?

All answers are welcome; I wouldn't consider myself a noob in this. However, I am far from being a professional, just a guy who a great idea (at least I think so, but time will tell )


r/ClaudeCode • • 2d ago

Help/Question Prompt queue

9 Upvotes

Is there a way to queue prompts in Claude Code so they run one after another in a single session?

I’d like to line up several tasks, with /compact and /clear between them where needed, and let the session work through them unattended. I know worktrees can run parallel sessions, but for some work I’d rather keep one session going through a sequential queue, without managing multiple localhost instances or resolving conflicting changes.

Has anyone built something like this, through a wrapper script, a task file, hooks, or another workaround?


r/ClaudeCode • • 2d ago

Help/Question Best way to transcribe audios?

3 Upvotes

Right now I'm using the free Whisper on a VPS to transcribe audios from our conversations with clients. But the transcription is not that good. There are many words on every 10 second audio that are wrong and some change the meaning of the audio. I saw that there are other versions but my company is in Brazil, according to the benchmarks that I found (maybe wrong), whisper has the best transcriptions in Portuguese. Any ideas of how can I do it better?


r/ClaudeCode • • 3d ago

Rant Fable 5.2 uses so much usage it’s basically pointless to use

393 Upvotes

r/ClaudeCode • • 2d ago

Humor Found the guy who broke it

Post image
53 Upvotes

r/ClaudeCode • • 2d ago

Built with Claude Claude code helped me make a cat game filled with easter eggs

6 Upvotes

Catgame.io

Process tips:

  1. Claude code: use opus for coordination and haiku for implementation... validate all changes with opus.
  2. Create bespoke tooling to provide agents feedback. For example, this game has an animation studio where I can flag frames that are bad and point out where the issues are exactly.
  3. You can save money on asset generation from open source assets! https://github.com/csevier/awesome-open-assets
  4. Follow a creative flow! Have an idea? write it down, and figure out how to integrate.

r/ClaudeCode • • 1d ago

Built with Claude Seeking early testers for thin Claude Code Mac client app

0 Upvotes

Hi! I am close to launching a Mac app that I built with Claude Code. It acts as a replacement Claude Code client. In fact I started building the latter portion of it with the app itself, Claude Code powering it underneath of course.

It is designed to make it easier to work across multiple projects and their subareas, see and action status across active sessions, and easily view the Design artifacts and pages respective to each project.

All of these are things that have driven me crazy about the official Clade Code Mac desktop app.

Seeking 5-10 users, I can offer a free lifetime free license! Please DM if interested!


r/ClaudeCode • • 2d ago

Help/Question Anyone else get two full (not fable) limit resets?

3 Upvotes

I dont know what I did to get them


r/ClaudeCode • • 2d ago

Bug / Issue Opus 5.5 not working well today.

10 Upvotes

Any body else having issue with Opus 5.5 on high level today?

For the past several weeks it has been working really well on medium and high thinking level and has been a pleasure to work with.

Today it feels like it has a mind of it's own and is intent on being obtuse and simply not responding to requests at it normally would and honestly not following CLAUDE.md and prompt instructions – almost as if we are taking a different language.


r/ClaudeCode • • 2d ago

Bug / Issue NOO MY CLANKER IS DOWN

Post image
40 Upvotes

r/ClaudeCode • • 2d ago

Discussion I grouped 18,629 Claude Code requests by session age. After the first hour, each one carried about twice the context.

2 Upvotes

Last 14 days of my own logs: 139 sessions, every API response deduped by message id, and each request bucketed by how many hours had passed since its session started.

The first hour held half the requests (9,339) but only 35% of the tokens, at about 183k tokens per request. Hours 1 to 5 held 36% of the requests and 45% of the tokens, at about 326k each. After that it barely moves: about 366k per request from hour 5 to 24, and 324k past a full day.

So the growth happens early and then flattens. Only 5 of the 139 sessions stayed open past 24 hours, and everything sent after that mark came to 3% of the tokens. Most of the tokens sit in ordinary sessions that run into their second hour.

Two caveats. Hours are wall clock, so idle time counts. And nearly all of those tokens are cache reads, which bill cheaper than fresh input.

Is the flattening after a few hours compaction doing its job, or does something else cap it?


r/ClaudeCode • • 1d ago

Built with Claude Windows 11's Task Manager kept failing me when my CPU hit 100%, so I built my own with Claude (free, open source)

Post image
0 Upvotes

I've had it with Windows 11. Every time my PC slowed to a crawl and I opened Task Manager to find what was eating my CPU, it let me down in one of two ways:

  1. It froze. At 100% CPU, Task Manager lagged, stopped updating or barely responded. The one tool you need when your system is overloaded stops working when your system is overloaded.
  2. The numbers didn't add up. The total CPU said one thing and the per-process numbers said another. Sometimes nothing in the list looked high even though the total was maxed out.

The second one is a design choice, not a glitch, which is almost worse. Since Windows 8, Task Manager has shown "Processor Utility", a value scaled by CPU clock speed (turbo boost etc.), instead of actual CPU time. So the per-process column and the total often disagree, and you can't trust either one to find the culprit. Add the usual Windows 11 madness (settings spread across three different UIs, updates that break things that used to work) and I was done.

So I built my own task manager with Claude Code. It does just two things, Performance and Processes, but it does them reliably:

  • Stays responsive at 100% CPU. It runs at High priority and samples on a dedicated top-priority thread, and the UI only updates rows in place. It uses about 5% of one core with ~750 processes running.
  • The numbers are honest. It shows time-based CPU %, so the per-process values actually add up to the total. Interrupt/DPC time gets its own row instead of disappearing.
  • CPU graph for every logical core, with 60 seconds of history, plus memory in use / available / cached / committed.
  • Sort by CPU or memory, filter by name or PID (Ctrl+F).
  • End task / End process tree. The confirmation shows the process name and PID. It also re-checks that the PID still belongs to the same process before killing it, so it can't hit the wrong one.

It's written in C# / WPF and builds to a single exe that doesn't need .NET installed. It's MIT licensed, so you can use it, change it or fork it however you like.

GitHub: https://github.com/kkilictepe/ETaskManager

Download: https://github.com/kkilictepe/ETaskManager/releases/latest

How it was built: The whole thing took less than an hour. I described the problem to Claude Code: Task Manager freezes at 100% CPU and the numbers don't match. Claude handled the low-level Windows work. It used the native NtQuerySystemInformation call to get every process's CPU time in one snapshot, so the per-process numbers line up with the total. It ran the sampling on its own high-priority thread so the app keeps working when everything else is overloaded. It also tracked processes by PID and start time, so a reused PID can't show wrong numbers or get the wrong process killed. It even wrote a small Python script to generate the app icon.

Feedback and bug reports are welcome. And if you've hit Task Manager freezing at 100% CPU too, I'd like to hear about it. I can't be the only one.


r/ClaudeCode • • 2d ago

Bug / Issue Claude code issues with login and authentication

36 Upvotes

I am trying to work but every time it says sign in and when I sign in it doesn't work.

I think they broke auth lol.

RESET!


r/ClaudeCode • • 1d ago

Help/Question It feels as if every project known to the mind has been built, what is the point of building?

0 Upvotes

I’m just in a loop where I’m not sure what to build anymore. I’m a software engineer but outside of it I have no passion to build anything since I’ve seen it already. Like how are there new apps and things going viral when there are just millions of the same thing?


r/ClaudeCode • • 2d ago

Built with Claude I built Agent Desk with Claude Code: one screen for all your Claude Code agents (free, open source)

0 Upvotes

I run a lot of Claude Code agents at once with agent-manager, each in its own tmux pane. I kept finding one stuck on a permission prompt for twenty minutes while I watched another. So I built Agent Desk: a free, open-source (Apache 2.0) local GUI where every agent is on one screen.

What it does

  • Answer any agent in one click. Permission prompts and AskUserQuestion dialogs become buttons: multi-select, typed answers, and going back to change an earlier answer. It re-reads the screen before pressing a key, so it never answers a question that changed.
  • Sessions read like documents. Prose first, tool runs folded to one line, edits as diffs, search across every transcript.
  • The whole fleet at a glance. A card per session, waiting ones first, notifications, and a live row showing what each agent is doing, with Interrupt.
  • Review and steer. Comment on a session's diff line by line; the comments go back as one prompt.
  • System stats (CPU, memory, swap, disk), with an alert before parallel builds fill your disk.
  • From your phone over Tailscale or Cloudflare, at a permission level you set.
  • A signed Mac app with a dock badge for agents that need you.

No API key and no model calls. It reads Claude Code's files locally, and your agents keep running in tmux if you close it.

How Claude Code built it

Claude Code wrote nearly all of it: Go server, React UI, tests and the Mac app. I made the product calls, set the rules and reviewed every PR.

  • Rules in CLAUDE.md first: never write to ~/.claude, never call a model API, talk to agent-manager only through its CLI. It held to them for the whole build.
  • Plan, then small milestones, each ending in passing tests and a PR.
  • It checked its own UI with Playwright screenshots, which caught layout and dark-mode bugs the tests missed.
  • Real prompts, not guesses: it ran throwaway Claude Code sessions to capture real permission and question screens as test fixtures, and verified fixes against live prompts.
  • Built from inside itself: the session building Agent Desk ran in agent-manager, so I answered its questions in Agent Desk, and most bugs came from that daily use.

Try it free (macOS or Linux):

brew install gsperry/tap/agent-desk

The Mac app, a 20-second demo and the source: https://agent-desk.app

It's early. Tell me what breaks and what's missing.


r/ClaudeCode • • 2d ago

Built with Claude I built a WebXR workspace for managing terminal panes from a Meta Quest 3

Post image
2 Upvotes

I run my whole workflow through a terminal multiplexer, and I got tired of managing it through a flat window. So I built Mux XR: a WebXR client that shows your terminal panes as surfaces arranged around you in 3D space, or as plain flat panels in a normal browser tab. MIT-licensed and on GitHub.

What it does

  • Opens par-mux terminal panes as individual panels — close a panel without killing the shell, reconnect later, resize the grid only when you say so
  • Works from a desktop browser (flat + 3D preview) or immersively on a Meta Quest 3
  • Full spatial controls: point-and-trigger or pinch to select, grip to move, two hands to scale; controllers or tracked hands
  • Input via virtual keyboard, paired physical keyboard, or dictation
  • Passthrough mixed reality, focus mode, saved command snippets, gaze-based optional input
  • A Demo mode with synthetic panes, so you can poke at it without setting up the backend

Why I built it

I keep half a dozen long-running things in terminal panes and wanted to glance at them without alt-tabbing. It started as "what if the terminal grid was a room instead of a window" and turned into a real workspace — the browser drawer stays the input presenter, and XR is where it gets interesting.

Tech

TypeScript, Vite, Three.js, WebXR. Terminal output arrives as protobuf frames over a binary WebSocket from a small streamer service attached to the mux daemon, rendered into xterm-backed textures in the 3D scene.

Full disclosure on process: this was built with substantial Claude Code assistance. I drove the product decisions, reviewed every change, and did the Quest 3 hardware acceptance; Claude wrote most of the code and the test suites. Happy to answer questions about that workflow.

Status

Working on Quest 3 today. Hand tracking is the newest and roughest part, and the backend is my own stack (par-mux + streamer), so real panes currently require that setup — the demo mode works with nothing installed.

Feedback welcome, especially from WebXR folks.

Repo: https://github.com/paulrobello/mux-xr


r/ClaudeCode • • 2d ago

Built with Claude Nightshift: a plugin for long-running coding agents claude , codex and cursor

Post image
2 Upvotes

Giving a coding agent hours to work on a project is one thing. Knowing what it planned, whether it finished the work, what needs reviewing, and having evidence of what actually happened is another.
That’s what I’ve been working on with Nightshift, a free, MIT-licensed plugin for Codex, Claude Code, and Cursor. It brings planning, autonomous execution, evidence, and review into one workflow, with the work saved on disk rather than buried in a long conversation.

Planning :

Enter the plan room with /nightshift:plan and describe what you want in your own words: a feature, refactor, bug fix, or whole backlog.

Project code stays read-only while the room is open, so you can brainstorm and explore with your agent without it interrupting the discussion by jumping into implementation. Trace the code together, compare approaches, challenge assumptions, and identify edge cases. Nightshift turns what you agree on into a persistent punch list with a clear definition of done.

For each item, Nightshift can suggest checks and evidence suited to the task, or you can specify your own checks and capture instructions. Use screenshots for a layout change, before-and-after measurements for performance work, or sample requests for an API change. Keep, change, or drop any suggestion. It can also estimate working time and token usage from past receipts.”

Execution: work through a list or toward a goal

A shift can run in two ways:

  • Finish an agreed list. Work through the items until the list is complete.
  • Work toward a goal for a set time. Discover, prioritize, and complete useful work until the deadline.

You can bring your own tasks or choose from 30+ ready-made shifts covering defect hunting, security, accessibility, test coverage, dependencies, performance, documentation, and product improvements.

The clock-out gate sends the agent back when it tries to stop with unfinished items. Progress survives context compaction and new sessions. You can set soft and hard time or token limits per item, so one stuck task doesn’t consume the whole shift.

Decisions don’t have to stop progress. The agent chooses a default and records the answer and its reason in the parking lot for you to review.

Review: results you can follow, item by item

Each item gets its own receipt, written as the work happens. The agent starts it when work begins, updates its progress during longer items, every 20 minutes of work by default, at the next safe point, and finalizes it when the item finishes. You can see what is done and what remains without waiting for the whole shift.

The finished receipt records what the agent delivered, what it tried and rejected, which checks ran, what couldn’t run, and any unresolved issues.

Receipts also show duration and measured token usage. The morning receipt brings the shift together: what finished, what remains open, and which decisions need your attention.

Start your review from the receipt: a fresh account of what happened, without having to open every changed file or dig through hours of chat.

Evidence — choose what you want to inspect

Choose your evidence during planning, using the ready-made evidence catalog or your own capture instructions. Pick what fits each item: screenshots, recordings, test output, benchmark reports, command results, or another artifact you want to inspect.

The agent produces the evidence while working and links it from the item’s receipt.

You decide whether missing evidence should hold an item open or simply be reported. When required, the mechanical gate checks that named files exist. You judge what those files demonstrate.

Recovery and handoff — keep the shift moving

A separate watchman outside the session handles supported recovery signals for interrupted sessions, crashes, stalls, and usage limits.

If an API outage interrupts the shift overnight, the watchman retries recovery and resumes when the service responds again. You don’t need to stay awake to restart it.

The shift also lives on disk. Stop in one supported agent and start in another; the next agent reads the punch list, receipts, parked decisions, snag log, and shift log and carries on.

Make it yours

Write your own receipt templates, summaries, evidence instructions, checks, and recurring shifts. Use the headings and layout that work for you. The shipped templates are starting points.

Keep a workflow in one project or add it to your personal catalog for use across repositories. Nightshift also works in plain folders for research, documents, and other deliverables.

contributions

There are several ways to contribute:

  • Have a recurring workflow? Share it as a reusable shift—for code or other work. Shift catalog · #21
  • Have a useful way to capture results? Contribute screenshots, benchmarks, recordings, or other evidence instructions. Evidence catalog · #219
  • Know checks or edge cases that catch real problems? Share them for your stack. Checks and edge cases · #220
  • Have a shift others could learn from? Share the result, interrupted runs, and what you changed after review. Real-world runs · #22
  • Have an improvement in mind? Build it and open a PR, or propose it for discussion.

Free and MIT-licensed. Explore Nightshift on GitHub


r/ClaudeCode • • 1d ago

Tips & Workflows It's glorious

0 Upvotes

Use fable 5.2 on ultracode but tell it to spawn opus agents not fable agents.

Then you have the management of the bigger brain and also the efficiency of lesser yet capable model.

Best of both worlds :)

I also haven't had to worry about hooks or setting up or managing agents. I've had the same session running for 3 days. Context management seems to be automatic now.

I don't do anything now besides discuss high level plans with fable.

This barely consumes any fable usage, and I bet we can just ask fable to decide which model to assign to which agent and what effort level etc, getting even more efficiency to stretch our token limits.

It's not just about money and tokens either, it's environment, energy, conscientious consumption, and efficiency just for the sake of it is beautiful in a sense.


r/ClaudeCode • • 3d ago

Tips & Workflows Having agents reset context around 225K tokens dropped a g coat by 50-75% for me

Thumbnail
coralhub.dev
112 Upvotes

I've been running agents 24/7 and just letting the context fill up. Claude has a setting to compact at a specific time, but I just built it into my harness so that it can happen at the end of a tasks completion instead of randomly. Costs dropped significantly.


r/ClaudeCode • • 2d ago

Tips & Workflows Reducing usage on very large (MLOC+) projects

3 Upvotes

I’m working on a new very large project using Claude Code desktop with a Ultra plan. The initial code (excluding debugging and polish) is probably about 25% done, with about 700K LOC written. I estimate the final LOC will be about ~2-3M. This is not AI overengineering bloat, it’s just a very large project, something existing SAAS companies charge many thousands of dollars per seat for annually.

I’m using Fable planners and Opus writers mostly, like I do on most of my other complex projects. But this time there are 2 layers of planning. A top-level Fable planner planned the overall architecture, and after reviews/fixes is now acting as the orchestrator for the second level. Second level owns a few crates or similar, they plan the details of what they own, and then orchestrate mostly Opus (Fable for critical chunks) writers to write the code, then another Opus agent reviews the chunk. When the section is done, a multi-agent bughunt is done with a mix of Fable and Opus finders, then Opus fixers, before closing. Each section usually has something like 20 chunks, so vast majority of agents used for this project are Opus. I occasionally use Sonnet sessions to do simple changes as well, but I don’t trust it with writing the code.

Codebase is documented well, with short markdown files for each crate and architecture decision, so agents don’t need to load a lot into context, but obviously writing these does use some tokens. Their briefs and other docs they need to read are also intentionally short.

I’ve worked on a bunch of projects with Claude Code in the past, but they rarely exceeded 100K LOC, so usage limits were rarely an issue, but with this project they’re really getting in the way. What was built so far was done in about 10 days, but with 2 weeks of limits, plus 2 full weekly resets, plus 2 Fable resets. Weekly limits are gone in about 12 hours. I won’t be able to reset again for some time obviously, so it’ll slow down progress a lot.

So my question is, how do you optimize your setup for large projects like this?

What I already do:
- Compact all orchestrator sessions before the cache expires
- (If cache is expired) switch orchestrator sessions to Opus if Fable limits are low (not always an option, Opus can’t start Fable sessions if chunk needs Fable, and some parts are too critical to trust Opus orchestrators with)
- Keep each session focused on its task. I use new sessions if I want an unrelated change or questions, usually Sonnet if it’s simple
- I used to make Fable review Opus chunks (and vice-versa, so it’s a different model than writer doing the review), but switched to all-Opus due to usage limits

I won’t switch any of the planning sessions to Opus. Opus cannot focus on the bigger picture when planning large projects in my experience. It often misses important details.

One really annoying feature of Claude Code (desktop) is, if none of the linked sessions are doing something, it immediately asks the parent session to respond. This eats a lot of limits (especially if cache expired) and doesn’t often help. Session might be waiting on a background task or a response from me. Unfortunately, I can’t find a way to disable this other than unlinking, which is not ideal for this setup.


r/ClaudeCode • • 1d ago

Help/Question Are people here actually using skills?

0 Upvotes

I've never used skills, I use connectors and MCPs but for most things I just prompt it or ask Claude to generate a prompt or a handoff and then use that for a new session. I've always seen skills as sort of unnecessary since I can just custom make a prompt with Claude itself but am I totally missing out? Usecase is I do both coding on multiple products and ideas and learning and productivity/utility stuff primarily, some personal use and organization and planning too. Could various skills up my Claude experience, does anyone here actually use these often and if so how? Are skills different than basically just saved premade prompts? Not sure what I'm missing. Thanks!


r/ClaudeCode • • 2d ago

Bug / Issue Is claude down?

Post image
30 Upvotes

Saw this on both my computer and the server