monsieurleon

Appreciate that. Exactly the idea: less prompt-tweaking, more structured context. Glad it was what you were looking for

Good question. Codex already supports the AGENTS.md file. I’m not trying to replace that.

This project does one narrow thing: it turns those agents into callable, auditable sub‑agents you can invoke at runtime as an MCP tool.

What it adds on top of Agents/AGENTS.md:

- Runtime delegation: a single MCP tool delegate(task, agent|persona, profile, …) that the outer session (or you) can call mid‑flow. Not just “pick one agent at start,” but spin up a specialist for a subtask and return the result.

- Introspection & CI gates: list_agents and validate_agents are exposed as tools so the model (and CI) can see what’s allowed and fail misconfig before anything runs.

- Isolation defaults: each call runs in a temp workdir; you can point Codex at a git worktree/mirror so sub‑agents don’t write into your main repo. Profiles keep state separate.

- Ops hygiene: server is tiny, no stdout (MCP handshake‑safe), debug → stderr only, and the server itself makes no runtime network calls. Small surface area to audit.

Under the hood it still writes AGENTS.md for the selected persona and executes codex exec --profile <agent-profile> "<task>". So if you’re happy manually choosing agents and running codex exec, you don’t need this. If you want in‑session delegation + CI validation + safer defaults with minimal moving parts, that’s the point.

If I’m missing a built‑in way to get all of the above from Agents alone, I’d love a pointer.

That’s great ! Does the extension work with APIs UIs like open-webui or LibreChat?