For me, the Copilot has been creating .TSX files lately in it’s responses. It hasn’t done that for me in the past. The TSX looks ok, but my subscribers cant really do anything with that format outside of the browser.
Is this a new feature? Anyone else seeing this?
Hi @dougfresh ,
Thank you for reaching out!
What you’re seeing usually comes down to the output format the Copilot is choosing.
- If the Copilot generates a React component, the download option will just be TSX.
- If it generates Markdown, you should see Markdown, TXT, PDF, and DOCX.
- If it generates HTML, you should see HTML and PDF.
So this is not necessarily a new feature or a bug by itself. It’s often prompt-driven. If the system prompt or builder instructions nudge the Copilot toward React or interactive UI output, it may choose a React/TSX artifact. If you want more document-style downloads, it helps to explicitly steer it toward Markdown or HTML instead, for example:
“Use Markdown for downloadable documents and only use React if I explicitly ask for an interactive component.”
If you’re open to it, could you please email us the agent link and a session ID where this happened?