Local Files

Upload files directly from your computer to give your agent access to documents that aren't stored in a cloud service.

How it works#

You upload files through the Runbear dashboard, and they are indexed for retrieval. The agent searches this content at query time to provide grounded answers.

Uploads accept the supported file formats — the file dialog filters to those types. The one exception on that list is .yaml, which can be synced from Google Drive but not uploaded directly.

No external account or authorization is needed.

CSV and Excel analysis#

Anthropic agents on standard (non-HIPAA) data handling can inspect a saved CSV or Excel original with code execution. This supports exact record lookups, counts, filters, and analysis across worksheets. The full file is still indexed for semantic search; search results help the agent find the relevant file before opening its original.

Original-file access uses the uploaded snapshot, not a live connection to the source. Previously indexed local files without a saved original must be uploaded again. Google Drive files acquire their saved originals during synchronization.

Hosted code execution accepts originals up to 500 MB and at most 16 files per run, including conversation attachments. A larger file can still be indexed within the existing upload limit, but cannot be opened for complete analysis. Original-file tools are unavailable in HIPAA mode, implicit-trigger runs, and Vertex fallback.

Setup#

1. Open your agent in the Runbear dashboard and go to the Knowledge tab.
2. Select Local Files.
3. Upload your files in the dialog that appears.
4. Click Save.

Limits#

Each file can be up to 512 MB; a larger file is not indexed. The same cap applies to files synced from Google Drive.

Managing files#

You can add new files or remove existing ones at any time from the same dialog. Changes take effect immediately after saving.