Context

Every run starts in a fresh sandbox. This page lists what carries over from one run to the next and what does not.

What persists

Library files. The Library is the shared file store for your organization, its projects, and each person. Helios mounts the folders a run may see under ~/context in the sandbox. Playbooks, templates, and reference files live there, and every run reads the same copy.

Approved changes. An agent can edit files under ~/context. Those edits become a proposed change. A person reviews the diff and approves or discards each file. Only approved files reach the Library, so a later run sees them. See proposing changes and reviewing changes.

Pinned resources. A repository or other integration resource pinned to a chat or a workflow stays pinned for every run.

Chat history. A chat keeps its own message history. Forking a chat copies that history into a new chat. Workflows do not see chat history.

API memory. When an agent works out how to complete a task against an integration's API, Helios records the procedure. The next agent that takes a similar task against the same integration starts from that record. This memory is scoped to your organization and the integration. It stores only the shape of the API calls. The contents of your records are never stored. It is managed by Helios and cannot be viewed or edited. Instructions in the prompt always take precedence.

What does not persist

The sandbox filesystem. Anything an agent writes outside ~/context disappears when the run ends. That includes $TMPDIR, installed packages, and the agent's own scratch folder at ~/context/agent.

Unapproved edits. A proposed change that nobody approves never reaches the Library. The next run does not see it.