Attachments and context
Mail, files, images and PDFs go onto the composer and become context for the answer.
A screenshot beats a description
Panda reads images, so a picture of the broken layout is usually faster and more precise than three sentences about it.
Attach something
- Files and data. CSVs, configs, logs, anything Panda should read.
- Images. Screenshots, mockups, diagrams.
- Email. Drag one from the Gmail tab straight onto the composer.
Point at it with @
Typing @ names a thing instead of describing it: a file in the project, a connected app to bring into scope, an agent to hand the message to, or a skill to run. It is the difference between "the auth file" and the file.
Images in Panda's replies
Panda can show you a picture as well as read one. When it captures a screenshot to check its own work, or writes an image file, it can put that image straight into its reply, and it appears in the chat at full size. Click it to view it full screen, or hover it to download it.
If Panda says it cannot show you an image it has on disk, ask it to show the image in the chat. A path written in code stays a clickable link that opens the file, without the picture.
What Panda keeps in context
The quality of Panda's output is directly proportional to the quality of its input. A vague request produces a generic answer. A request with the right context - the specific file, the error screenshot, the design mockup - produces a precise one.
PandaOS gives you several ways to pull relevant context into a message so Panda works with the same information you have.
Mentions for precision
Type @ to reference a specific resource by name:
- Files - point Panda at an exact file in your project instead of describing where it is.
- Apps - bring a connected app (Gmail, Supabase, Vercel) into scope so Panda knows to use it.
- Agents - hand the message to a specialized agent.
- Skills - invoke a reusable workflow.
Mentions are the fastest way to be precise. Instead of saying "look at the authentication middleware," you can @-mention the exact file. Instead of saying "check my deployment status," you can @-mention your Vercel app. This eliminates ambiguity and saves Panda from searching for the right resource.