Summary
Artifact links created by a Codex/GPT-5.6 session can fail to open in Happier with:
File does not exist
The file does exist in the session that created it, but the file preview RPC appears to resolve the path from the daemon/workspace process instead of the session context that produced the artifact.
Example
A Codex response linked a markdown artifact like:
project/<repo>/docs/product/native-ios-visual-audit-2026-07-17.md
Clicking it opened the Happier preview panel, but preview returned File does not exist.
Why this matters
In containerized/self-hosted deployments, the agent session and the Happier daemon may not share the same absolute filesystem view. A path that is valid inside the agent session can be invalid from the daemon process, even though both refer to the same logical workspace file.
Expected behavior
Happier should resolve artifact preview/stat/read requests relative to the originating session/workspace context, not only relative to the daemon process filesystem.
Local validation
We confirmed the issue by adding a local resolver before the file preview stat/readFile handlers. Once the artifact path was mapped back to the active session workspace, the existing artifact opened correctly.
This local resolver is only a workaround for our deployment; the upstream fix should use Happier's own session/workspace metadata to resolve artifact paths at the file-preview boundary.
Summary
Artifact links created by a Codex/GPT-5.6 session can fail to open in Happier with:
File does not existThe file does exist in the session that created it, but the file preview RPC appears to resolve the path from the daemon/workspace process instead of the session context that produced the artifact.
Example
A Codex response linked a markdown artifact like:
project/<repo>/docs/product/native-ios-visual-audit-2026-07-17.mdClicking it opened the Happier preview panel, but preview returned
File does not exist.Why this matters
In containerized/self-hosted deployments, the agent session and the Happier daemon may not share the same absolute filesystem view. A path that is valid inside the agent session can be invalid from the daemon process, even though both refer to the same logical workspace file.
Expected behavior
Happier should resolve artifact preview/stat/read requests relative to the originating session/workspace context, not only relative to the daemon process filesystem.
Local validation
We confirmed the issue by adding a local resolver before the file preview
stat/readFilehandlers. Once the artifact path was mapped back to the active session workspace, the existing artifact opened correctly.This local resolver is only a workaround for our deployment; the upstream fix should use Happier's own session/workspace metadata to resolve artifact paths at the file-preview boundary.