Skip to content

[FEATURE]: add option to Export thinking and tool use inputs/outputs #4609

Closed as not planned
Closed as not planned
[FEATURE]: add option to Export thinking and tool use inputs/outputs#4609
Labels
discussionUsed for feature requests, proposals, ideas, etc. Open discussion

Description

@Ninja3047
Ninja3047
opened on Nov 21, 2025

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Right now the export to markdown only exports the user and assistant messages and nothing about the reasoning or the tool use information. Only the tools used are exported but nothing about the details of what parameters were used or the output of the tools.

I know it could potentially make the markdown export very large so maybe having it as an option would suffice.

Activity

  1. Ninja3047
    added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Nov 21, 2025

  2. dan-kirberger commented on Nov 21, 2025

    @dan-kirberger
    dan-kirberger
    on Nov 21, 2025

    I figure it would make troubleshooting issues like this easier: #2464

    I'm curious what tool call causes my token count to instantly quadruple, the output i see in the ui looks simple enough!

  3. rekram1-node commented on Nov 24, 2025

    @rekram1-node
    rekram1-node
    on Nov 24, 2025
    Contributor

    @Ninja3047 have u tried opencode export? It is everything u need, just not in markdown

  4. Rom888 commented on Dec 20, 2025

    @Rom888
    Rom888
    on Dec 20, 2025

    I see this exported markdown with empty assistant and tool.
    Is this by design or a bug?

    # Debugging npx jest in.service.spec.ts failure

**Session ID:** ses_4d84ff224ffeYhLIVwlrNF5nxB
**Created:** 12/16/2025, 6:03:27 PM
**Updated:** 12/19/2025, 6:38:58 PM

---

## User

this test: npx jest in.service.spec.ts failed, try to understand why

---

## Assistant

'''
Tool: read
'''

---

## Assistant
'''

'''
Tool: read
'''

---

## Assistant

'''
Tool: bash
'''

---

  5. rekram1-node commented on Dec 21, 2025

    @rekram1-node
    rekram1-node
    on Dec 21, 2025
    Contributor

    i think its “by design” but could be improved for sure

  6. rektide commented on Dec 24, 2025

    @rektide
    rektide
    on Dec 24, 2025
    Contributor

    Opened #6089 because what we have now makes it basically impossible to reflect on what has happened in a session in any deep capacity.

    Longer term I hope that the plugin API can give us hooks to be able to capture & understand the session at a deep level, ideally shunt it into observability systems like MCP Semantic Conventions. But this is an advanced hope! 🚀

  7. thdxr commented on Mar 25, 2026

    @thdxr
    thdxr
    on Mar 25, 2026
    Member

    To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

  8. thdxr
    closed this as not plannedon Mar 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussionUsed for feature requests, proposals, ideas, etc. Open discussion

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions