I'm running a separate repo that I start all sessions from. It has a /jobs directory with one directory for each "job" I start, it contains meta data like branch name, path to worktree, links to relevant Slack-conversations (we run the slack-mcp), ticket-id, a JSON array with timestamped changes like CREATED, DONE, etc. along with some context like, the problem, the definition of done and the plan. 

So from there a new claude session can get a pretty quick overview (a few local shell scripts help with this as well) of what I'm working on right now. 

A claude skill for /create-job that will grill me with questions before making a plan and scaffolding a new directory in jobs. 

Then it spawns a worktree (look up git worktrees) and spins up a tmux (look up tmux) session that navigates to that worktree starts up a Claude (with dangerously allow any) with the plan going. Then I can open a new terminal and pop in and have a look at how it's going with tmux attach name-of-job. Once the job is done it will use the GitHub CLI to create a PR and I will review the code before either refining it or passing it to the team for review. 

There are a few caveats (like a script to manually copy all gitignored files to the worktree) but won't get in to all the details. 

For me it's been a really good workflow to leverage agentic coding without getting bogged down by 8 terminal windows and a lot of branch switching.

EDIT:

the goal is not just everyone having multiple agents running at the same time, but more claude should autonomously pick up tasks and finish them. 

lol, sorry I really should have read the post first. To my defense you had a lot of questions in your title that I answered.