Skip to content

VS Code extension intermittently reports “Codex process is not available” with gpt-5.6-sol and personality fallback warning #32013

Open

Description

@liquiphyofficial-ux

Environment

  • IDE: Visual Studio Code on Windows
  • Codex extension version: 26.707.31428
  • Model: gpt-5.6-sol
  • Reasoning effort: ultra
  • config.toml contains:
model = "gpt-5.6-sol"
model_reasoning_effort = "ultra"
personality = "none"
service_tier = "default"

[windows]
sandbox = "elevated"
  • The Codex UI personality selector only exposes Friendly or Pragmatic. Pragmatic was selected in the UI even though config.toml says personality = "none".

Issue

The VS Code Codex panel intermittently crashes and displays:

Codex process errored: Codex process is not available

codex_protocol::openai_models: Model personality requested but model_messages is missing, falling back to base instructions.
model=gpt-5.6-sol personality=pragmatic

Reloading Codex restores the UI. In at least one occurrence, after reloading and reopening the panel, Codex continued working on the previously assigned goal. This suggests the underlying task/session may still be alive or recoverable while the local extension process/UI connection fails.

Reproduction observed

  1. Configure gpt-5.6-sol with model_reasoning_effort = "ultra".
  2. Keep personality = "none" in config.toml.
  3. Select Pragmatic in the Codex UI because the UI does not provide a None option.
  4. Use Codex normally on a codebase.
  5. The panel may later show Codex process is not available together with the missing model_messages personality fallback warning.
  6. Reload Codex.
  7. The task may resume, indicating a recoverable extension/process failure rather than a full task failure.

Expected behavior

  • The VS Code extension should not become unavailable because personality metadata is missing.
  • If a model does not support personalities, the UI should provide a None option or clearly disable the selector.
  • A personality fallback warning should remain non-fatal.
  • If the background task remains active, the panel should reconnect without presenting a full process-crash screen.

Additional context

OpenAI status showed only a FedRAMP-specific incident at the time, so this did not appear to be part of a general service outage.

There are existing issues containing the same model_messages is missing warning for other models, but I did not find an exact report combining gpt-5.6-sol, the VS Code extension, the UI/TOML personality mismatch, and the recoverable Codex process is not available state.

Activity

  1. added
    bugSomething isn't working
    extensionIssues related to the VS Code extension
    windows-osIssues related to Codex on Windows systems
    connectivityIssues involving networking or endpoint connectivity problems (disconnections)
    configIssues involving config.toml, config keys, config merging, or config updates
    on Jul 10, 2026
  2. liquiphyofficial-ux commented on Jul 10, 2026

    @liquiphyofficial-ux
    Author

    Additional confirmation: selecting Pragmatic in the Codex Personalization UI directly rewrites C:\Users\omery\.codex\config.toml, changing:

    personality = "none"

    to:

    personality = "pragmatic"

    The screenshot after selecting Pragmatic shows the persisted config value as personality = "pragmatic". This confirms the UI is not merely applying a temporary session preference; it mutates the host config file. Because the UI currently exposes only Friendly or Pragmatic and no None option, a user cannot select the UI without re-enabling personality for a model that then logs model_messages is missing. This strengthens the case for either adding a None option, disabling the selector for unsupported models, or preventing the fallback warning from coinciding with a process-unavailable state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingconfigIssues involving config.toml, config keys, config merging, or config updatesconnectivityIssues involving networking or endpoint connectivity problems (disconnections)extensionIssues related to the VS Code extensionwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions