Allow users to opt out of forced Fast tier for explorer and librarian subagents

[fede-oss]

Summary

LazyCodex 4.16.3 installs explorer and librarian Codex subagent configurations with service_tier = "fast". As a result, these agents use Fast service even when the user explicitly asks for Standard/default mode in the prompt; there is no documented LazyCodex opt-out that survives bootstrap/reinstallation.

Environment

• LazyCodex version: 4.16.3 (latest release as of 2026-07-11)
• Codex version: 0.144.1 (latest release as of 2026-07-11)
• OS: macOS Darwin 24.6.0 arm64
• Install method: LazyCodex/OMO plugin marketplace and bootstrap-managed agent configs
• Relevant config: ~/.codex/config.toml maps [agents.explorer] and [agents.librarian] to ./agents/explorer.toml and ./agents/librarian.toml

Repository Decision

• Target repository: code-yeongyu/lazycodex
• Why this belongs there: the current LazyCodex bundle and the generated files under ~/.codex/agents/ explicitly set the Fast service tier. The behavior is therefore reproducible from LazyCodex-managed configuration, independent of prompt wording.
• LazyCodex evidence: at source commit 9b9f8e8, plugins/omo/components/ultrawork/agents/explorer.toml:6 and librarian.toml:6 both contain service_tier = "fast". The installed 4.16.3 copies contain the same setting.
• Upstream Codex evidence: Codex loads the installed TOML files through [agents.explorer].config_file and [agents.librarian].config_file. Related upstream reports include Codex App subagents appear to use Fast mode despite Standard speed and fast opt-out openai/codex#30407 and Subagents sometimes spawned with service_tier=priority openai/codex#29940, but neither addresses LazyCodex hard-coding the tier in its distributed agent files.

Reproduction

1. Install LazyCodex 4.16.3 with its standard bootstrap.
2. Inspect ~/.codex/agents/explorer.toml and ~/.codex/agents/librarian.toml; both contain service_tier = "fast".
3. Start Codex in Standard/default service mode and instruct it to spawn an explorer or librarian subagent without Fast mode (for example, “use Standard, do not use Fast mode”).
4. Observe that the subagent launch configuration still resolves from the agent TOML with service_tier = "fast".

Expected Behavior

LazyCodex should respect a user's explicit Fast-mode opt-out. Either omit service_tier so the parent/default tier is inherited, default it to Standard, or provide a documented installer/config option that controls the generated subagent tier.

Actual Behavior

The bundled agent configuration unconditionally selects Fast for explorer and librarian. Prompt instructions cannot override that launch-time configuration, and bootstrap/reinstallation restores the bundled setting.

Evidence

• Installed manifest: ~/.codex/plugins/cache/sisyphuslabs/omo/4.16.3/.codex-plugin/plugin.json reports version 4.16.3.
• Latest LazyCodex release: v4.16.3, published 2026-07-10.
• Latest LazyCodex source commit inspected: 9b9f8e8.
• Installed files:
  • ~/.codex/agents/explorer.toml:6: service_tier = "fast"
  • ~/.codex/agents/librarian.toml:6: service_tier = "fast"
• Current source files:
  • plugins/omo/components/ultrawork/agents/explorer.toml:6
  • plugins/omo/components/ultrawork/agents/librarian.toml:6
• A non-interactive codex exec probe loaded OMO hooks successfully and exited 0 on Codex 0.144.1, confirming the installed plugin is active rather than a stale unused cache.

Root Cause

Strongly confirmed: LazyCodex ships and bootstrap-links agent TOML files that explicitly set the service tier to Fast. Service tier is launch configuration, so a user-level natural-language instruction to the parent agent does not remove the configured value.

The remaining upstream question is whether Codex should expose a per-spawn tier override or inherit parent opt-out state even when an agent TOML selects Fast. That is tracked separately in openai/codex#30407/#29940 and does not remove the LazyCodex-side need for an opt-out.

Proposed Fix

1. Remove unconditional service_tier = "fast" from the bundled explorer.toml and librarian.toml, allowing Codex's effective/default tier to apply; or gate it behind an explicit LazyCodex installer preference.
2. Preserve user customization during bootstrap/update instead of silently restoring Fast.
3. Document which roles use Fast and how users can opt out globally or per role.

Likely files/components:

• plugins/omo/components/ultrawork/agents/explorer.toml
• plugins/omo/components/ultrawork/agents/librarian.toml
• plugins/omo/components/bootstrap/src/setup.ts
• bootstrap/package smoke tests for generated agent configs

Verification Plan

• Fresh-install LazyCodex with Fast disabled and confirm neither generated agent file forces service_tier = "fast".
• Spawn explorer and librarian workers from a Standard/default parent and confirm usage remains Standard.
• Enable the explicit Fast preference (if added) and confirm only then that both roles use Fast.
• Run bootstrap twice and confirm a user's opt-out is preserved.

---

This issue or PR was generated by LazyCodex.
Tag: lazycodex-generated