Codex
f4fae71fe3
2.6 KiB
Priorities
The ranked work queue for the autonomous improvement loop. The architecture-review pass (the architect) owns this file: each run it turns the roadmap plus an internal scan (gaps in the services → agents → workflows lifecycle, API coherence, drift, tech debt, test and DX friction) into a single ordered list — highest-value first — and links each item to a tracking issue. The hourly continuous-improvement pass works the top item whose issue is still open. So the architect decides what, and the increment loop builds it.
Reading / editing. An item is done when its linked issue closes (the increment
that builds it adds Closes #<issue>). Roadmap phase (Now → Next → Later) is the
primary ordering; internal findings are interleaved by value, not kept in a
separate list. The human can reorder this list — or the issues — at any time to
redirect the loop; direction always wins.
Off-limits to the loop (the architect proposes these as notes, never as queue items the loop can auto-merge): brand/positioning copy, breaking public-API changes, architectural rewrites. Those go to the human.
Work queue (ranked)
- Handle AtlasCloud Minimax 400s for native service tools (#4354) — The previous AtlasCloud marker retry item (#4348) shipped, but the live provider has now exposed an earlier Now-phase conformance break: Minimax rejects native service-tool payloads in the agent, universe, and A2A stream fallback harnesses. Fixing the single-service-tool path restores the services-as-tools promise behind first-agent trust and unblocks several live adoption-facing examples without changing public APIs.
- Fix AtlasCloud Minimax tool follow-up retry after tool results (#4355) — Once native tool payloads are accepted, the next AtlasCloud gap is the follow-up retry transcript after a tool result. This protects plan/delegate plus service side effects from failing after partial work, directly supporting the services → agents → workflows lifecycle under real provider behavior.
- Trace agent RunInfo in OpenTelemetry spans (#4315) — After the live conformance regressions are stable, the highest Next-phase operability gap is connecting existing run metadata to traces so real agent runs can be debugged across steps, tool calls, delegation, failures, services, and flows without inventing a new surface.
Seeded by Claude Code from the roadmap + open issues; thereafter maintained by the architecture-review pass.