Skip to content

Feat/agent orchestrator - #267

Closed
ryantzr1 wants to merge 1 commit into
mainfrom
feat/agent-orchestrator
Closed

ryantzr1 wants to merge 1 commit into
mainfrom
feat/agent-orchestrator

Conversation

@ryantzr1

@ryantzr1 ryantzr1 commented Jan 12, 2026

Copy link
Copy Markdown
Contributor

Note

Introduces multi-agent orchestration docs and example, and refines model routing for Codex-capable models.

  • Adds docs/cookbooks/multi-agent.mdx with a full guide, diagrams, and usage instructions; registers page in docs.json
  • New example examples/07_multi_agent.py showing a coordinator using two AgentTool sub-agents (browser, coding) with CLI options
  • Updates hud/agents/resolver.py to detect Codex-capable models (e.g., gpt-5.1, gpt-5.1-codex) and route them to OpenAIAgent, checking only the matched identifier (not aliases)
  • Extends tests in hud/agents/tests/test_resolver.py to cover Codex routing, alias handling, and provider mapping

Written by Cursor Bugbot for commit 971f613. This will update automatically on new commits. Configure here.

Comment thread hud/agents/orchestrator.py Outdated
Comment thread docs/cookbooks/multi-agent.mdx Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7550f70b0e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread hud/agents/resolver.py
Comment on lines +68 to +72
candidate_ids = (m.get("id"), m.get("name"), m.get("model"))
if model in candidate_ids:
# Only check if the matched model string is codex-capable
if _is_codex_capable_model(model):
return AgentType.OPENAI.cls, m

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Detect codex capability from matched model entry

The codex routing check is based on the user-supplied model string, not the gateway entry that actually matched. If a codex-capable model is exposed under an alias that doesn’t include “codex” (e.g., id primary with model: gpt-5.1-codex), this branch will skip OpenAIAgent and fall back to provider mapping, so create_agent will still use the codex model_id but with OpenAIChatAgent, which won’t support codex native tools. Consider checking codex capability on the matched gateway model field (or the specific matched candidate) rather than the raw input.

Useful? React with 👍 / 👎.

- Add multi-agent example with conductor and sub-agents
- Add skills documentation (overview, authoring guide, orchestration)
- Fix codex model routing to check only matched ID
- Remove unsafe eval() from docs example
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant