正在打开每日关注
正在打开每日关注
介绍如何配置 Astra、Luna、Sol 的 Codex 子代理树,并通过项目配置、Skill 或 Herdr 复用。
A lot of people have asked how to configure this cost-efficient Astra + Luna + Sol agent tree and get it working. There are a few ways to use it, depending on how you normally use Codex. 1. Have Codex configure it Give Codex the diagram and ask it to set up project-level custom agents. Specify the model and model_reasoning_effort for each role, and save the rules for assigning work. Once the configuration is loaded in a fresh session, Astra can call subagents using those roles. 2. Turn it into a Skill If you use this setup often, put the role configuration templates into a Skill, along with when to use each role and how to collect its results. Set it up the first time, then use it as needed without explaining the whole tree every time. 3. Use it through Herdr If you already use Herdr, you can launch and manage Codex CLI there. Herdr manages the sessions, while Astra assigns work within Codex using the same role configuration. No need to change the setup just to use Herdr. Whichever approach you use, make sure the role configuration is active. Writing “have Luna explore and Sol implement” in chat or AGENTS.md doesn’t mean the model has switched. You can ask Codex to check the subagent session logs to confirm the model and reasoning effort. If you just want to get started, the first option is enough. Small tasks don’t need the whole tree, either. Of course, everyone’s experience with quota usage across models is different, so you can adjust the models and effort levels to suit your own usage.
Codex tip: A cost-efficient Luna + Sol agent tree, orchestrated by Astra. Effort levels chosen by weighing DeepSWE’s pass rates, average cost per task, and agent steps. Hand this to Codex to set it up 👇 https://t.co/1s0YC8zkps
是什么 这是一条面向 Codex 用户的实践建议,核心是把 Astra 作为主编排者,把 Luna 与 Sol 配成职责、模型和推理强度不同的子代理,并按规则分派任务。它同时给出三种落地路径:由 Codex 写入项目级自定义 Agent;将角色模板、适用时机和结果汇总方式封装为 Skill;或通过 Herdr 管理 Codex CLI 会话。
核心设计 价值不在于简单增加模型数量,而在于把协作协议显式化:每个角色要有稳定的模型与 model_reasoning_effort,主代理要知道何时调用、如何接收结果,配置还必须在新会话中实际加载。作者特别强调,聊天文字或 AGENTS.md 中的自然语言要求不会自动完成角色切换,需检查子代理会话日志确认生效。
关键洞察 对经常重复的工程任务,Skill 是可复用边界;Herdr 更像会话运营层,编排逻辑仍留在 Codex。成本优化应结合任务规模、模型配额、通过率和步骤数动态取舍,小任务不必启动完整树。
边界与风险 文中未提供具体角色职责、模型名称、配置文件示例或实测数据,因此不能据此断言该树的通用收益。多代理也会增加上下文传递、协调、日志审计和失败重试成本;若没有可验证的分派规则,复杂度可能抵消额度节省。重视可复现性的团队还应补充配置版本化、输出契约和评估基线。