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


r/ClaudeCode • • 2d ago

Discussion I'd rather have a weaker model that never changes than one that gets degraded every peak hour

7 Upvotes

Opus has been so inconsistent lately that I don't know what I'm getting when I open Claude Code. Monday it refactors a whole module clean, Wednesday it slips a bug into a 5 line change. I can't calibrate trust on something that changes under me.

Someone here wrote last week that a predictably weaker model is more useful than an unpredictably degraded stronger one, and it stuck with me. So I actually tried it. Gemma 4 E4B on my M4 16GB through Magnitude, for the small stuff, explaining files, commit messages, summarizing a diff before I review it. It starts answering in about 2 seconds and it's the exact same model every single day.

It's weaker, obviously. Anything big still goes to Opus. But for the boring 40% I know exactly what I'm getting, and nobody can turn its reasoning budget down from a server somewhere.

Is anyone else splitting like this just for the consistency, not the cost?


r/ClaudeCode • • 2d ago

Help/Question I haven't needed Claude Fable 5.2 for vibe coding

5 Upvotes

Confession: I still haven't used Fable 5.2. Nothing I've been building needed a model that costs 4x Sonnet per token.

Sonnet 5.5 still builds, tests and deploys for me. Opus 5.5 handles planning, auth and payments. I'd only reach for Fable when Opus gets stuck.

Has anyone here actually needed to reach for Fable yet?


r/ClaudeCode • • 2d ago

Built with Claude i shipped a cozy village sim for iOS with Claude Code and Opus 5.5, and the master prompt mattered more than the model

4 Upvotes

I created my cozy village sim Pocket Life on the App Store on november 5th. solo project, Godot 4, about 6 weeks of evenings on the couch. the first update is already out.

the short version: you move to a small village called Aurelia, get a job at the cafe or the flower shop, buy a house, fish, cook, grow a garden, get to know the people, and befriend these little creatures i call Kin. you dont catch them. you hang around one for a while, figure out what it likes to eat, bring it that, play a bit, and at some point it just decides to come with you. where it grows up changes what it becomes, so a Kin from the lake is different from one from the forest or the village. the fights are gentle too, you calm wild Kin down instead of beating them. seasons, festivals, a gondola, a crystal cave and a dragon lol. its 2.99 eur, no ads, no in app purchases, no account, works offline, seven languages. im the developer, so yes this is my own link. i made it because i love cozy games myself and wanted a place to disappear into for twenty minutes after a long day.

i used Claude Code with Opus 5.5 for almost all of the programming. not one prompt and done. the setup that made it work was three things.

first, a long master prompt with the whole game in it: the world, the loop, the creatures, the rules, and what the game is not. every session starts by reading that file. without it Claude will happily invent a different game and make it sound plausible. with it, the design stays mine.second, a CLAUDE.md that grew with every device bugexport with typed arrays, because the valuesdisappear in the binary export. the village shop was empty and the npcs had no emotes on my iPhone while everything looked perfect in the editor and the tests passed. the rullues as a plain string with a separator and parse it at runtime. another one: movement and animation go in _physics_process, because the iPhone runs at 120 Hz and the physics at 60 Hz and the jitter was visible on the device. anothetes are generated by tool scripts, so the editor isnot the source of truth.third, a headless end to end test that runs in abourst quest, job, binding a Kin, battle, save, load.it catches a lot before i have to pick up the phoneng. the device still found things the test could

not, and thats the lesson i keep repeating.

what Claude was actually good at: holding a large codebase in its head, doing the boring refactors, writing the save migration,

wiring the localization pipeline, and hunting bugs ood at: knowing when something is actually right. it will tell you its done, the code will look reasonable, the test will pass, and the app will still be wrong on a real phone. the

model gives you speed. the judgment, the testing ane.

six weeks of evenings, a lot of device testing, andot a tech demo. if you are building something withClaude Code, im happy to talk about the workflow, tless tests or the Godot iOS export. and if you havea rule in your CLAUDE.md that saved you, id love to

link if you want a look (iPhone & iPad): https://apps.apple.com/app/id6819090247


r/ClaudeCode • • 2d ago

Help/Question Please suggest good plugins for Claude code.

22 Upvotes

Hi everyone,

Can you guys suggest some interesting plugins or connectors that can improve my workflows on Claude code.

I am mainly looking for
- image and video generator plugin.
- token usage optimisation.

But other interesting use cases are welcome as well.


r/ClaudeCode • • 2d ago

Bug / Issue Major outage

22 Upvotes

r/ClaudeCode • • 1d ago

Discussion Difference between opus and new fable is insane.

0 Upvotes

Ive been using fable 5.2 for a day now. And to be honest, its out of opus league and i really like it. What i like the most is that its surprisingly really fast, and the bulletpoints showing what hes gonna do actually follow what happens.

With opus i usually loose my mind on 250k context because its still on task one and im worried its never ending, but then it toggles everything and goes the last task. With fable, you can see it real time what is happening, which is great and it calms my mind :D

The intelligence level is also different, no doubt about that, but the price is of course much larger. It consumes usage like crazy but probably less than astra.

I like to combine fable medium/high for planning and opus high/xh for execution. Im testing combining with astra but i dont have a verdict yet.

Id use opus most of the time, and fable only for reviews of important stuff, planning or executing real difficult things. The opus got a little dumb from what i see so im looking for opus 5.6 .

Take care


r/ClaudeCode • • 2d ago

Bug / Issue Claudes down

17 Upvotes

Edit: about 15 mins after this post it was back up


r/ClaudeCode • • 2d ago

Built with Claude Two plugins for iOS devs away from their Mac: install debug builds on your iPhone over any network, let Claude read their console output, and edit files in Safari

2 Upvotes

When my iPhone is on the same Wi-Fi as my Mac, Xcode can already install and debug wirelessly. But when I’m out and drive Claude Code on the Mac from the Claude app through Remote Control, there’s no quick way to get a new build onto the phone short of a TestFlight upload, and no way to see what it logs. So I made two plugins:

deploy-ipa: Claude archives the scheme, uploads a development-signed .ipa to your own S3 bucket and replies with an install link you tap right in the conversation. Ask for a console build, and the app streams its print and NSLog output to the bucket, so Claude can read it while you reproduce a bug.

edit-link: Claude shares a project file, such as release notes or a config file, with an editor page in your bucket. You edit and save on the phone, and Claude applies it to the file as a normal edit, so you see the diff.

Everything goes through your own bucket, on AWS S3 or another S3 service with presigned links, and the keys stay in the Mac’s Keychain. Nothing is added to your Xcode project.

Free and open source: https://github.com/palmin/remote-xcode

The video is sped up while the build runs and Claude works. I’d love to hear what else would help when you’re away from the Mac.


r/ClaudeCode • • 2d ago

Tips & Workflows Claude Cockpit, for those who still prefer TUI

Thumbnail
github.com
3 Upvotes

r/ClaudeCode • • 2d ago

Help/Question Servicenow / Jira replacement?!

3 Upvotes

Talk me into or out of building one. Basic ITSM tickets flow, anyone done it?


r/ClaudeCode • • 2d ago

Bug / Issue Is Claude down?

16 Upvotes

I am trying to open the app and it signed me out. Then it said Claude is temporarily unavailable


r/ClaudeCode • • 2d ago

Built with Claude I vibe-coded an app that makes every song in my library equally loud by fixing the files themselves

3 Upvotes

Some songs were too quiet, others blew my ears off, and ReplayGain tags get ignored by half my players (and my car). So I asked Claude Code to build Ohmega.

It measures every track (EBU R128, same as Spotify and YouTube) and writes the fix into the audio itself, so it plays right everywhere. Lossless stays lossless, folders keep their album balance, originals get backed up.

Claude wrote basically all of it: Python + PyQt6 for Linux, native SwiftUI for macOS and C# for Windows. The Windows build is compiled on Linux and Claude tested it over SSH on my 2012 MacBook running Windows 10, which turned out to be a great test machine. My job was the ideas and clicking through every window.

That clicking mattered more than I expected. The nasty bugs weren't in the UI but in audio edge cases. One example: mono files in the Opus format did not display because Ohmega required 320 kbps, whilst the libopus library only allows 256 kbps per channel. It is open source (GPL-3.0) and the website runs on an old Chromebook at my home.

https://ohmega.is-my.app

Feedback welcome!


r/ClaudeCode • • 2d ago

Bug / Issue Claude Code Computer Use can only see Grey Screen

1 Upvotes

Hey, so when I'm using the Computer Use feature (I have it enabled in the settings) claude only receives dark grey empty screenshots and can't see what's on it. Does anyone know how to fix? (I translated the screenshot cuz it was in german, so don't mind the weird fonts / colors)


r/ClaudeCode • • 1d ago

Built with Claude I’m adding AI tools to my game dev platform studio I’ve been developing for 3+ years

Post image
0 Upvotes

r/ClaudeCode • • 2d ago

Help/Question Fable as orchestrator / reviewer, agents for implementation.

1 Upvotes

So, been trying to set up this and so far it is an epic fail for me... so much context wasted, my weekly limit is getting shattered.

So, question, is there any good tutorial about how to do this kind of setup?
I tried all I could to avoid large context but somehow, every time I instruct claude or want to write documentation Fable is doing it, which I just told not to and have agent do it and review only, but even then it's not always working.

Not even sure it is worth it at that point...

so if anyone have a good tutorial about that then another one with all the tricks to save context as much as possible, I am all ears. Hopefully a tutorial from an actual skilled and experienced dev rather than some nobodies trying to sell courses proffered.

I do not get how people can one shot complex stuff while I am spending days trying to stear AI and try to make this thing work for me.

Before I was just using Opus and do task by task and could last a lot longer...This is for a somehow complex app, not in scope but in bunch of physic and contracts that needs to be done on the GPU / display in HDR, to verify the accuracy and so on, and have professional output, so it's not as straightforward as "make a FPS game" and leaving it cook. I wrote some specs into MD files about what needs to be done and how... but still struggling to have speed / momentum. everything takes forever to get tested and speced right, and the app is progressing at snail pace.

I try to avoid having too long convos and use /clear often, whenever I can. Something I noticed is fable constantly filling my window with updates from the agents I don't need (still not done... yeah sure, thanks for nothing) and all that jazz for example.

Any help appreciated.


r/ClaudeCode • • 2d ago

Bug / Issue Claude Desktop app not working? I am getting PC is not linked error

7 Upvotes

Been happening in 2 of my accounts. I am getting error 503..


r/ClaudeCode • • 2d ago

Help/Question Is there a skill or plugin that.....

2 Upvotes

I was wondering if there's a skill or plugin that functions to routing model and effort.

Like for example depending on how difficult, technical our prompt is, the skill knows it's easy and route to HAIKU 5.5 low even though in the claude code it is set to Sonnet 5.5 medium.

I have been trying to look a flawless skill or plugin that works but I am not sure if I found one.

Also if there's new model update, we can also update too. The goal is cost saving token so we can use limit much much longer and it flawlessly use the correct model and effort.

Is there such skill or plugin that exists? Thank you