Files
Files
Each String has a shared file drop where you can upload documents that become part of the conversation context. Files are stored alongside the conversation and automatically included when the character generates responses.
How It Works
When you upload a file to a String:
- The file is stored as part of the conversation (not on the filesystem — stored securely in the database)
- File content is injected into the character's context as a "Shared Files" section
- The character can reference and discuss the file contents in its responses
This means your character has access to the documents you share — similar to the Knowledge Base, but scoped to a specific conversation rather than a specific character.
Uploading Files
The file panel is in the bottom half of the sidebar (visible when a conversation is open).
- Drag and drop files directly onto the panel
- Or click to open a file browser
[Screenshot: File panel in sidebar showing uploaded files and drag-and-drop zone]
Limits
- Maximum file size: 10 MB per file
- Maximum files per String: 50
- Duplicate filenames: Handled automatically by the server
Supported Content
Text-based files work best since their content is injected into the LLM's context. The character can read and discuss the contents of uploaded text files, code files, configuration files, and similar text-based documents.
Managing Files
The file panel shows all uploaded files for the current conversation:
- Preview — click a file to view its contents
- Delete — remove a file (soft-delete, can be recovered if needed)
Files are conversation-scoped. Each String has its own file collection, independent of other conversations and character knowledge bases.
How Files Appear in Context
When the character generates a response, uploaded files are included in a dedicated section of the prompt between the Knowledge Base results and Memory context:
[Character identity and personality]
[System prompts]
[Knowledge base results]
[Shared Files] ← your uploaded files
[Memory context]
[Tool descriptions]
The system caps the total file content included to keep context manageable. If you have many large files, the most relevant portions are included.
If the file storage service is temporarily unavailable, the character still responds — just without file context. This is consistent with the fail-open design throughout QUI.
Files vs Knowledge Base
| Feature | Shared Files | Knowledge Base |
|---|---|---|
| Scope | Per conversation (String) | Per character |
| Access | Only in the conversation where uploaded | In every conversation with that character |
| Best for | Project-specific documents, code review files, meeting notes | Permanent reference material, domain knowledge |
| Upload via | Strings sidebar file panel | Visual Builder → Knowledge node |
Use shared files for temporary, conversation-specific documents. Use the Knowledge Base for persistent reference material that should inform the character across all conversations.
