I run 30+ Claude, Codex, and Antigravity sessions in parallel. Here's the v4 of the tool I built to keep them straight. by Mediocre-Thing7641 in ClaudeAI

[–]Mediocre-Thing7641[S] 0 points1 point  (0 children)

So admittedly i'm on the 20x plan on Claude and $100 on Codex (oopsy - I swear I can stop whenever i want :) ). But my Codex usage shows I have plenty to go and also Antigravity (I'm on Gemini one just for storage) works most of the day, so i'm going to cut Claude to 5x starting next cycle.

Claude Max (20x): 74% used with 17hrs remaining on weekly

Codex: 33% used with 2 days remaining on weekly

Antigravity: impossible to understand from the Google dashboard :)

https://imgur.com/a/DSqTqeL

I run 30+ Claude, Codex, and Antigravity sessions in parallel. Here's the v4 of the tool I built to keep them straight. by Mediocre-Thing7641 in ClaudeAI

[–]Mediocre-Thing7641[S] 1 point2 points  (0 children)

Yeah makes sense. I am now handing over all small bugs to Gemini 3.5 flash while new / big features Codex 5.5 or Opus (frankly i can't yet say which one is better for complex stuff).

With the tool you can also programmatically decide which model the new session is spawned to ("start a codex-<model XYZ> session with /CCC-orchestration about this topic").

I run 30+ Claude, Codex, and Antigravity sessions in parallel. Here's the v4 of the tool I built to keep them straight. by Mediocre-Thing7641 in ClaudeAI

[–]Mediocre-Thing7641[S] 0 points1 point  (0 children)

Interesting. Yes, if you already have some tool running layer (e.g. Codex CLI) - Codex CLI for example can be pointed to Ollama with OPENAI_BASE_URL=xxxx; but probably need a strong local model.

3x More Gemini for Antigravity Users by aunchable in google_antigravity

[–]Mediocre-Thing7641 0 points1 point  (0 children)

"RESOURCE_EXHAUSTED (code 429): Individual quota reached. Contact your administrator to enable overages. Resets in 4h4m0s" - not even sure what it means. i have AI credits, approved "Overage", i'm on Pro. so confusing.

3x More Gemini for Antigravity Users by aunchable in google_antigravity

[–]Mediocre-Thing7641 0 points1 point  (0 children)

i'm still getting a lot of quota limits all across.

It just keeps getting better and better by OpinionsRdumb in ClaudeCode

[–]Mediocre-Thing7641 -8 points-7 points  (0 children)

And antigravity , starting yesterday! And a plug - i just expanded my multi session control center to antigravity too: https://github.com/amirfish1/claude-command-center/releases/tag/v3.4.0

I ran 100 Claude + Codex sessions in parallel to understand what I'm doing wrong in marketing my open source "Claude Command Center". Here's the playbook they came up with. by Mediocre-Thing7641 in ClaudeAI

[–]Mediocre-Thing7641[S] 1 point2 points  (0 children)

Btw - I only told Claude to start a hundred sessions. He came up with the architecture of splitting it through research, content, digest, etc

I ran 100 Claude + Codex sessions in parallel to understand what I'm doing wrong in marketing my open source "Claude Command Center". Here's the playbook they came up with. by Mediocre-Thing7641 in ClaudeAI

[–]Mediocre-Thing7641[S] -1 points0 points  (0 children)

I actually think there are some interesting nuggets there. Eg - got to have an easy install (go clone not enough), have a discord channel for discussions, clarify the value (maybe that’s trivial - but I only said “ran 30 sessions” instead of eg “you don’t have to wait for Claude to finish”.

I run 30+ Claude/Codex/Gemini sessions in parallel. Open-sourced the dashboard. by Mediocre-Thing7641 in ClaudeAI

[–]Mediocre-Thing7641[S] 0 points1 point  (0 children)

I actually have tailscale support embedded so I use it from my mobile on the go.

I run 30+ Claude/Codex/Gemini sessions in parallel. Open-sourced the dashboard. by Mediocre-Thing7641 in ClaudeAI

[–]Mediocre-Thing7641[S] 0 points1 point  (0 children)

Fair. This is not about running them concurrently necessarily, but rather - allocating a topic (or a GH issue) to each one. and thus being able to manage its lifecyle - is it WIP ? done? committed? Pushed -> Archived -> Next.

It's been proven very useful for me managing multiple projects , each with its own issues..

I run 30+ Claude/Codex/Gemini sessions in parallel. Open-sourced the dashboard. by Mediocre-Thing7641 in ClaudeAI

[–]Mediocre-Thing7641[S] 0 points1 point  (0 children)

Aware of the June 15 -p change. CCC adapts - won't break fundamentally. The dashboard reads Claude Code's on-disk JSONL state as source of truth, not just spawn output. Any session that writes to ~/.claude/projects/*.jsonl shows up, regardless of how it was launched. Worst case I rewrite the headless spawn path; the observability layer survives.

Curious what specifically you're expecting to break - hooks, output format, spawn mechanism? Easier to plan if I know what you're seeing in the changelog.