[Bug]: Agent device access reported disabled despite enabled setting#31394

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

Not sure

Steps to reproduce

1. Enable Agent device access in Settings > Integrations > Devices.
2. Reload T3 Code and start a new agent session.
3. Ask the agent to list devices with device_list.

Expected behavior

The new session can list and control available devices when Agent device access is enabled.

Actual behavior

The tool returns: Agent device access is turned off for this environment. Ask the user to turn on Agent device access in Settings > Integrations > Devices; it applies when the agent session next starts, such as in a new thread.

The user confirmed the setting was enabled before starting a new session, and the problem persisted after reloading T3 Code. An Android emulator was connected and visible through adb devices as emulator-5554.

Impact

Major degradation or frequent failure: agent device control is unavailable.

Version or commit

Server version 0.1.8-nightly.20261105.4205.

Environment

Linux x64, Ubuntu 22.04.5 LTS; local environment; Codex provider, gpt-6.1-terra. The same error was also observed in a Claude agent session.

Logs or stack traces

The full device tool error is quoted above.

Workaround

ADB can see the emulator independently; no workaround for T3 agent device access was established.