bug: File preview serves stale content for unchanged file paths

Hello,

I discovered that the in-app file preview keeps showing stale content when a workspace file is modified in place (same path, new content), because the mutable file endpoints send no cache policy and the preview refresh does not bypass the browser cache.

Steps to reproduce:

1. Create an HTML file in the workspace (e.g. a generated report).
2. Open it from the chat file card (HTML preview in the app).
3. Modify or regenerate the file in place (same path, new content, new mtime).
4. Re-open the preview and/or press the refresh button in the preview header (multiple times).
5. Observe that the stale version is still rendered, even after several refreshes.
6. Copy the new content to a file with a different name and preview it. The new content is shown immediately.

Expected behavior:

• The preview renders the updated file content after the file is modified in place.

Actual behavior:

• The preview keeps rendering the stale version indefinitely. Pressing the refresh button or re-opening the preview does not help.

Root cause analysis:

1. Backend: mutable file endpoints send no cache policy

cptr/routers/workspace.py defines three mutable file endpoints:

• serve_static() for GET /api/workspace/files/serve/{file_path:path} (lines 911-935)
• view_file() for GET /api/workspace/files/view (lines 813-834)
• download_file() for GET /api/workspace/files/download (lines 840-854)

All three return a plain FileResponse with no Cache-Control or Expires header. Measured live response for the /serve endpoint:

HTTP/1.1 200 OK
content-type: text/html; charset=utf-8
accept-ranges: bytes
content-length: 236299
last-modified: Mon, 31 Aug 2026 16:13:17 GMT
etag: "6b640272f48391eebd93dfeb0a538543"

(no Cache-Control, no Expires)

Without a cache directive, browsers and WebViews apply heuristic caching to 200 responses and may serve the stored body for an unbounded time. These endpoints serve mutable files behind stable path-based URLs, which is exactly the case that requires an explicit cache policy.

Note: the server also ignores If-None-Match (always 200, never 304). I verified this by re-requesting with the previous ETag after modifying the file, so even a revalidating client cannot benefit server-side. The observed behavior indicates the client does not even revalidate.

Contrast: routers/files.py:82 (immutable upload blobs) correctly sends Cache-Control: public, max-age=31536000, immutable, so the workspace file endpoints appear to have simply been missed.

2. Frontend: preview uses a stable URL and a cache-respecting reload

In the bundled frontend build (cptr 0.9.21, frontend/build/_app/immutable/nodes/2.*.js), the chat HTML preview renders:

<iframe sandbox="allow-scripts allow-same-origin" class="preview-iframe"></iframe>

with src set to /api/workspace/files/serve/${filePath}, a stable URL per file path. The preview toolbar's reload action performs a plain iframe.contentWindow.location.reload(). A regular location.reload() respects the HTTP cache (no cache-busting parameter, no bypass), so once the WebView has cached the 200 response for that URL, the refresh button re-serves the cached body.

Suggested fixes:

• Server (recommended, fixes all clients): add an explicit cache policy to the mutable file endpoints (/api/workspace/files/serve/*, /view, /download), either Cache-Control: no-store (simplest), or Cache-Control: no-cache plus 304 handling for If-None-Match / If-Modified-Since. The ETag and Last-Modified headers are already sent by FileResponse, so revalidation would be cheap.
• Frontend (defense in depth): append a cache-busting query parameter to the preview iframe URL on every open and on refresh (e.g. ?v=<file mtime> or ?t=<Date.now()>). The /serve route is path-based and ignores the query string, so this works without any server change. Alternatively, make the refresh action perform a cache-bypassing reload.

Workaround:

Preview a copy under a new file name, or open the file in an external browser.

Thank you for your time and consideration.

Best regards,
Joshua Krimmer

Start in cptr/routers/workspace.py at serve_static(), view_file(), and download_file() around the cited lines, then compare their FileResponse headers with routers/files.py:82. Reproduce the stable-URL preview behavior and verify that updated in-place files are served after reopening or refreshing, with an explicit cache policy covering all three mutable endpoints.