Inter-Agent Communication and Parallel Task Execution Support

Resolved 💬 3 comments Opened Aug 13, 2025 by miteshashar Closed Jan 4, 2026

Feature Request

When Claude code is executing tasks, it is already possible to still send messages and Claude Code is able to accommodate that message and accordingly re-aligns its actions.
However, when one or more sub-agents are running, there is no way to direct a message to a specific agent or the main instance. Being able to do that would be fantastic.

Use cases:

  • Agent 1, 2 and 3 are running in parallel. We notice a faulty pattern in Agent 2 and want to inform Agent 2.
  • There are tasks running either in the main agent or in 1 or more sub-agents. In the meantime, we want to trigger other sub-agents to run in parallel(for a task that may or may not be in the todos already). It would be great if I am able to inform the main agent to trigger these sub-agents. Example below:

``
Update Todos
⎿  ☒ Fetch and analyze all open GitHub issues using github-manager agent
☐ Analyze Issue #23 (Hardcoded Admin Credentials) - critical security issue
☐ Analyze Issue #24 (Authorization Bypass) - critical security issue
☐ Analyze Issue #36 (OpenNext.js Anti-Patterns) - high priority, 75% complete
☐ Analyze Issue #35 (Remove Sample Data) - likely resolved based on commits
☐ Analyze Issue #25 (ItemCard Refactor) - high priority maintainability
☐ Analyze remaining medium priority issues (#33, #34, #26, #38)
☐ Evaluate issue references in PLAN-WAVE-2.md and PLAN-WAVE-3.md documents
☐ Provide concise status reports for each issue and seek user decisions
☐ Update plan documents based on user feedback and issue analysis
☐ Post comments/updates on GitHub issues as instructed by user
``

The issue analyses are running sequentially and pressing escape while an agent is running is a very flaky pattern. I want to inform the main agent to actually complete all the analyses in parallel.

Environment Info

  • Platform: darwin
  • Terminal: WarpTerminal
  • Version: 1.0.77
  • Feedback ID:

Errors while submitting this feedback with /bug

[
    {
        "error": "AxiosError: Request failed with status code 403\n    at LN (file:///path/to/claude-code/cli.js:685:1077)\n    at Unzip.V0 (file:///path/to/claude-code/cli.js:686:9955)\n    at Unzip.emit (node:events:519:35)\n    at Unzip.emit (node:domain:489:12)\n    at endReadableNT (node:internal/streams/readable:1701:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)\n    at bB1.request (file:///path/to/claude-code/cli.js:688:2088)\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async vH8 (file:///path/to/claude-code/cli.js:2381:470)\n    at async Promise.all (index 0)\n    at async file:///path/to/claude-code/cli.js:2367:19497",
        "timestamp": "2025-08-13T19:01:04.321Z"
    },
    {
        "error": "AxiosError: Request failed with status code 403\n    at LN (file:///path/to/claude-code/cli.js:685:1077)\n    at Unzip.V0 (file:///path/to/claude-code/cli.js:686:9955)\n    at Unzip.emit (node:events:519:35)\n    at Unzip.emit (node:domain:489:12)\n    at endReadableNT (node:internal/streams/readable:1701:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)\n    at bB1.request (file:///path/to/claude-code/cli.js:688:2088)\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async vH8 (file:///path/toclaude-code/cli.js:2381:470)\n    at async Promise.all (index 0)\n    at async file:///path/to/claude-code/cli.js:2367:19497",
        "timestamp": "2025-08-13T19:01:21.814Z"
    }
]

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗