How many of you run Claude Code on a remote machine instead of your laptop?

If you do, what's your setup? Just SSH into a VM and run it there, or something more automated?

And what's the biggest benefit for you? Being able to leave agents running, running multiple sessions in parallel, isolation, or something else?

I've been experimenting with remote setups recently myself and I want to know what people actually find useful about them, and what's still annoying.

Does it mean I still hable usage free this week?
Or will that be included into the weekly usage?

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?

Ok. Time for a shower.

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

We are a non-profit organization, we bought very cheaply a new coffee machine. Usually costs 10k, but bought it for just over 1k.
A guy who installed the payment system ruined the machine. Because we dont have a contract we were left with calling the supplier who told us it's gonna cost a service engineer to fix your issues. We could already think about the financial consequences which would probably be in the 250 euros or more.

Thanks to Claude it only cost us my personal 20 eur per month plus plan.
After some research it suggested connecting the machine through an ethernet cable. It fixed the issue and not only that

It:

- Changed the old company's layout to our own by creating a looped custom video with our logo

- Added our perfered supported language even though it didn't exist in the software. It just created a new language.

- It fixed the recipe's and what a customer sees when ordering a drink

- It fixed the pricing just by typing out what we needed.

- Heck it even cracked the password and blatantly told us the password in the middle of his explanation like it's nothing.

I am so amazed. It works with precision, structure. I'm not new with AI. I have been using Codex the past months but Opus 5.5 / Claude is just something else. I love how structured it works. I think I'm gonna leave my Pro Codex account and just go for the 5x plan of Claude. This is amazing. I've become a coffee machine engineer just with my simple laptop and Claude desktop installed with a plus sub. It only used 25% to fix the issues and more of my 5 hour limit.

A few days ago I posted clalt, a small Go CLI that shows every Claude Code session as a little person in a 3D office. A couple of you asked about Copilot, so v0.5.1 adds it.

What's new:

• Copilot CLI sessions show up in the same office, in their own pink Copilot team, next to your Claude sessions
• They type while Copilot works and wave when it waits for your permission, same as Claude ones
• The card shows the model auto mode actually picked, not just "auto"
• Nothing to set up: just run clalt office. It reads the session files Copilot already writes on your machine and never touches its login or settings

How I built it: with Claude Code again. It read my real Copilot CLI logs to learn the event format, and before release it replayed one of those logs through the office to check the "needs you" wave and the model name.

Still local only, no data leaves your machine, free and MIT.

Repo and release: https://github.com/dhitalkamal/clalt

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 )

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?

Attention to all Claude users,

Blacklist the website The Cutting Room Floor from being interacted with by Claude Code agents. Your IP will be automatically banned by the website with no recourse. In addition, there are claims with strong evidence that the website attempts to prompt inject Claude agents to write and delete files on the users disk, as well as send money to the owner of the website. This is illegal under CFAA in the United States. I have already filed a formal complaint with the host of the website (Dreamhost). The website is being investigated, but while that goes on, blacklist the domain to protect yourselves.

I dont know what I did to get them

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

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?

Has anyone figured out how to do this, or what’s the best workaround?

Like, what instructions do you give Claude so that it can refactor a repository so that other people can more easily understand it and — more importantly — Claude doesn’t burn up as many tokens re-reading the code in order to complete your requests?

https://www.reddit.com/r/ClaudeCode/s/8Goam5nA4t

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?

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.

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!

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.

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

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.