/export ignores theme.export.pageBg in HTML export

[jwu]

What happened?

When exporting a session with /export, the generated HTML does not use the theme’s export.pageBg value. From the code, export.cardBg and export.infoBg also appear to be ignored.

The export code reads these theme values, but the final HTML backgrounds are still derived from userMessageBg instead of using the explicit export colors.

Steps to reproduce

1. Create or modify a theme with a clearly distinct
   export.pageBg value:

     {
       "export": {
         "pageBg": "#ff00ff"
       }
     }

2. Start pi with that theme active.
3. Run /export.
4. Open the exported HTML file.

Expected behavior

The exported HTML page background should use theme.export.pageBg exactly, rather than a derived color.

Version

0.62.0

[github-actions]

Hi @jwu, thanks for opening an issue.

OSS weekend is active until Monday, March 30, 2026, so new issues are being auto-closed for now.

Please reopen or submit this issue again after Monday, March 30, 2026. For support, join Discord.

[badlogic]

Fixed on main.

Root cause was in packages/coding-agent/src/core/export-html/index.ts: generateThemeVars() read theme.export.pageBg/cardBg/infoBg, but generateHtml() still filled the actual CSS placeholders from deriveExportColors(userMessageBg), so the explicit export colors never reached the final HTML.

The fix makes generateHtml() prefer getThemeExportColors(themeName) for page, card, and info backgrounds, with the existing derived colors kept only as fallback when an export color is unset.

npm run check passes.