Skip to content

[Bug]: OMP native chat rejects every message when the saved model differs from OMP's default and no effort is saved #31995

Closed

Description

@pandudpn

Operating system

Linux x64 (Ubuntu 24.04, kernel 6.8), Orca running headless via orca serve, clients paired over the network.

Orca version

1.4.237 (orcad 0.1.0+033018f7660d), OMP 18.12.6. The same code is on main at 4dd97f02d5.

Details

Summary: An OMP Chat UI session whose saved options hold a model but no effort rejects every message with "OMP didn't accept this message", including plain text like T. The prompt never reaches OMP. This is the ACP counterpart of #31849 (Pi).

Evidence from agent-session-journal.db (7 OMP sessions on 2026-10-22):

Session record_json.options Dispatch results
omp_604903a8… {"model":"omniroute/coding-max"} rejected ×3
omp_0bf78e10… {"effort":"xhigh","model":"omniroute/chat"} accepted ×4
omp_004cc2e0… {"effort":"xhigh","model":"omniroute/chat"} accepted ×3
omp_628c5ebc… {"model":"omniroute/coding-max"} rejected
omp_32fd2f3c… {"model":"omniroute/coding-max"} rejected
omp_db95763e… {"model":"omniroute/coding-max"} rejected
omp_ac25c623… {"model":"omniroute/coding-worker"} rejected

OMP starts every session on omniroute/chat with thinking: xhigh. Each rejected send is submission → dispatch pending → dispatch rejected with rejection: {"kind":"providerRejected"} and no detail. The OMP session file holds no user message.

Root cause: applyAcpMessageOptions (src/main/acp/acp-message-execution-options.ts). For a message whose model differs from the session's start model, the effort to send comes from read().models.find(...)?.defaultEffort. OMP's session/new reports a thinking option (category thought_level) but no per-model effort menu, and OMP's dialect has no modelEfforts, so that default is undefined. The guard then throws because the session reports a current effort:

if (session.options.picked.has(key) || session.options.reported()[key] !== undefined) {
  throw new AgentSessionOptionRejectedError(
    new Error(`The default ${key} for this model is unknown`)
  )
}

reported().effort is defined for any agent that reports a thought_level option, so every model-only message to a non-start model is refused before session/prompt is written. The handover turns this into providerRejected.

Reproduced against the real adapter with the existing scripted-agent rig (openAcpAdapterRig, Grok config options): dispatch({ executionOptions: { model: 'grok-4.6' } }) rejects with The default effort for this model is unknown, and no session/prompt frame is sent.

OMP accepts the prompts directly: omp acp driven by hand with the same --plugin-dir, ORCA_* environment, a set_config_option to omniroute/coding-max and the exact rejected text returns stopReason: "end_turn".

Steps to reproduce

  1. Enable Settings → Experimental → Chat UI.
  2. In an OMP chat, pick a model other than OMP's default without picking an effort.
  3. Open a new OMP chat and send any message.

Expected: OMP receives the prompt and keeps the thinking level it uses for the model.
Actual: "OMP didn't accept this message." on every message in that chat.

Workaround: Pick an effort along with the model, or use the OMP terminal view.


This is an ACP-native version of the Pi report in #31849. Note that #31927 (fix: keep chat option actions independent of inventory) also rewrites applyAcpMessageOptions; a narrow fix that only relaxes the guard is in preparation.

Activity

  1. nwparker commented on Oct 24, 2026

    @nwparker
    Contributor

    Thanks for the detailed report, @pandudpn. Chats failing with a model-only change (no known default effort for the selected model) were fixed in #32004 (shipped in v1.4.239): the guard now only refuses when Orca has already applied a value that differs from the agent's initial one, for both ACP and Pi RPC chats. Could you try the latest build? If it still happens, please reply or reopen with the details.

  2. pandudpn commented on Oct 25, 2026

    @pandudpn
    ContributorAuthor

    Thanks @nwparker. I updated both sides to 1.4.239: the macOS desktop app, and the headless orca serve built from source at a commit that contains 752f531 (#32004), with out/main rebuilt and the serve restarted. New OMP chats still fail. #32004 fixed the send path; this failure happens earlier, when the chat is created.

    What happens: the composer seeds a new OMP chat with {"model":"omniroute/coding-max","effort":"xhigh"}. The host refuses the create with agent_session_operation_invalid / optionRejected, the desktop shows "Chat connection could not be confirmed.", and no session record is written.

    Why: assertAgentSessionOptionsAdmitted (src/main/runtime/agent-session-record-options.ts) checks the effort against the saved catalog row. For OMP, every model other than the probe session's current one has efforts: []:

    omniroute/chat        efforts: [off, auto, minimal, low, medium, high, xhigh]
    omniroute/coding-max  efforts: []          (no effortsKnown flag)
    

    The empty list comes from read() in src/main/acp/acp-structured-options.ts:

    const sessionMenu = { efforts: model.id === currentModel ? sessionEfforts : [] }

    OMP's dialect has no modelEfforts, so non-current models get []. agentSessionEffortLevels treats an explicit empty list as "admits none", and coding-max + xhigh is refused even though OMP runs that pair fine.

    Evidence: on 1.4.237 I sent agentSession.create straight to the serve:

    options result
    {model: 'omniroute/coding-max'} ok
    {model: 'omniroute/coding-max', effort: 'xhigh'} optionRejected
    {model: 'omniroute/chat', effort: 'xhigh'} ok

    I haven't rerun that probe on 1.4.239. The code above is the same in both versions, and the seed and catalog rows on my 1.4.239 host match the failing case.

    Fix: I updated #31998 (its original send-path change is covered by #32004) to mark those rows { efforts: [], effortsKnown: false } when the agent reports a thought_level option without a per-model menu. Admission then lets the effort through and the agent decides. Current-model rows and dialects that advertise menus are unchanged.

    Workaround: pick omniroute/chat before opening the chat, then switch models.

  3. added a commit that references this issue on Oct 25, 2026
    7e8bf3d
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions