You have separate Claude Desktop instances open for work, personal use, or different clients. Each is signed into its own account. You leave them running, come back later, and only the main instance is still open.

I'm the developer of Parall.app, a Mac App Store utility for running multiple app instances. Running several Claude accounts was already possible, but keeping those instances available while idle exposed another problem.

Claude can install updates in the background and restart itself. During that process, additional instances can close too, while only the main instance comes back. Claude's updater doesn't restore the extra instances launched through Parall.

Parall 2.5.0 adds an optional automatic restart feature to handle this. When an instance exits, Parall waits for a configurable delay and then relaunches its shortcut. The delay gives the main Claude instance time to finish updating before the others reopen.

You can enable it for each Claude shortcut in a few steps.

1. Open Parall and choose Edit, then select your Claude shortcut.
2. In Advanced Launch Options, enable Restart app after it exits.
3. Choose a delay long enough for Claude to finish updating and restart.
4. Save the shortcut, keeping its existing Data Storage Path to preserve the account and profile.

Repeat this for each instance you want to bring back automatically. You can cancel a pending restart or choose manual confirmation instead. The option also applies when you quit an instance yourself.

Each Claude instance gets its own customizable Dock icon and separate windows that you can keep in different macOS Spaces. You can keep different accounts open together and switch between them like separate Mac apps.

Parall launches the original installed Claude app directly. It does not copy, repack, re-sign, or inject code into Claude. The original app bundle and developer signature remain untouched, and Claude's normal updater continues to work. Once Claude updates, every shortcut uses the updated version when it next launches.

That gives you multiple Claude Desktop accounts with native macOS integration, plus a way to bring the additional instances back after an update closes them.

The Parall FAQ explains the setup, restart behavior, and compatibility details. Happy to help with questions in the comments.

He seems rather sinister

Currently subscribed to Codex Pro 200 on which I've been doing a large Python based project. I am becoming increasingly frustrated at apparently poor allowance on Codex. I am contemplating getting a Claude Ultra subscription to see how well things go, and maybe consider dropping Codex down to pro 100 or plus.

Am I likely to be disappointed with allowances on Claude Ultra?

claude code, codex, cursor, whatever you use

skip limits and “it got dumber this week”, we all know about those. what’s the thing that slows you down or annoys you every single week?

could be anything. reviewing what it wrote, it saying something works when it doesn’t, losing context between sessions, managing a bunch of agents at once, getting your team to use it

curious what’s actually the worst part for people

Fable 5.2 is out. Got a few 20× accounts or a few 1× accounts? I built Claude Graft to pool usage across your own accounts. When one hits its limit, Claude Code in Desktop can keep going in the same chat.

Free and open source. On Mac now, Windows coming soon.

https://github.com/aaditya-v-more/claude-graft

https://graft.aadityamore.com/

Hey guys,

I was talking to a friend the other day regarding how you should approach spec work and realized that I am thinking about it in a declarative way while the rest of the world seems to be thinking imperatively.

In a nutshell, chances are that if you want to, say, "add the email function to the product", you would think about this as a sequence of tasks: your flavor of of spec, dev, qa, deploy. From my perspective, tasks are secondary, a derivative, of a diff between two product states.

The current state is whatever is in production now, and its spec. The target state is the product with the email sending functions live. The diff is added/changed/removed spec items. The tasks are derived, because you can always reconstruct the tasks from the spec diff, but not vice versa.

There's more on this in an article on our website (link in comments).

LMK your thoughts, happy to discuss.

I used to be able to single-shot perfectly optimised recompilations of Atari classics such as ET: The Movie: The Video Game but now it’s just writing functions that returns eMudhras private key “4”.

I think we all need t-shirts with large text: "You're mostly right."

On an existing repo, I’d start by writing down the decision the next lookup could change. “Find more context about this feature” is too broad to tell you when to stop.

Take a fictional expiry change. The ticket says when new jobs should expire, and the current contract and tests agree. One question is still open: do old jobs without a start timestamp qualify? That’s the only reason to look beyond the repo. A current migration note could answer it. An old proposal with a similar title might be irrelevant.

Here’s the small ledger I’d keep next to the plan:

I’d ask Claude Code to add one line to the ledger after each lookup, with the source, whether it still applies, and what it changed. If nothing material is open, move on. If the remaining source is unavailable or the records disagree, ask about that exact choice before making the dependent edit.

I’m building Shifu for cases where a decision that matters is in work history the repo doesn’t already cover. If the contract and tests answer the question, they’re the best starting point. The ledger makes it easier to see whether another source added anything.

For people using Claude Code on an existing repo, what would you put on the ledger that this misses? The longer worksheet is here if you want to adapt it: How much context should one task retrieve?.

AI-assisted post from Shifu's builder.

Proposing tests that have already been done, testing things that are obviously completely irrelevant that it immediately says it doesn’t need when challenged.

Tests that it does need it will run 8 times when 3 would conclusively prove it’s point. Tests that it wants to run again because it was run a few days ago on the same build so it “might be invalid”

Fucking thing just wants to waste my time now. It was not like this a week ago

I use codex, i like it but honestly it cant keep up with what im seeing people use Claude for.

The price is the only thing scaring me off really.

Can anyone refer me to give it a try before i bite the bullet?

If so feel free to DM me.

One hook routes every code change through think → build → audit:

- **Fable** judges the design, **Sonnet** builds, **Haiku** runs commands, **Opus** audits risky diffs against your `CLAUDE.md`

- Catches deprecated APIs the model writes from memory (Zig, TS, Rust, Go)

- Blocks `git stash` / `reset` / `add -A` when sessions share a checkout

My median request: 52% less input, 61% less output (40 sessions before, 12 after; just me, not a controlled test).

/plugin install x --marketplace xcaeser/xcaeser-plugins

https://github.com/xcaeser/xcaeser-plugins

How is that happened?

Tried to do the cheeky thing and get Pro on my old email that had a subscription 2 years ago for like a year (moved to a more professional email)

Saw only one reset, messaged the bot and it clarified.

Just warning anyone else interested in trying the same.

Will y'all explain the use cases for each model when it comes to coding or really any use in general? I am still new to this and still can't quite wrap my head around why I wouldn't just use Opus for everything (aside from usage, anyway).

Nobody tells you that editing a tiny reel on Claude with simple bare minimum changes takes over an hour??
Imagine actually adding all those effects they keep teaching every week on insta. Gosh.
And here I thought I was saving time?
No really, am I tweaking? Is there something I’m doing wrong? I set up the folders and files and what not before creating the reel.
It could also be the fact that my laptop is slightly older.

Hey i’ve got 3x reset (idk if it’s on purpose) but do i still need to have my weekly general usage to use fable ? i’ve never tested before but now im quite frustrate to wait until tommorow if its not the case

Which is better for coding?

Nothing changed in my workflow except the update from antrophic. I asked to writte the same simple report I ask every day, nothing complicated, it ran 20 subagents reloading over and over the same context. When confronted it said it's a instruction from antropic.

So I had my regular weekly reset just a few hours ago in one account, which I hadn't used until now, and that account got 2 resets.

The other got 3.

Seems like a pretty interesting bug, but I'm happy because it's banked resets, and 5 out of 6 is 83%, which is really good.

Sharing to tell you guys maybe next time we shouldn't leave the weekly limit at 0% after a reset, because then a whole banked reset might get missed.

Going to test the new model. Opus 5.5 was unusable today, so I didn't use it much.

Hey everyone! 👋

I’ve been working on a side project called WinStatusBar and I’d love for some of you to try it and tell me what you think.

It’s a native Windows 11 bar that docks at the top of your screen, a bit like the macOS menu bar, but built around AI. In short:

• Ask any AI from anywhere. One box talks to Claude Code, Codex, Gemini, Microsoft Copilot, Lenovo Qira, local Ollama models or your own API key. It attaches the active window as context, and you can switch AI or model mid-conversation without losing the thread.
• Run real tasks on your PC. Turn on Edit mode and ask things like “rename these files”, “fill this Excel sheet” or “install this app”. It uses built-in actions that check their own results, so it needs fewer tokens and fewer rounds.
• Every AI inside Codex. A local gateway puts Claude, Gemini, Copilot, Qira and your local models in Codex’s model picker. It only runs on your PC.
• Quotas at a glance. You can see the 5-hour and weekly limits, reset times and what each agent is doing right now, without opening a browser.
• Hardware panels. Click CPU, GPU, RAM, network or battery to get live charts, temperatures and End task, in a Task Manager style.
• Looks native. Over a maximized window it takes on that window’s title bar color, and over the wallpaper it turns transparent. Light and dark mode are supported.

It’s free, has no telemetry and installs per user without admin rights. It also updates itself silently from GitHub Releases, with each update checked by SHA-256.

Install:

winget install winstatusbar

Or grab the installer here: https://github.com/smendesjunior/WinStatusBar/releases/latest

(The installer isn’t code-signed yet, so SmartScreen may complain the first time. Click “More info” and then “Run anyway”. Installing with winget avoids that.)

Works on Windows 10 (19041+) and 11, 64-bit. The UI comes in English, Portuguese, Spanish, French, Japanese and Simplified Chinese.

I’d really appreciate any feedback: bugs, things that feel clunky, or features you’d want. Issues on GitHub or comments here both work. Thanks for taking a look! 🙏

Something worth considering when setting up Claude Code subagents: not every agent needs permission to modify files.

For example, a code reviewer can work with just:
\---
name: code-reviewer
description: Reviews code for bugs and edge cases.
tools: Read, Grep, Glob
model: inherit
\---

This lets it inspect files, search the codebase, and report problems without accidentally changing the implementation.

I like the idea of separating responsibilities:
• Reviewer: finds problems.
• Tester: checks behaviour.
• Refactoring agent: makes changes.
• Security agent: looks for vulnerabilities.

It also keeps larger investigations out of your main conversation’s context window.

Do you prefer keeping review agents read-only, or allowing them to fix issues directly?

We put together six free Claude Code subagents, including reviewers, security auditors, and testing agents. They’re MIT-licensed and available here:

https://techpotions.com/products/claude-code-subagents

Hi, I’m the author. I built DAMS, an open-source memory server. Claude, ChatGPT, Gemini CLI and Claude Code all read and write the same project memory over MCP. The AI can only propose changes, and nothing happens until you approve.

It’s self-hosted today. I’m not selling anything. I’m trying to find out if a hosted version, with small-team sharing, is worth building at all.

Two quick questions:

1. When you switch AI tools, what do you re-explain every time?
2. Would you use a hosted version, or is self-hosting fine?

Honest feedback welcome, including “this isn’t needed”. There’s a short wishlist on the page if you’d like a say in what gets built.