claude-code - 💡(How to fix) Fix isolation: worktree frontmatter not respected when agent invoked via claude --agent [2 comments, 3 participants]

TL;DR

The isolation: worktree frontmatter in the agent definition file is not being respected when the agent is invoked as the main agent, suggesting a potential issue with how the --agent flag handles isolation.

Guidance

• Verify that the isolation parameter is correctly parsed from the agent definition file by checking the code that handles the --agent flag.
• Investigate if there's a difference in how the isolation parameter is applied when an agent is spawned as a sub-agent versus being the main agent.
• Check the documentation for the --agent flag to see if there are any specific options or configurations that need to be set for isolation to work correctly.
• Consider adding logging or debugging statements to the code that handles agent invocation to see how the isolation parameter is being processed.

Example

No specific code snippet can be provided without more context, but an example of how the isolation parameter might be handled in the agent invocation code could look like:

# Pseudo-code example of agent invocation
if agent_invoked_as_main:
    # Check if isolation is set to 'worktree'
    if agent_definition['isolation'] == 'worktree':
        # Create a temporary git worktree
        create_temp_worktree()
    else:
        # Run in main worktree
        run_in_main_worktree()

Notes

The issue seems to be specific to how the --agent flag handles the isolation parameter, and more investigation is needed to determine the root cause.

Recommendation

Apply a workaround by modifying the agent invocation code to correctly handle the isolation parameter when the agent is invoked as the main agent, as it seems like the current implementation has a bug or inconsistency in how isolation is applied in different scenarios.