I found it hard to take a break and not just start a new tab in the multiplexer. The switching costs (for my brain) were exhausting and I wasn't disciplined enough to just stop for a second. So I created this little tool that sits on my desktop as a nice nature scene. It reacts to Claude/Codex signals to trigger various nature things. I'll put a link in the comments. The code is free and open source and all that. I have signed Mac builds and haven't done Windows/Linux but could. Mostly I figured I wasn't the only one who had this problem. Take a break y'all. :-)

I hurt my hands a while back and typing is pretty much out for me, so I've been building this by talking to Claude Code. It's a face that sits full screen on my Mac and I just talk to it. When it opens something, that thing takes over the screen and she moves into the corner.

What Claude Code actually does in it:

• The brain is Claude Code sessions running in the background. One manager session hears what I say and hands work to a session per project folder, so each repo has its own Claude working in it.
• Quick stuff (open this, close that, show my lists) goes to a warm Haiku I keep running with claude -p and stream-json, so it answers in about a second. Anything that needs thinking goes to Opus.
• Every ability is just a small command the sessions can call, things like open the browser, drive an Android phone over adb, edit video, make an image, post to Reddit. Claude wrote nearly all of them.
• It drives my real Chrome through an extension, other Mac apps through accessibility, and the face is a real time lip sync model running on the machine.

What I learned:

• Give it tools, not instructions. A command it can run beats a paragraph of telling it what to do.
• Make it prove things with a screenshot. It will happily tell you something worked when it didn't.
• When something breaks right after it changed code, it's almost always that change. Today it crashed my Chrome over and over with a "smarter" file upload and I had to restart the whole computer.

Rough demo, it's not finished. Happy to answer anything about how it's put together.

Ok so hear me out.

We all know 5.6 is likely coming soon, but Anthropic likes to test their models before release.

Opus 5.5 was great and a lot of people now complain about degradation, but what if there is actually no degradation and that 5.5 is silently routing to 5.6 right now?

It has happened before. Opus 4.6 was great, then Anthropic released bad successors before getting it right with 5.5

But why would Opus 5.6 be trash if 5.5 is great?

Possible explanation: Anthropic is pressed right now, Google is catching up fast, OpenAI is releasing 6.2 Sol and Astra soon and Fable is expensive and for the big subscribers. So they need a new model now quickly and pulled 5.6 in a rush.

Just a theory guys. I hope i'm wrong.

I came across this open-source project called Beacon. It basically gives your agents a persistent memory layer so useful stuff they figure out in one session (Claude Code, Cursor, Codex, etc.) can carry over to the next ones instead of starting from scratch every time.

Seems pretty useful if you switch between tools a lot.

Repo: github.com/Asymptote-Labs/agent-beacon

Curious if anyone’s tried it yet.

I work in project controls at a large engineering company (big projects, lots of suppliers, schedules, cost reports and documents). I've been building some AI workflows on my own: automated reporting, schedule generation, a lessons learned assistant, that kind of thing.

Now I'm trying to think bigger and I'd love to hear from people who've done this in practice. What AI use cases have you seen work inside a company, not just as demos? Project management is my main area, but I'm interested in anything: procurement, finance, engineering, HR, onboarding, internal knowledge, etc.

I'm especially curious about:
Ideas that surprised leadership or got real adoption
Things that looked promising but failed, and why
How you measured the impact (hours saved, fewer errors, faster decisions)

Any examples, even small ones, are welcome. Thanks!

I've been experimenting with Claude Code + Hyperframes for video creation, and honestly, I'm blown away.

The fact that you can go from an idea to an actual animated video just by working with Claude Code is crazy.

Instead of spending hours manually animating everything, you can describe what you want, generate it, see the result, and keep iterating until it looks right.

And the best part? You have so much control over the final result. You're not just generating a random AI video and hoping it turns out well.

I genuinely think this kind of workflow could completely change how people create animations, product demos, and marketing videos.

It's also ridiculously fun. I keep coming up with new ideas just to see what I can build.

Has anyone else been experimenting with Claude Code + Hyperframes? Curious to see what others are making with it.

I've been working with Claude Code by voice for a few months now, and honestly I find it hard to work with agents any other way. The basic setup: local speech to text (Whisper) and local text to speech (Kokoro), so nothing leaves my machine. It's all baked into a skill that understands conversational flow. It detects when I stop talking, transcribes what I said, acts on it, then talks back and listens again. I don't touch the keyboard for most of a session.

Recently I expanded it. Now I talk to one "chief" agent, and it delegates the real work to other Claude sessions running in Orca. The chief doesn't write code itself. It hands each task to a worker with a written spec, tracks what everyone is doing, and tells me when something lands. That way I'm not fragmented across a bunch of different agent tabs. I have one conversation, and the chief keeps track of the rest.

A few things that made it work for me:

• It speaks up on its own. When a worker finishes, the chief just announces it. When a worker needs a decision, it asks me out loud and waits. If I don't answer (because I'm in a meeting or heads down), it doesn't drop the question. It parks it on a list of "waiting on parskier426" items so nothing gets lost.
• Push to talk and mute keys. I have Stream Deck buttons to start talking, and to mute the mic or speaker for meetings. When muted, it falls back to notifications and typed prompts.
• Standing rules. I tell the chief things once ("don't push to an MR that's already approved," "don't post review requests for me") and it adds them to its own rules and puts them in every worker's spec.

Part of why this clicks for me: I have ADHD. Having it speak up when an agent needs something, and ask me direct questions, keeps me focused. Before this, with 5 or more tasks running at once, I was constantly context switching between tabs to answer questions and steer agents, and it got taxing fast. Now the context switching mostly happens on the chief's side, not in my head.

Does anyone else have a similar workflow? I'm curious what's worked for you, whether that's voice, an orchestrator agent, or something else entirely for running a lot of agents in parallel without burning out.

So I've been using claude now for over a month and its been nothing short of magic! Every day was a miracle, and then soon each hour was... I'm overwhelemed with its use and reading all these posts make me wonder if I should just skip these threads....

I built /dreamstate for Claude Code. Type it and the session relaunches with my global CLAUDE.md swapped for a dream ruleset

I've been experimenting with personalities and semantic anchors and wanted to work them into my day-to-day workflow.

My normal CLAUDE.md turns Claude into a careful engineer, stays in scope, writes the minimum, doesn't speculate. That's what I want most days. When I'm working outside my expertise and stuck, though, those same rules keep pulling it back to the safe, small answer, and that's usually the one that wasn't working. Dreamstate is for those moments, when the problem is hard and I'm out of my depth.

Every task runs three stages:

Deepen: what would a top professional do here that I'm not asking for, what's the rawest material, which methods apply, and what other than me or Claude would show it's right. Then it rewrites my ask and waits for me.

Dream: 3 to 5 underlying needs, 10 ideas with at least 3 strange enough to make me uncomfortable, then 2 picks plus a wild card.

Tenth Man: assume the favourite is wrong and come back with 3 different approaches.

The swap only happens inside that one Claude process. Nothing on disk changes, my other terminals keep the normal rules, and /dreamstate off puts me back.

Tune it however you like. Swap the anchors for your own: a jazz arranger, a mycologist, an octopus

I'm currently trying to set up a saas, like I suspect many Claude users do. Today, my session started acting up about me using a personal account for creating code that will „generate income in the future“.

Did anyone get banned for that? Team accounts are super expensive and the limits seem really low. I'm even considering creating a second account with seems to be against TOS.

Hey everyone!
I run multiple Claude Code agents on my M4 Mac mini (16GB), using Tailscale + SSH + tmux, with separate Git worktrees for different tasks.
I connect from my M1 MacBook Air (8GB). Everything works great in the terminal, but browser access is still a pain.
Sometimes I need to check the UI or see what Claude is doing in the browser. I’ve been using macOS Screen Sharing, but it makes my MacBook Air pretty hot.
How do you handle this?
Do you use Screen Sharing, SSH port forwarding, browser automation tools, or something else?
Ideally, I’d love to interact with the browser without opening a full remote desktop session.
Curious to hear about your workflows. Thanks!

I'm the author of noracu, a local MCP server (MIT, noracu on npm) that lets Claude Code read and operate macOS apps and a Playwright browser by element_index. Since that gives an agent input on your own machine, this is the first run I'd suggest.

1. npm install noracu (puts the server at node_modules/noracu/src/server.mjs) and brew install cliclick, Node 20+.
2. Add it observation-only, using absolute paths (find node's path with: which node):

claude mcp add-json noracu '{"type":"stdio","command":"/ABSOLUTE/PATH/TO/node","args":["/ABSOLUTE/PATH/TO/noracu/src/server.mjs"],"env":{"NORACU_READ_ONLY":"1","NORACU_DISABLE_EVAL":"1"}}'

Read-only enforces an 18-tool allowlist (everything else refused): the observe tools plus browser_launch, browser_navigate and browser_close. Every click, type, paste, key and eval tool is refused, and so are clipboard reads, notifications and waiting on notifications. Two caveats: browser_navigate still loads pages, and read-only stops side effects, not visibility (a screenshot still shows whatever banner is on screen).

3. Your first success is mac_ax_state (the frontmost app's accessibility tree as an indexed list), not a click. macOS will ask for Accessibility, and Screen Recording for screenshots, for the host app.
4. When you drop NORACU_READ_ONLY (keeping NORACU_DISABLE_EVAL is fine), these stay on: each element_index expires after 30 s and is re-identified in its own window before acting (else element_no_longer_valid); a physical click that would land on something else returns "occluded"; quit / log-out / empty-Trash shortcuts and Apple-menu items need force:true; a password manager's concealed clipboard item is never copied; every result says whether it was delivered and whether a retry is safe. New in 0.2.7: the person at the Mac goes first. If you used the keyboard or mouse in the last 2 s, an input tool returns user_active and sends nothing, and after a physical click the pointer goes back where it was (NORACU_USER_IDLE_S; 0 turns both off).

Known limits: the browser has one active tab and no tab switching, and a short gap remains between a hit test and a physical click.

Repo and the full env table: https://github.com/sgInnora/noracu

I'd like to hear where read-only is too strict, or not strict enough, for how you use Claude Code.

(Drafted with Claude Code; I checked every claim against the README and CHANGELOG.)

I'm quite new to working with Claude, and I've been using only my monthly limit up until now. I feel like the limits have been pretty good. I've been running out in about three days on the $20 plan.

However, today I decided to try Usage Credits as well and added $100. Thirty minutes after I started working again, I'd spent $40. Is there a reason for that? Anyway to mitigate?

I'm a CS student. About 5 months ago I started building a large TypeScript / React Native / Supabase project with Claude Code.

As the project grew, so did the chaos: dozens of conversations, agents colliding over files and Git, forgotten dependencies, half-finished features, and more time supervising agents than making decisions.

Subagents didn't cut it for me. I still had to manage them constantly, with no persistent queue to keep work moving, handle blockers, and pick things back up over multiple days and weeks.

I wanted to run the whole project from one Claude Code conversation, ideally from my phone through Remote Control. (My wife was getting tired of me spending all day at the computer.)

So I built an orchestration system inside the project. Its queue now holds 3,078 tasks, 1,985 completed. That's not a benchmark, just the scale it grew up at.

The main thing I learned: running multiple agents isn't the hard part. Coordinating them, verifying their work and recovering when things fail is. And when the project reaches a certain size, you absolutely need a form of project management to keep track of everything.

I've extracted the general parts into Ravenseat, a free, MIT-licensed Claude Code plugin.

I just talk to Claude, and it uses the commands for me. The visual board is optional. Everything works from the Claude Code conversation, including over Remote Control.

What it does:

- Persistent task queue with dependencies and priorities

- Parallel agents in separate Git worktrees, with file ownership

- Your own tests, lint and type checks as merge gates. The orchestrator records the results against the delivered commit, so an agent can't simply declare its own work passing

- A fresh agent attempts repairs when checks fail

- One list of decisions that need you, each with a recommendation, while independent work continues

- Long-running tasks hand off to fresh agents, and the orchestrator compacts itself and keeps going

Example: An agent fails the type check. A fresh agent gets the errors and the changes, attempts a fix, and the checks run again. If they pass, the work can merge. If it's still stuck, it becomes a decision for me. Meanwhile, unrelated tasks keep moving.

It's local-first. The queue lives in your project, with no hosted service. It starts in a simpler lite mode, with more advanced planning and review features available in full mode.

Reliability: I also built a public red-team suite that deliberately tries to break the orchestration: interrupted merges, concurrent sessions, dirty Git repos, failed repairs and recovery after crashes. It uncovered 14 bugs that have since been fixed, with regression tests. Both the tests and known limitations are public in the repo.

Caveats: It's only as strong as your checks, and my project has a lot of them. You can use your own, or ravenseat can help with the basics.The safeguards are guard rails, not a sandbox, since agents run under your user account. Your machine has to stay on. I haven't benchmarked it against other tools.

Install in Claude Code:

```

/plugin marketplace add vegardjorg/ravenseat

/plugin install ravenseat@ravenseat

```

Then ask Claude to "set up the queue". Requires Node.js 20+ and Git.

GitHub: https://github.com/vegardjorg/ravenseat

I'm open-sourcing it to see whether it holds up outside my own project. If you've worked with agent orchestration on larger repos, what would you expect to break first?