Codex Windows App via Remote Connections does not inject memories while CLI does with same CODEX_HOME

What version of Codex is running?

• Codex CLI on the remote Linux host: codex-cli 0.130.0
• Codex App/Desktop: running on Windows, connected to the Linux host using the Codex Remote Connections flow documented at https://developers.openai.com/codex/remote-connections
• App-server process observed on the remote Linux host: codex app-server --listen unix:// from the same Codex install path as the CLI

Subscription

Not relevant / not sure this is subscription-specific.

Model

gpt-5.5

Platform

Remote host: Linux x86_64:

Linux 6.8.0-94-generic x86_64 GNU/Linux

Client: Codex App/Desktop running on Windows, using Remote Connections to connect to the Linux host above.

What issue are you seeing?

With the same CODEX_HOME on the remote Linux host, memory works from Codex CLI but a new Codex App session connected via Remote Connections does not appear to inject the same memories into the agent context.

The relevant remote host config has memories enabled:

[features]
memories = true

[memories]
use_memories = true
generate_memories = true

The CLI on the remote host can write/read memory files under ~/.codex/memories. For example, a user-approved project preference was saved in:

~/.codex/memories/alioth-local-build.md

The file contains a project-specific local build preference, and rg confirms it is present in the memory store. A new CLI session can use this memory. However, a new Windows Codex App session connected to the same host through Remote Connections, using the same remote CODEX_HOME, does not recall or inject that memory unless the user explicitly asks it to read the file path manually.

Steps to reproduce

1. On a Linux remote host, configure Codex with memory enabled:

```toml
[features]
memories = true

[memories]
use_memories = true
generate_memories = true
```

1. Connect to that Linux host from the Windows Codex App using the Remote Connections feature: https://developers.openai.com/codex/remote-connections

1. In Codex CLI on the same remote host and same CODEX_HOME, save or generate a memory under ~/.codex/memories, for example a simple project preference.

1. Confirm from the remote CLI that the memory exists:

``bash
rg -n 'Ninja|ccache|project preference' ~/.codex/memories
``

1. Start a new Codex CLI session in the same project and ask about the saved preference. The CLI can use the memory.

1. Start a new Windows Codex App session connected to the same remote host/project through Remote Connections, same remote user, same remote CODEX_HOME, and ask about the same saved preference.

Expected behavior

Codex App sessions connected through Remote Connections should inject or otherwise make available the same enabled memories that Codex CLI uses on the remote host when both are using the same remote CODEX_HOME and the same trusted project.

At minimum, the App should expose diagnostics showing whether memory is enabled, disabled, read-only, unavailable, or filtered out for the remote session.

Actual behavior

The remote CLI memory pipeline works, but a new Windows Codex App session connected through Remote Connections does not appear to receive the saved memory in its context.

The App session can still read the memory file manually if asked to inspect the path, so this looks like a Remote Connections/App memory injection/runtime wiring difference rather than a missing file.

Local diagnostics

Memory config and trusted project are present in the remote host ~/.codex/config.toml.

The remote memory files exist:

~/.codex/memories/alioth-local-build.md
~/.codex/memories/raw_memories.md

The app-server socket/process was checked on the remote host. After local state recovery, the malformed state DB issue was no longer the primary symptom; the remaining issue is specifically that Windows Codex App sessions over Remote Connections do not appear to inject the memory that the remote CLI can use.

Related issues

These look related but not exact duplicates:

• #20987: memory enabled in config but runtime injects read-only memory instructions
• #19758: request for topic-based memory directory and agent-initiated memory_write
• #17496: memory read path / project scope issue
• #18343: scoped memory management for global/project/thread memories

I did not find an existing issue specifically tracking: remote CLI can use memories from the same remote CODEX_HOME, while Windows Codex App sessions connected through Remote Connections do not inject them.