Delegated agents lose local Docker access and report false usage-limit errors for goals #54023

Summary

Two reproducible Codex issues affect delegated agents.

1. Delegated agent cannot access local Docker

The local Codex environment can use Docker successfully:

whoami
korone\\notal

docker context show
desktop-linux

docker run --rm python:3.12-slim python --version
Python 3.12.15

The delegated agent runtime is separate and consistently fails with:

Access denied: C:\\Users\\notal\\.docker\\config.json
permission denied: //./pipe/docker_engine

This remains broken after:

• Switching to the desktop-linux context.
• Reconnecting the agent.
• Enabling Full access.
• Setting default_permissions = ":danger-full-access".
• Setting approval_policy = "never".
• Setting Windows native sandbox mode to elevated.

Expected behavior: a delegated agent created for the same local environment should either inherit the local Docker access or clearly expose that it is running in a separate runtime before the task starts.

2. Bot-created agents trigger a false usage-limit error

It is not possible to reliably navigate to a chat for an agent created by Codex and set a goal for that agent. The coordinating bot also cannot set a goal for that created agent. When attempting this, Codex reports that the usage limit has been reached even when the account usage display is below the limit, including cases around 90% remaining/available usage.

This behavior was reproduced and verified. The failure affects both:

• Opening the bot-created agent chat and setting a goal there.
• Having the coordinating bot set a goal for that agent.

Expected behavior: the goal operation should succeed when the account has available usage, or return an accurate error that identifies the actual blocked resource.

Environment:

• Windows
• Codex desktop/CLI
• Docker Desktop 4.95.0
• Docker Engine 29.8.2
• Docker context desktop-linux

Screenshots and exact timestamps can be attached if needed.