2 people reported

All time, since Oct 3.

Delegated owner consent rejected

“Later sends to the same conversation were rejected because owner consent forwarded from the parent was treated as untrusted.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/13694/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Forwarded owner consent rejected for delegated tasks on Windows. Later sends from the parent Dot conversation are refused under the original scope; direct confirmation fails with AbsolutePathBuf error.

Is this your bug?

File my report
Where
Dot delegated tasks
Error text
invalid turn/start params: AbsolutePathBuf deserialized without a base path
Versions
0.156.1 to 26.930.41038
Platforms
Windows
How bad
Breaks a normal workflow.

Part of: Delegated task approval not recognized8 bugs

  1. Direct approval rejected as untrusted18 people
  2. Forwarded approval rejected17 people
  3. /approve command unavailable8 people
  4. Relayed approval rejected2 people
  5. Forwarded authorization rejected2 people
  6. Auto-review rejects delegated commands2 people
  7. Auto-review cites superseded restriction2 people

Original reports2, newest first

  1. [Windows/dot] Delegated consent accepted once then rejected; direct confirmation blocked by AbsolutePathBufOn GitHub#51320
  2. Windows/Dot: later owner-approved scope rejected at delivery after implementation; direct consent fallback failsOn GitHub#50673

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.