Files supply reference material that the operator can consult across relevant tasks. Use them for background that should remain available: product documentation, terminology, policies, research, or other material that helps it understand your work.
Files are supplemental context. The File system holds editable work, while Sources supply inputs to a particular conversation.
Prepare useful reference material
Choose focused, current documents with descriptive names. A product guide and a separate customer glossary are easier to identify than a single document mixing unrelated material. Explain important context in the document itself rather than relying on its filename alone.
- Open Files in the owning Workspace, Agent, or Project.
- Add the material you have permission to use.
- Review its filename, contents, and destination.
- Ask a representative question whose answer depends on that material.
- Check that the answer reflects the relevant evidence.
The operator can inspect an authorized catalog and read relevant contents. Availability does not mean every document is read for every task, or that every format can be interpreted completely.
Understand where Files apply
| Owner | Use |
|---|---|
| Agent | Background governed by the Agent's resource access and assignments |
| Project | Context specific to that Project's development |
| Workspace | Shared background available to eligible Chat and Project work |
A Chat consumes eligible Workspace context; it does not own a separate Files library. Inherited Files remain owned by their source. Edit or replace them at that owner rather than expecting a receiving resource to change the shared original.
Add Files from the Composer
Use /file in the slash command menu to open the supported creation, upload, or import workflow. Review the destination before saving. In Chat, managed background material belongs to the Workspace rather than a separate Chat library.
The file upload dialog supports browsing files, uploading a folder, and dropping files into its upload area. It accepts common text and code documents, PDF, Word, spreadsheets, and presentations, with a limit of 20 MB per file. Review the selected paths before confirming.
Dropping a file directly onto the message Composer follows the attachment flow instead. That supplies a conversation Source; it does not silently add a configuration File.
Choose the right home
| Material | Destination | Purpose |
|---|---|---|
| Customer records used by an application | Its authorized database or storage | They belong to the application's data lifecycle |
| Interview transcript for today's synthesis | Conversation Sources | It is input to a specific task |
| Product glossary used across recurring work | Configuration Files | It provides lasting background |
| Report you are actively revising | File system | It is editable working content |
| Steps for reviewing that report | Skills | It describes a method |
Example: a product knowledge library
Start with a few focused documents: a product overview, a glossary, and a guide to your customers. Include the document's purpose, relevant date, and any limits on its claims. Separate current behavior from future plans so the Operator has enough context to describe each accurately.
Then ask a question that requires the material:
Using the Product overview File, explain how our service helps a new account administrator. Identify the source of the key claims and flag anything the document does not establish.
Select the intended File through the mention picker, especially when several resources have similar names. Review whether the answer uses the relevant evidence rather than assuming that availability proves the document was read.
Organize the library
Use descriptive relative paths such as product/overview.md and customers/glossary.md when organizing a collection. Files with the same path in different owners remain separate resources. A Project-local file does not replace a Workspace file simply because their names match.
Keep task-specific historical evidence in the conversation that used it. Name current library documents clearly so readers do not have to guess which version applies.
Keep material current
Replace a document at its owning scope when its reference content changes. New material and replacements affect future work without rewriting the evidence behind past results.
If an answer appears stale, check the active scope, the current file, and whether the task used the relevant contents. For an exact task input, attach the needed version as a Source. For an independent editable copy, use the File system.
Do not store credentials in Files. A document can describe a system, but it cannot grant access to that system, select a Design, or enable a Skill or tool.