Chat

Chat is the interactive way to work with an agent. You give it a task, watch it work, and steer it as it goes. It is the same agent runtime that workflows use - the same sandbox, the same integrations, the same database and MCP access.

Chat is where you figure out how a task should be done. Once it works, save the instructions as a workflow and put the agent on it permanently.

Files

Upload files to a chat and the agent finds them in its sandbox. The agent is told the path of each file you attach, so you can refer to them naturally. "Reconcile the CSV I just uploaded against the payments table."

Uploads belong to the chat. Deleting the chat deletes them.

Pinned resources

Pin a GitHub repository to a chat and the agent gets authenticated access to it - Helios injects a short-lived, repository-scoped token at the network layer, so the agent can clone and work in the repo without ever seeing a credential. Pinning also disambiguates: when you say "the repo", the agent knows which one.

See integration resources.

Forking

Fork a chat to branch off from where it is. The fork copies the full message history, so the new agent starts with everything the original was told. Use it to try a different approach without losing the path you were on.

Sharing a transcript

Share a chat to get a public link to its transcript.

• You choose the cutoff message. Everything up to and including it is visible; everything after it is withheld - so you can keep working in the chat without extending what you shared.
• The link exposes only the chat's title and those messages. It does not expose your Library files, your integrations, or the agent's sandbox.
• Anyone with the link can read it. There is no sign-in check. Treat a share link as public.
• Unshare at any time to revoke the link.

Re-sharing an already-shared chat updates the cutoff, keeping the same link.

Chat and workflows

Both bill the same way - see pricing.