DEVUP Docs
Back to Dashboard

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.

Selected code can also come in straight from the editor: press Ctrl+Alt+D.

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 AI 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 and links are refused.
  • @ search covers the folders you have open.

Files that stay out

DEVUP AI 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.

FAQ

How large can an attachment be?

Up to 100,000 characters per file. Attachments must be text files.

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.