Attachments & Context
How to enrich Panda's understanding by bringing external files, references, and resources into the conversation.
Why context matters
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.
Attaching files and images
You can attach files directly to any message:
- Documents and data files - CSVs, configs, logs, or any file Panda should read and work with.
- Images - screenshots of bugs, design mockups, architecture diagrams, or UI references. Panda can see and reason about images, so attaching a screenshot of a broken layout is often faster than describing the problem.
- Emails - drag an email from the Gmail tab directly into the conversation to pull in its full content without copy-pasting.
Attachments travel with the message they are attached to. They become part of the conversation context and Panda can reference them in later messages.
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.