Changelog

What shipped in Helios

Dated product updates, newest first. Each entry links to the docs page that explains it.

RSS feedRead the docs →
  1. Library

    Library and change review

    Agents now work from a shared Library. Every file an agent edits is staged as a proposed change. A person reviews the diff and approves or discards each file.

    • Three scopes. Organization, project, and personal files, plus a scratch area per agent session.
    • Files are mounted in the sandbox at ~/context.
    • Side-by-side diffs with Added, Modified, and Deleted labels. Approve per file or approve all.
    • Conflict detection. Approval is blocked when the live file changed after staging.
    • Agents cannot approve their own changes.
    • Share any folder with viewer or editor access.
    • A Files panel in chat shows what the running agent can see and has changed.
    • Uploading files from the browser is not available yet. Files enter the Library through agent sessions.
    Library docs →
  2. CLI

    CLI terminal app and helios configure

    Running helios opens a full-screen terminal app with chat, workflows, projects, access, and Helios Code. helios configure walks a new user from an API key to a running agent.

    • Home screen with a new chat input and recent chats. Command palette on ctrl+p.
    • Trigger a workflow with t, share it with s, and pick the service account it runs as.
    • helios configure saves progress and resumes. Rerun one step with --redo <step>.
    • Launch a Helios Code agent, watch the boot logs, then attach. A files tab shows the diff for each repository the agent edits.
    • helios integration connect and helios code iac scaffold, export, and apply work from scripts.
    • Every command prints JSON when piped.
    Install the CLI →
  3. Access

    Act as me for service accounts and credential mode on shares

    A named service account can act as you in integrations that need a personal login. When you share an integration, you choose whether the grantee connects with their own account or with the Helios app.

    • Act as me is a switch on the service account page. You can only point a service account at yourself.
    • Applies to GitHub and Slack, the two integrations that require a personal authorization.
    • The Share dialog for an integration has a Connects as picker. The default stays Their own account.
    • Change the mode later from the access list without sharing again.
    • Workflows that run as a service account no longer stop with authorization required on GitHub or Slack.
    Service accounts →
  4. CLI

    Sharing, groups, and service accounts from the CLI

    The helios command line has the same access controls as the dashboard. Pick a project, share any resource, and manage groups and service accounts from a shell or a script.

    • helios project use <id or name>, the HELIOS_PROJECT variable, or --project set the active project.
    • helios share <type>/<id> --with <principal> --role <role> with an optional --expires date. Principals are everyone, user, group, or service account.
    • helios access list shows your effective role and every grant, direct or inherited. helios shared list shows what was shared with you.
    • helios group and helios service-account commands for create, rename, disable, enable, delete, and member changes.
    • helios service-account assign makes a workflow run as that account.
    • Roles are viewer, operator, editor, and admin. You cannot grant above your own role.
    Roles and permissions →
  5. Integrations

    Gmail, Google Drive, Google Docs, and Google Sheets

    Four Google Workspace integrations. Agents get the full API of each one, with the Helios app or your own Google app.

    • Read and send mail, organize files, write documents, and update sheets from a chat or a workflow.
    • Connect with the Helios Google app or bring your own OAuth app.
    • Event triggers from Google are not available yet. Use a schedule.
    Integrations →
  6. Integrations

    Database connections

    Connect Postgres, MySQL, or ClickHouse and let agents query it directly.

    • Connection strings are encrypted with KMS and never enter the agent context.
    • Optional SSH tunnel for databases inside a private network.
    • Share a connection with a person, a group, or the whole organization.
    Databases →
  7. MCP

    Remote MCP servers

    Attach any remote HTTP MCP server and its tools appear in chats and workflows.

    • Bearer token or OAuth2 authentication.
    • Tool allowlist and timeouts per server.
    • Scope a server to the organization or to one project.
    • Helios itself is an MCP server. Call find_relevant_apis and call_api from your own client.
    MCP servers →
  8. Environments

    Environments built from a Dockerfile

    Build an environment from a Dockerfile, then run agents on it with a terminal and Git panel in the browser.

    • Overview, Versions, and Dockerfile tabs with build logs.
    • An environment bundles the image, secrets, cloud-init, integrations, and the coding agent.
    • Claude Code is pre-signed in the environment through the Claude Account integration.
    Sandboxes →
  9. Workflows

    Signed webhook triggers

    Start a workflow from any system that can send an HTTP request. Every request is signed with HMAC-SHA256.

    • A five minute replay window rejects old requests.
    • Rotate the signing secret without changing the URL.
    • The request body is available to the agent as the run payload.
    Triggers →

Try the latest release.

Start with 5,000 free credits.

Get started free
Book a demo