[Feature]: Any non-image file attachment support

[Dan503]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/web

Problem or use case

I want to be able to just drag and drop my log.txt file into the chat to attach it to the chat instead of having to copy/paste the path and type the file name every time I want the AI to know where to look for the log file.

Proposed solution

I would be fine with you just duplicating the Claude Code implementation or even just adding the file path as plain text to the chat so the AI knows where to look for the file.

This is how the Claude Code interface handles it:

This method of referencing the file can be done for any file type. Basically if it isn't an image, then just integrate a file-path reference to the file.

Why this matters

Much faster to drag and drop than paste the file path from windows explorer and type the word "log.txt".

The log file changes frequently so I need to get the AI to reference the log file each time I start a new chat.

Smallest useful scope

Drag and drop the file into the text input area and it adds the file path to the chat as plain text. That would be enough.

Alternatives considered

I work around it by copy/pasting the path from windows explorer then I manually type \log.txt

Risks or tradeoffs

No response

Examples or references

No response

Contribution

• I would be open to helping implement this.

[ViliusZur]

I would like this feature as well. This would help when debugging log. Also, CSV support would be greatly appreciated as well.

[Jardo-51]

Would be great if this covered directories too, not just files. Dropping a folder from the file explorer should insert its path/URI into the composer the same way a file does.

Right now dropping a directory hits the same code path as any non-image file in apps/web/src/components/chat/ChatComposer.tsx (onComposerDrop → addComposerImages), which rejects anything without an image/ MIME type with "Please attach image files only." A dropped directory has an empty type, so it triggers that misleading error. The fix for non-image files should handle the directory case in the same pass.

[Teejay-first]

Baffled this has still not been done. For it's creator not having a very stance towards other dev tools, it surely is surprising that even the most basic implementation of just dropping external files and have it paste the file path, has not been yet implemented.

I just tried t3code again after months not touching for smaller naunce things like this, and Im leaving again.

please just dial in these UX aspects!

[tetranow]

.docx as well please as I use it for feature implementation status tracking, clunky, but works my way!

[jlrochin]

One additional concrete use case: T3 Code currently rejects Excel files (.xlsx) when attempting to attach them to a chat.

Steps to reproduce:

1. Attempt to attach an .xlsx file from the composer.
2. T3 Code displays: Unsupported file type for '<file>.xlsx'. Please attach image files only.

Expected behavior: the workbook can be attached for the agent to inspect, or at minimum added as a reference to a file accessible from the workspace, as proposed in this issue.

This blocks workflows where the source material is a spreadsheet and forces users to find a workaround outside the composer.

[DmitriyAlergant]

+1 here

Tried attaching via drag&drop. Desktop app. Seeing "Unsupported file type for '2026-08-12-005001-prod.txt'. Please attach image files only." is unexpected for a txt file.

No fancy context extraction needed.

[isaachorowitz]

This should be treated as a major attachment-system flaw, not just a convenience enhancement.

The current composer accepts only files whose browser MIME type starts with image/. PDFs (application/pdf), logs, source files, Markdown, CSVs, Word documents, and other ordinary files are rejected before they can reach the agent. The server contract and normalization path independently model and validate attachments as images only, so this is a system-wide limitation rather than a missing button.

This affects a broad and very common agent workflow: users regularly need to hand an agent a PDF specification, build log, crash report, exported data file, screenshot-adjacent document, or source/config file that is not already inside the connected workspace. Today they must copy/paste contents, manually type a path, or move the file into the workspace first. That is especially painful for remote clients, where the file may exist only on the user's local machine.

The impact is also inconsistent and confusing: some image types work, while other images can fail later because of browser decoding or provider MIME restrictions; PDFs appear to be silently outside the supported model entirely.

A durable fix should establish a provider-neutral generic attachment/file contract, persist the upload safely, and then let each provider either:

• consume the file natively;
• receive a filesystem/path reference when it can access the workspace; or
• receive a clear unsupported-type error instead of silently dropping it.

A sensible minimum would be drag-and-drop of local files with filename, MIME type, size, and a stable attachment reference, with PDFs and text-like files included. This issue should be prioritized because the current image-only assumption blocks a large category of normal coding-agent inputs. Related Android picker issue: #5006.

[genesis-gh-agorshkov]

This continues to be the main bottleneck for wider adoption across the team. Right now inability to attach files of various types prevents majority of our team's workflows. As previous commentators stated, attachments of any type that the underlying harnesses already support would be great to add support for?

[Jardo-51]

I found these workarounds that we can use while we wait for #5543 to merge:

1. Browser Window

• Select the file or directory in the explorer and press ctrl + c.
• Open a fresh browser window, click to the address bar and press ctrl + v. This inserts the file path into the address bar.
• Press ctrl + a and then ctrl + c to select and copy the file path.
• Go to T3 code and paste the file path into composer.

2. Clipboard App

I recently vibe-coded a clipboard monitoring app in Rust (shameless plug). You have to build it and run it yourself. But other clipboard tools may work as well.

• Select the file or directory in the explorer and press ctrl + c.
• In T3 composer, press ctrl + shift + c which opens the clipboard tool window. Press enter to paste the path.

[bdlowery]

Still can't upload folders into the chat