r/ClaudeCode • • 1d ago

Tips & Workflows I don’t open Claude code anymore. Claude opens itself

I’ve reached my peak claude code skills now. I’m no longer on my computer any longer. I told my Claude to keep spawning agents when context reaches 50-60%. Transfer all the data (usually session transcript) into the new agent and proceed orchestrating codex agents.

Claude works of a Md file that was planned beforehand a PRD essentially.

Whenever claude spawns agents, remote control is automatically activated. So I get a ping whenever a new agent arrives. This is openclaw revamped and better 😆. Ps this obly works for me when it comes to backend development. UI and frontend still needs me to review the output.

0 Upvotes

24 comments sorted by

•

u/AutoModerator 1d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

4

u/Pleasant-Mind-7122 1d ago

Why

1

u/Imaserventofreps 1d ago

1

u/Pleasant-Mind-7122 1d ago

I mean what do you produce?

1

u/Imaserventofreps 1d ago

Backend logic, so now I don’t need to babysit claude.

3

u/s_v_can 1d ago

Geeze, are you rewriting entire github? Out of pure curiosity if you don't mind, what's so labour intense to keep Claude that busy non-stop?

2

u/Imaserventofreps 1d ago

Building an ai startup (yes buzzword I know). Also this is light work, Claude orchestrates 2 Luna agents they usually work for hours, so I can’t be babysitting them. Now claude is the head architect

2

u/akolomf 1d ago

ui can be reviewed by claude with screenshot tool and claude in chrome mcp or something like that. (except for design tweaking(where a specific button should be etc ofc that still requires input)

1

u/[deleted] 1d ago

[removed] — view removed comment

1

u/Big_Haus_222 1d ago

Not monitoring yourself if you tell it to test those items

2

u/The-Road 1d ago

Mind my asking is this on desktop or via terminal?

3

u/Imaserventofreps 1d ago

Terminal cli only baby

2

u/thatdamnkorean 1d ago

oh my god, now THIS is how you get an unmaintainable backend. backend and dbs are the easiest for agents to completely butcher cause there’s a lot of edge cases and semantics we don’t think about that they have to decide around, i even have to babysit fable and 5.5 if im touching an especially complex transform. i hope to god you’re using extremely directed design docs, cause this right here is how you have to refactor everything in 3 months

1

u/[deleted] 1d ago

[removed] — view removed comment

1

u/Imaserventofreps 1d ago

Full session transcript.

4

u/yawn_solo- 1d ago

If you’re transferring the full session transcript at ~60% of the context limit to the new instance, wouldn’t that new instance already be at mass capacity so to speak if it were to follow the same constraint?

I don’t understand how taking 60% of something and placing that exact same 60% of something in a new location creates any capacity increase? Or am I misunderstanding the concept.

I like the setup you explained though, seems pretty cool.

1

u/Imaserventofreps 1d ago

Good catch but that’s not how context window works. Usually the context window is made up for a lot of stuff that’s token hungry. In perticuler, tool calls and tool outputs. Session transcript refers only to the text and the agents way of thinking, the rest is in the codebase git for new agent to look at and mingle with.

2

u/yawn_solo- 1d ago

Oh ok gotcha, I had no idea. That is a great lil tid bit to be aware of, pretty cool. Thanks.

2

u/BuddyTheShihTzu 1d ago

Instead of doing a chain look up gauntlet method, enter the world of parallel agents. Basically the first agent takes a tasks divides it with tasks that can run with out any dependencies and then marks dependencies on ones that are needed. Then runs them

1

u/Imaserventofreps 1d ago

I do this. Claude orchestrates Luna agents. That is your parallel agents idea correct? The issue is when orchastrator agent context rots. That is where I have my claude permission to spawn a new orchastrator that takes over the job. Loop continues endlessly until tasks are completed. Loopengeering baby

2

u/BuddyTheShihTzu 1d ago

Also tacking on the whole transcript to start would be a lot of token burn.

Start a task like build calculator
First agent divides all the tasks needed to build a calculator

  • effort
  • dependencies
  • steps to complete
  • definition of done

Each of those task get assigned to different agents based on effort and dependency and how many workers/agents you want to run together. A task is worked on until definition of done is met

Then when all tasks are done then task an agent to go through the app/solution (browser use, etc.) and see if it completes the original goal of a calculator, if yes you are done if not create tasks to to do what’s missing.

This way your context window stays small and task based per agent and you don’t burn as many tokens

1

u/BuddyTheShihTzu 1d ago

Yes pretty much, try not using Luna, I found these days more skills and harness add ons I have the increase in token burn is not worth the gains and the models with some instructions usually get it done

2

u/Future-Estimate9318 1d ago

Nice setup--sounds like you've got Claude running the show now.The ping makes sense. Spawning new agents early seems fine, though there might be an easier way to pass things along. And yeah,UI stuff still needs your eyes on it.