DEVUP Code
Add files and code to the chat
Decide which code goes with your message: attach files and selections, check the context gauge before sending, and learn which files stay out.
Attach from the + menu
Open the + menu and pick what to attach:
- the file you are editing;
- the code you have selected;
- your open editors;
- any file in the workspace;
- Upload from computer: an image, a PDF or a text file from anywhere on your computer, for models that accept that kind of file.

Selected code can also come in straight from the editor: press Ctrl+Alt+D.
Find a file with @
In the message box, type @ and part of a file name, then choose the file from the results to attach it.
The search leaves out files your project excludes, such as .gitignore entries. The .gitignore part follows devupai.context.searchFollowsGitignore.
If a file or folder name contains invisible characters, the + menu and the @ results, and the tooltip of a file attached above the message box, list which ones after its path, for example (U+202E), so you can tell that name from the same name written without them.
Chips and the context gauge
Each attachment sits above the message box as a chip, and one click removes it.
Before sending, glance at the small gauge for a rough idea of the share of the model's context this message would fill.
Long chats and large messages
When a chat gets long, DEVUP Code may leave the oldest messages out, and says so in a note under the reply.
If your message is more than the selected model can take, it isn't sent: you see the reason, and you can switch to another model.
What you can attach
- Text files, up to 100,000 characters each.
- Binary files added from the workspace with + or @ are refused, and so are links to other files.
- @ search covers the folders you have open.
- Uploads from your computer: Images are PNG, JPEG, WebP or GIF; PDF files go as PDF; Text files are any other file except SVG, when it is UTF-8.
- Files can also be pasted into the message box, or dropped on it with Shift held down.
Files that stay out
DEVUP Code never lists these in file search, can't attach them and never changes them: .env files, private keys, certificates, SSH and Git folders, and other files that may hold secrets.
To protect more files, add your own never-send patterns to devupai.context.neverSend. These patterns only add to the protection that is built in; none of it can be removed.
When one of your patterns holds an invisible character, a special space, or two spaces side by side inside it, DEVUP Code doesn't use it. The Never sent list leaves it out, though your settings still hold it as you wrote it. Write a single * in place of each group of those characters, and the pattern covers those files.
FAQ
How large can an attachment be?
Up to 100,000 characters per text file. With Upload from computer, you can also attach images and PDF files when the selected model accepts them.
Can I attach a .env file?
No. Files that may hold secrets, such as .env files and private keys, can't be attached and don't appear in file search.
Why doesn't a file show up in @ search?
Search covers your open folders and leaves out files your project excludes, including .gitignore entries. Files that may hold secrets never appear.
What does the context gauge show?
A rough estimate, shown before you send, of the share of the model's context the message will use.