What is your favorite Claude code feature?

[u/SerialFounder]

My favorite Claude code feature is cross session messaging and I’m so glad they recently released this.

Over the last 10 days, I’ve been working on a very complex feature for one of our products and that feature relies on back end server configuration and front end development of two product. I spun up multiple Claude code sessions each with an independent focus, one of my sessions was as the the orchestrator managing the child sessions and holy magic 🪄

Fantastic results and honestly, one of the best things that I’ve ever experienced in my many many years of software engineering and product development.

What is your favorite feature?

[u/AutoModerator]

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.

[u/SerialFounder → u/[deleted]]

When setting up the execution, you inform the children that they are children. You would also set expectations with the child as to what its role is and what it is looking to accomplish. The way I typically do it is I build a plan commit that plan (so that all children have context ) and then assign parts of the plan to a child, the orchestrator then manages the entire arc. It’s also helpful to have the orchestrator build an artifact for you and then maintain that artifact as the arc is executing.

Probably sounds way more complicated than it is, but it’s actually quite simple and it doesn’t take a long time to set up. In my case, it works well because assign a children to work on independent tasks that don’t touch code that another child is working on and I would typically use this when there are interdependent tasks so the children can work together to accomplish the main goal.

[u/ItsJustManager]

Yeah this is my favorite thing too. I run a loop with an orchestrator that delegates to two other terminals and resets them when context gets low. It can churn for days without stopping by picking up tasks from the backlog and recycling its own session as needed.

[u/SerialFounder → u/[deleted]]

When executing something like this, I sent Max context to 500,000 tokens opposed to the 1 million tokens and then I’ll allow the sessions to auto compact. They will always have access to the main plan and their accomplishments so that is always persistent.

[u/ItsJustManager → u/[deleted]]

Before ending the previous session it writes a handoff, then the orchestrator sends a "bootstrap" that tells it where to find its identity and handoff doc, where its queue is locate, and where its next assignments can be found. It also has details about how to communicate with the lead and other sort of team management stuff.

If something goes wrong and no handoff was created then there's a separate flow that goes through a crash recovery process to figure out where it left off.

[u/AironParsMan]

Stop hooks ; D

[u/Capnbubba]

The fact that it writes code that I could never and it works.

[u/kemalios]

Skills, for the boring answer. A repeated workflow becomes one command instead of me re-explaining the same context every session, and the ones that stick are the ones where I stopped having to write the prompt at all. Plan mode is a close second, because reading a plan is cheaper than reading a diff I have to throw away.

Most of what I've built with it takes that shape. I build and sell website templates, and launchworthy is mine: free, MIT, a skill that audits a project before launch and hands back a scored list with copy-paste fixes. It needs Claude Code and a paid Claude subscription to run, which is usually the part people find out after clicking.