[Bug] Unpinned native Codex sessions follow Astra instead of the Omnigent default

[yaoharry]

Description

An unpinned native Codex session launches on GPT-6 Astra when Codex marks Astra as its catalog default, even though Omnigent defines CODEX_DEFAULT_MODEL as gpt-5.6-sol. Expected: Omnigent should use Sol when Sol is available, while preserving an explicit user or provider model pin.

Steps to reproduce

1. Use a Codex catalog that includes system.ai.gpt-6-astra with isDefault: true and also includes system.ai.gpt-5-6-sol.
2. Start a native Codex session without an explicit model override.
3. Observe that Omnigent pins Astra from the catalog default row.

Concrete code-path evidence: mark_launch_default() keeps Codex’s default marker for an unpinned catalog, and the native runner later pins the row marked isDefault.

Version

0.15.0.dev0

OS

Linux

Harness

Codex

Harness mode

Native

Platform or device

Linux

Observed impact

Sessions using an unpinned catalog where Codex marks Astra as default.

Authentication type

Databricks

[github-actions]

🤖 Automated triage

• Bot assessment: Medium impact
• Priority: P2-medium
• Evidence: concrete code-path analysis
• Why: Unpinned native Codex sessions can start on Astra instead of Omnigent's configured Sol model, affecting session creation and model selection but remaining workable by explicitly pinning the desired model.

This automated assessment uses the issue content and repository signals. Maintainers can override the priority label.

[github-actions]

Thanks for reporting this. #4063, #3366, #4115 may be related, and have already been fixed — so the fixes may have shipped after the build you're on.

Could you check whether you're on a version that includes them? If you are and this still happens, say so here — that makes it a regression rather than a duplicate, and we'll keep this open.