openai / openai/codex

Codex Desktop: connector write tool remains read-only despite Full Access permissions

Open
#42,095 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug sandbox tool-calls windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Codex Desktop 26.825.6671.0 / codex-cli 0.151.0-alpha.7.2
Windows x64, build 26200

The IOL Invertironline connector rejects its write operation even though:

  • The task runs with danger-full-access.
  • The connector-specific permission is “Allow all actions”.
  • validate_order succeeds and returns a valid validation ID.
  • The operation was explicitly confirmed by the user.

Calling place_order immediately afterward fails with:

This session is read-only. Tool 'place_order' is not allowed.
error_code: INVALID_ARGUMENT

The tool event reports readOnlyHint: false. No order is created. The same behavior occurs in multiple newly created tasks.

Expected behavior: after explicit confirmation and successful validation, the write operation should execute or request the appropriate approval. The connector session should not remain read-only when Full Access is effective.

No account information, instrument, quantity, validation token, or session transcript is included.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue on Windows x64 with Codex Desktop 26.825.6671.0 and codex-cli 0.151.0-alpha.7.2, then trace connector permission handling around the read-only session and readOnlyHint. Done means place_order executes or requests the appropriate approval after validation and explicit confirmation with Full Access enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
authorization, cli, desktop-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.