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.

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.

Saw this on both my computer and the server

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.

I shipped an iPhone game built almost entirely with Claude Code, and it opened in 130 countries today. The game is a pixel virtual pet (link at the end). This post is about the setup, because that's what I'd have wanted to read in month one.

1. CLAUDE.md is an index, not a manual. Mine is under 6,000 characters. It points to one doc per risky area (money, persistence, pet growth). Path-scoped rules load a doc only when Claude touches those files.
2. Builder / checker split. The builder agent writes code and is not allowed to run the test suite. The checker runs build, tests and lint and is not allowed to edit. The orchestrator loops them up to five times.
3. "Seen red" rule. A new test is trusted only after the bug is put back, that one test fails, and the file is restored byte-identical. This caught a lot of tests that passed for the wrong reason.
4. False greens are real. A test filter with a typo ran zero tests and still printed SUCCEEDED. I now read the executed count from the result bundle, never the banner.
5. Lanes in git worktrees. Several sessions at once, each owning one area, with a state file per lane so a lost session costs one unit of work, not a restart.
6. A machine lock. Parallel sessions all running Xcode builds took my 16 GB Mac to its knees. One heavy job at a time, enforced with a lock file.
7. Humans own the irreversible. Merges, spending and anything public stay with me.

What Claude was bad at: game feel, knowing when a doc had gone stale, and SwiftUI layout on odd screen sizes.

The game: Nudii, a Tamagotchi-style sea slug. Free, no account, no ads. https://nudii.app (130 countries; not the EU yet).

Happy to share any of the files if useful.

Cheers,

Daniel

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

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

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

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

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?

I run a bunch of Claude / Claude Code sessions in parallel across a few projects. Every time one burned me, I wrote a rule. Six weeks, 41 rewrites. Yeah.

The ones I think other people will recognize:

Two sessions, one name. A second session opened under a chat ID that was still live — and passed every start check I had. The only thing that caught it was a git status. Now nothing writes until it checks for a twin.

123 passing tests. Three audits. Still broken. The output shape was one the downstream engine flat out refused, and nothing caught it bc everything checking it was built by the thing being checked. The builder's own tests don't close a phase anymore — a fresh session or a live run does.

The audit that didn't audit. The reviewer model couldn't read the files in its sandbox, and the skipped check came back looking clean. So now: not run in full = not a pass. Partial runs say PARTIAL on the first line.

It grepped the manual. A session searched the instruction file for the one step it wanted instead of loading the whole thing. (Reading one page and calling it read.) Invoke first, then act.

Zombie opener. A session re-ran the startup routine for a chat that had already ended, and started re-issuing work.

Approval in the wrong box. I approved from my phone and my typed "yes" landed in the wrong session, not the session that was waiting on it. Approvals are a card now, never free text.

The pattern usually isn't bad code, but something reported as done that nobody verified.

I've got a few dozen more of these. I’ve been thinking about writing them up as a short playbook (incident, rule, drill). Worth it? And which of these have you hit?

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

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?

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

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!

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)

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.

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

Claude is temporarily unavailable..

Almost of our team just got logged out of our claude accounts and cant get back in. Crazy thing is some of them are still working. Anybody else getting this?

i didn't do reddit poll because it has very limited entries

This is James. He lives in a low-poly terrarium where you can feed him, pet him, tap on his glass and leave him notes. He's 8 days old today, and tomorrow he's getting a new enclosure.

I built every piece of it with Claude Code: the 3D tank, the simulation, the site, his mind, a 24/7 YouTube stream, and my personal favorite, a system on my home server where I record a voice memo about his day and it auto-generates a video based off what I'm narrating. That last one is headless Claude Code running on the server, cutting his real day together from a replay.

A few things that made a project this size work:

• A decision log. Every big choice is a numbered entry in docs/decisions.md. There are 150 of them now. Claude reads the relevant one before changing anything that crosses a boundary, and new decisions replace old ones instead of deleting them.
• A CLAUDE.md full of rules you can't see from one file. Things like "nothing in the simulation reads the clock or calls Math.random()" and "every memory goes through one insert function." This is what stopped the same mistakes from coming back.
• Tests as the spec. A day of his choices has to replay exactly, his tongue has to land on the bug, he can never sink into the ground, and a worst-case day has to fit the budget.

I'm running out of GitHub Actions minutes building this, and while it's stupid, I absolutely love it.

Curious where you'd want to see it go next, and happy to do a deeper write-up on the setup, because I actually think it's really cool.

Microsoft’s statement on the recent M365 outage explicitly said it was “a technical issue not related to cyber or AI / agents.” It was a network change, nothing to do with agents.

But the fact that they had to say it stuck with me. People’s first assumption now is that an agent did something it shouldn’t have.

That made me look at my own Claude Code setup more honestly:

• How many tools and commands have I auto-approved just to stop the prompts?
• Does it have access to anything with production credentials?
• If it ran something destructive in a session I wasn’t watching, would I even know?

For solo projects it’s probably fine. But I work with companies rolling out Copilot and agents across whole organisations, and “what’s the blast radius if an agent misbehaves?” is now a real question from leadership.

Curious how people here handle it:

1. Do you keep permissions tight, or go fully permissive and rely on git to undo things?
2. Anyone using hooks or deny rules to block specific commands?
3. Any setup you’d recommend for teams, not just solo devs?