Library overview
The Library is the shared file store for your organization, its projects, and each person. Agents read it from their sandbox and propose changes that a person approves.
The Library is the shared file store in Helios. It holds the instructions, knowledge, and artifacts your agents work with. People and agents both read from it.
Agents never write to the Library directly. An agent edits files inside its own sandbox. Those edits become a proposed change. Nothing is shared until a person reviews the change and approves it. See proposing changes and reviewing changes.
Scopes
The Library has three scopes. Each scope is a separate tree of files.
| Scope | Who it is for | Where to browse it |
|---|---|---|
| Organization | Everyone in the organization. | Library in the sidebar, then Organization. |
| Project | The people who can reach one project. | Library inside the project. |
| Personal | Only you. | Library in the sidebar, then Personal. |
The Personal page has two trees. Your files holds your own files. Shared with you holds folders that other people shared with you. A shared folder appears under the name it was shared as. See permissions.
Each agent run also gets a scratch folder of its own. Files there belong to that run only.
Where agents see the files
When an agent starts, Helios mounts the Library folders the run may see under ~/context in the
sandbox.
~/context/organization the organization tree
~/context/project/<name> the tree for the run's project
~/context/user your personal tree
~/context/agent the run's own scratch folderThe agent reads these files straight from disk. It can cat a playbook, grep across a folder, or
copy a template. It does not need a tool call to reach them.
Each mounted folder is read-only or read-write for that run, based on the access of the person or service account the run belongs to.
The Library replaces the per-chat ~/workspace mount. Anything an agent should keep between runs
belongs in the Library and goes through review.
What agents can read and write
Read. Every file inside the run's scope. Files outside the scope do not exist as far as the agent is concerned.
Write. The agent can create, edit, and delete files under ~/context. Helios captures those
edits and stages them as a change. The live Library does not move until a person approves the
change. Edits inside a read-only folder can never be approved.
Browsing in the app
Every Library page shows a file tree and a preview pane.
- Markdown files render as formatted text.
- Other text files show as code.
- Binary files show no preview.
- Files above the inline preview size show a truncated notice. See limits.
- Files you cannot write carry a Read-only badge.
Press h then l to jump to the Library from anywhere in the app. The command palette also has
entries for the Organization, Personal, and Changes pages.
Next
- Proposing changes - how an agent's edits become a change.
- Reviewing changes - approve or discard each file.
- Permissions - who can read, write, and approve.
- Files panel - watch an agent's files while it works in chat.
Last updated on
MCP servers
Connect any remote MCP server so Helios agents can call its tools, and expose Helios itself over MCP to your own agents.
Proposing changes
Agents edit Library files inside their sandbox. Helios captures the edits after a short quiet period and stages them as a change. Nothing is live until a person approves it.