[BUG] Task export shows "Unexpected content type: thoughtSignature"

[rossdonald]

Problem (one or two sentences)

When exporting a task from a model that uses thought signatures like Gemini 3, then the markdown has the following:

[Tool Use: read_file]
Files: [
  {
    "path": "path/file.txt"
  }
]
[Unexpected content type: thoughtSignature]

Roo-Code/src/integrations/misc/export-markdown.ts

Line 92 in e2d1599

return `[Unexpected content type: ${block.type}]`

I'm not sure what should be there. Thought signature is an opaque token so it's probably not relevant to the task export.

Context (who is affected and when)

Users who export tasks from models that use thought signatures.

Reproduction steps

Version: 3.36.13
Windows 11
Gemini 3 Flash, Google Gemini Provider

Expected result

No error is shown

Actual result

Shows an error

Variations tried (optional)

None

App Version

3.36.13

API Provider (optional)

Google Gemini

Model Used (optional)

gemini-3-flash-preview

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause:
The formatContentBlockToMarkdown function in src/integrations/misc/export-markdown.ts handles various content block types (text, image, tool_use, tool_result, reasoning) but lacks a case for thoughtSignature blocks. When Gemini models (2.5/3+ with thinking features) generate responses, they include thoughtSignature blocks - opaque encrypted tokens used for reasoning continuity.

Proposed Solution:

1. Update src/integrations/misc/export-markdown.ts:

   • Add a ThoughtSignatureBlock interface to the extended types
   • Add a case for thoughtSignature in the formatContentBlockToMarkdown switch statement that returns an empty string (since thought signatures are opaque tokens not relevant for human-readable exports)

2. Add tests in src/integrations/misc/__tests__/export-markdown.spec.ts:

   • Test that thoughtSignature blocks are silently skipped
   • Add coverage for the existing content block types

This approach will:

• Silently skip thought signature blocks during export (no error message)
• Match the behavior of other internal blocks that are filtered during API communication
• Not affect the actual markdown output with any placeholder text

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[rossdonald]

I still see this error in v3.39.1. Is it fixed in the released version?