Files
Last updated:
The Files screen manages your personal server-side workspace. You can browse folders, create text files, upload files, edit supported documents, download files, and delete workspace items.
Note
A workspace is a server-side folder area assigned to your account. Agents can use workspace material only when their tools and allowed paths permit it.
Browse folders
Use Home and the breadcrumb trail to move through folders. Folders appear before files, and entries are sorted by name.
Recognized Oscova-managed folders show a short purpose description beneath the breadcrumb. This includes agent definitions and data, workspaces, settings, prompts, skills, tasks, memory, conversations, logs, metrics, audit records, notifications, and tool usage state. The description also appears in stable managed subfolders such as agent notes, daily memory, task runs, and chat attachments. Ordinary user-created subfolders do not show a system description.
Some top-level folders are protected from deletion, but their contents can still be managed when allowed.
Create folders and files
Click New Folder to create a folder in the current location.
Click New File to create a blank editable file. New files must use one of these extensions:
.md.txt.json.yaml.yml.csv.xml.enc
Names must be valid file names. Attempts to use path traversal or unsafe names are rejected.
Upload files
Click Upload and choose one or more files. The UI accepts up to 10 files at a time. Each uploaded file must be 10 MB or smaller.
Uploads overwrite an existing file with the same name in the current folder. For reference material you expect agents to read directly, prefer text formats over large binary files.
For semantic discovery across reference documents, put supported files in the managed library workspace. Oscova indexes that folder separately so an authorized agent can use Library Search even when you do not remember a file name or exact wording. Manage Library files on this screen because agents receive read-only access and direct disk changes do not trigger indexing.
Grant an agent access
The Files screen manages the content. The agent editor controls which folders an agent can use.
- Under Workspace Folders, select each managed workspace the agent may access. Changes are not saved automatically.
- Selecting Library grants read-only access to its source files and adds the Library Search tools.
- Under Additional Folder Access, choose External for an existing host folder or Managed for a path inside your user data.
- Give each additional folder a unique Label, then choose Read Only or Read & Write.
- In sandbox mode, additional folders appear to the agent under
/mnt/<label>.
Click Save in the agent editor. Labels that resolve to the same mount name block saving until you make them unique.
Edit text files
Click an editable file name or its edit icon to open the built-in editor. The editor supports the same text extensions used by New File.
Editable file content is limited to 512 KB. Larger files can still be downloaded, but they cannot be opened or saved in the browser editor.
Markdown files enable variable highlighting in the editor. Other supported formats open as plain text/code.
Encrypted text files keep their original extension followed by .enc, such as notes.md.enc. After you pass the Vault Password gate, Files opens a valid encrypted payload as plaintext in the same editor and encrypts it again when you save. If the file does not contain a valid authenticated encrypted payload, the editor shows and saves its stored text unchanged.
Downloading an encrypted file returns its ciphertext rather than the plaintext shown in the editor.
When backup history exists for a standard workspace file, the editor shows History with the number of saved revisions. Use history to compare or restore earlier text before overwriting an important prompt, skill resource, or workspace note.
Each editable file can keep up to 30 restore points. Oscova skips duplicate restore points when the latest saved version already matches the current file, and restoring an older version first tries to snapshot the current file.
History is not shown for oversized files, unsupported extensions, directories, missing files, or the internal file-history folder itself.
Saving runtime prompt files such as compaction, memory, environment, tool-search, and task-list prompts invalidates cached agents so later runs use the updated prompt content. A response already in progress keeps the prompt it started with.
Download and delete
Use the download icon to save a file copy to your computer.
Use the delete icon to remove a file or folder after confirmation. Deleting a folder removes all contents. There is no recycle bin in the Files screen.
Important
Export a backup before deleting large folders or reorganizing important reference material.
If an agent cannot see a file
- Confirm the file is in the workspace or an external directory assigned to that agent.
- Confirm the agent has a tool that can read files.
- Confirm the agent's allowed paths include the file location.
- If you just changed a grant, confirm you clicked Save in the agent editor.
- Confirm the file type and size are practical for the intended tool.
- Manage Library files through this screen. Watch My Files does not trigger Library indexing.
Direct file access and Library Search solve different problems. Use a file or PDF tool when the prompt names a specific file. Use Library Search to discover relevant passages across indexed Library files.
Security behavior
The file API keeps operations inside your user directory and rejects paths that escape through traversal or symlinked segments.
Note
A symlink is a filesystem shortcut that points somewhere else. Oscova rejects symlink escape paths so a workspace action cannot silently reach outside your user area.
Uploads are staged through a temporary sibling file and promoted only after the size check succeeds. If an upload fails or exceeds the 10 MB limit, it should not truncate the existing file with the same name.