Are Subagents supported?

[Pipboyguy]

Add support for multiple concurrent sessions per project

I'm not sure whether this refers to subagents or something else like git worktrees?

I've tried tdd-guard with multiple concurrent subagents but it does seem like they start writing to same files at the same time, triggering the pre-tool hook in a confusing way.

Am I misinterpreting or misunderstanding current limitations? If so, how would you recommend speeding up large projects where TDD can take a while?

Thanks!

[Pipboyguy]

As a side note, this is ideally a problem Anthropic would need to solve to enable concurrent agents to work in the same branch. Would a mutex, perhaps something akin to a file locking mechanism like file_being_edited.py.lock, be a viable solution for this?

[nizos]

Hi @Pipboyguy,

Thanks for reaching out!

This refers to multiple Claude Code sessions running at the same time in the same project and also for multiple subagents making modifications. I need to clarify this point better. :)

As you pointed out, there are some difficulties getting multiple concurrent sessions working without affecting each other.

From my perspective, we can get the session id from the hook event data and store different session data separately using this id. The issue is mapping the results from the test reporters to the correct session data file without resorting to any dangerous or overly complex ways of doing so. I would rather be safe than sorry when it comes to constructing and handling file paths due to the mechanics at play.

I am happy to discuss this and take ideas on how to approach this in a clean and safe manner. :)

[Pipboyguy]

You're right that you're solving a concurrency control problem, but for tdd-guard i think its more specifically about coordinating shared validation state rather than preventing file-level race conditions during editing.

Both issues would likely need hooks-based solutions - PreToolUse for conflict prevention and session ID isolation for state management. The main risk I see is deadlock if multiple sessions acquire locks in different orders.

This is coming from a someone without much knowledge of concurrent programming, I just want to solve this issue to reduce my screen time staring at streaming tokens all day