Before submitting
Area
apps/desktop
Problem or use case
When working in T3 Code, I sometimes copy a large block of text like logs, transcripts, generated code, or config snippets and want to attach it as a file instead of pasting it directly into the prompt box.
Google AI Studio has a very convenient version of this idea: when you paste a large chunk of text, it gets turned into a file automatically. That keeps the input clean and makes large pasted content easier to manage.
For T3 Code, I would like a similar workflow, but not as an automatic default. A normal paste should stay unchanged. The problem is that today there is no quick way to turn clipboard text into a file attachment inside the app, especially in a project-scoped workflow.
Proposed solution
Add a dedicated shortcut, for example Cmd+Option+V, that pastes the current clipboard text as a file attachment instead of inserting it into the input.
Suggested behavior:
- Read plain text from the clipboard
- Create a text file automatically
- Attach that file to the current chat or working context
- Keep normal paste behavior unchanged
Storage should be configurable. The generated file could be created in either:
- a dedicated global T3 Code folder, or
- a project-specific folder for the currently active project
This could be exposed as a setting so users can choose the destination that fits their workflow.
A sensible first version could use an automatic filename and attach the file immediately without extra prompts.
Why this matters
This would help users who work with long-form text inputs and project artifacts instead of short chat-style prompts.
It would make T3 Code better for logs, transcripts, specs, generated code, stack traces, and other large pasted content. It also creates a cleaner separation between prompt text and file-based context, which is especially useful in desktop IDE-style workflows.
Smallest useful scope
The narrowest useful version would be:
- add a keyboard shortcut such as
Cmd+Option+V
- convert clipboard text into a temporary
.md file
- attach that file to the current conversation
- let the app store it in one configurable location
It does not need automatic detection, custom naming, or a confirmation dialog in the first iteration.
Alternatives considered
Alternatives considered:
- automatic conversion of large pasted text into a file, similar to Google AI Studio
- manually creating a file outside the app and then attaching it
- pasting the content directly into the input field
I think the shortcut-based approach is better for T3 Code because it preserves normal paste behavior and makes the feature intentional.
Risks or tradeoffs
A few tradeoffs to consider:
- choosing a good default filename and extension
- deciding whether the file should be temporary or persist in project state
- handling very large clipboard contents safely
- making the storage location understandable to users
The main UX risk is hidden file creation, so the destination and behavior should be explicit in settings.
Examples or references
Comparable behavior exists in Google AI Studio, where large pasted text can be treated as a file instead of inline prompt content.
This request is specifically for T3 Code as a desktop-app style workflow, where project context and file attachments are a natural fit.
Contribution
Before submitting
Area
apps/desktop
Problem or use case
When working in T3 Code, I sometimes copy a large block of text like logs, transcripts, generated code, or config snippets and want to attach it as a file instead of pasting it directly into the prompt box.
Google AI Studio has a very convenient version of this idea: when you paste a large chunk of text, it gets turned into a file automatically. That keeps the input clean and makes large pasted content easier to manage.
For T3 Code, I would like a similar workflow, but not as an automatic default. A normal paste should stay unchanged. The problem is that today there is no quick way to turn clipboard text into a file attachment inside the app, especially in a project-scoped workflow.
Proposed solution
Add a dedicated shortcut, for example
Cmd+Option+V, that pastes the current clipboard text as a file attachment instead of inserting it into the input.Suggested behavior:
Storage should be configurable. The generated file could be created in either:
This could be exposed as a setting so users can choose the destination that fits their workflow.
A sensible first version could use an automatic filename and attach the file immediately without extra prompts.
Why this matters
This would help users who work with long-form text inputs and project artifacts instead of short chat-style prompts.
It would make T3 Code better for logs, transcripts, specs, generated code, stack traces, and other large pasted content. It also creates a cleaner separation between prompt text and file-based context, which is especially useful in desktop IDE-style workflows.
Smallest useful scope
The narrowest useful version would be:
Cmd+Option+V.mdfileIt does not need automatic detection, custom naming, or a confirmation dialog in the first iteration.
Alternatives considered
Alternatives considered:
I think the shortcut-based approach is better for T3 Code because it preserves normal paste behavior and makes the feature intentional.
Risks or tradeoffs
A few tradeoffs to consider:
The main UX risk is hidden file creation, so the destination and behavior should be explicit in settings.
Examples or references
Comparable behavior exists in Google AI Studio, where large pasted text can be treated as a file instead of inline prompt content.
This request is specifically for T3 Code as a desktop-app style workflow, where project context and file attachments are a natural fit.
Contribution