Idle SSH remote threads fail after restarting connection with AbsolutePathBuf deserialized without a base path #31983

What version of the Codex App are you using?

ChatGPT desktop app powered by Codex & OWL:

• Version: 26.707.31428
• Release date: July 10, 2026

What platform is your computer?

Local machine:

• Windows 11 Pro
• Version: 25H2
• OS build: 26200.8037
• Windows Feature Experience Pack: 1000.26100.300.0

Remote host:

• Ubuntu 26.04 LTS (Resolute)
• Kernel: Linux 7.0.0-27-generic
• Architecture: x86_64
• Hostname: genarrative-station
• Kernel mode: SMP, PREEMPT_DYNAMIC

What issue are you seeing?

After using Settings > Connections > SSH > Restart connection, previously idle remote conversations can no longer be continued.

Sending a new message in an affected conversation fails with:

Invalid request: AbsolutePathBuf deserialized without a base path

There is an important distinction:

• A conversation that had an active task running when the SSH connection was restarted continues to work normally afterward.
• Conversations that were idle when the connection was restarted fail when attempting to continue them.

Fully restarting the ChatGPT desktop app restores the affected conversations, so the persisted conversation itself does not appear to be corrupted. The issue seems limited to in-process restoration of the remote thread/workspace path context after an SSH connection restart.

What steps can reproduce the bug?

1. Connect to a Linux remote host using the desktop app's SSH connection feature.
2. Open a remote project and create at least two conversations.
3. Leave one conversation idle and keep a task running in the other conversation.
4. Open Settings > Connections.
5. Open the menu for the SSH connection and select Restart connection.
6. Return to the conversation that had an active task and continue it. It works normally.
7. Return to the conversation that was idle and send a message.
8. Observe the error:

Invalid request: AbsolutePathBuf deserialized without a base path

What is the expected behavior?

All remote conversations associated with the SSH host/project should restore their working-directory context and remain usable after restarting the SSH connection.

Workaround

Quit and restart the ChatGPT desktop app. After the full app restart, the previously affected conversations can be continued normally.

Additional information

This may be a cold-restoration/path-context issue: active conversations appear to retain enough runtime context across the SSH restart, while idle conversations are rehydrated without the base path required by AbsolutePathBuf.

Screenshots of the error and the Restart connection action are available if needed.