Helio installs on demand and launches into its own agent context. You never sign in again - it reuses one of your existing logins.
Install and launch
enigma pack install helio
Fetch the pack (the @enigmax/helio asset package) into ~/.enigma/packs/helio. list shows every pack and its install state. You can skip this - launching also fetches on demand.
enigma helio [account]
Launch a coding agent inside Helio’s isolated context, seeded with one of your logins. With no account it uses the pinned pack account, else your active profile’s account, else the tool’s active account. Defaults to Claude Code; target another agent with --tool.
enigma pack setup helio
Register Helio’s MCP servers (HackerOne, and a Burp client if you configure it). Kept out of the default launch because they need Python and the pack’s tooling. enigma pack update helio / enigma pack remove helio keep or delete the pack. See MCP and tooling.
You can also manage Helio from the dashboard’s Packs tab - install, update, remove, pick the seeding account, and copy the launch command.
Which account Helio uses
A pack runs under one of your configured logins, seeded into its isolated context so you do not log in again. You can point it at any account or profile - or a dedicated one for authorised security testing.
enigma pack use helio <account|->
Pin which login seeds Helio by default (- clears the pin). enigma helio <account> overrides it for a single launch. To keep security work under its own identity, create a login with enigma account add <name>, log in, then pin it.
This lets Helio run under a different identity than your everyday agent without touching your normal enigma claude setup. See Packs for how isolation, seeding and MCP work across every pack.