Skip to content

Multi agentic and tool integration #29264

Open

Description

@tarunpahade18

What variant of Codex are you using?

cli

What feature would you like to see?

CLI

Planner Agent → breaks task into steps
Research Agent → gathers information
Coding Agent → writes code
Reviewer Agent → critiques output

Research task:

  • Search docs
  • Search GitHub
  • Search issues

Additional information

Benefits:

Easier contributions from community
New tools without touching orchestration code
Parallel Tool Execution
Many terminals execute tools sequentially.

Example:

Research task:

  • Search docs
  • Search GitHub
  • Search issues

Activity

  1. added
    CLIIssues related to the Codex CLI
    subagentIssues involving subagents or multi-agent features
    on Jun 20, 2026
  2. github-actions commented on Jun 20, 2026

    @github-actions
    Contributor

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

  3. Necmttn commented on Jun 21, 2026

    @Necmttn

    A multi-agent CLI surface needs explicit run records. Planner, research, coding, and reviewer agents should each get a child run id, role, model, tool set, parent step, status, and output artifact refs. Parallel tool execution can then be audited and resumed without treating several agents' results as one undifferentiated transcript blob.


    Generated with ax.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CLIIssues related to the Codex CLIenhancementNew feature or requestsubagentIssues involving subagents or multi-agent features

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions