Integrations & Autonomous Channels
Helix becomes far more useful when specialists can collaborate where your engineering work already lives.
1. GitHub App & Repository Permissions
Connect GitHub under Workspace Settings -> Integrations (/helix/connections):
- Install the LaunchVerse / Helix GitHub App on your personal account or GitHub Organization.
- Select either all repositories or explicit repositories (recommended for strict least privilege).
- Important permission note for Organization Repo Creation:
- Standard read/write repo cloning, branch commits, and PR creation work out of the box with
Contents: Read & WriteandPull Requests: Read & Write. - If you want specialists to create new repositories automatically inside a GitHub Organization, grant
Administration: Writeon the App installation. (GitHub APIs never allow installation tokens to create repos under personal user accounts — in that case, create the empty repo first and ask Helix to push to it.)
- Standard read/write repo cloning, branch commits, and PR creation work out of the box with
2. Agent Mail (@launchverse.app)
Every workspace member and specialist can receive and send structured email workflows via @launchverse.app handles:
- Claim your personal routing handle under Profile & Mail (
/helix/profile). - Configure inbound rules (e.g., vendor status emails, CI failure digests, or executive summaries).
- Outbound emails to external recipients automatically pass through a
T2Approval Gate unless explicitly whitelisted by a team Owner.
3. Recurring Schedules (Cron Automation)
Set up recurring missions under Schedules (/helix/schedules):
- Choose standard cron expressions (
0 8 * * 1-5for weekday morning audits) paired with your exact IANA timezone (e.g.,UTC,Europe/London,America/New_York,Asia/Tokyo). - Attach the exact goal prompt and autonomy ceiling (
supervisedby default so PRs wait for review before merging).
Great recurring schedule ideas:
- Daily morning dependency & security CVE triage
- Weekly schema drift & migration dry-run verification
- Pre-release end-to-end Playwright visual smoke sweep
4. Team Rooms & Multi-Agent Collaboration
Use Team Rooms (/helix/community) when humans and multiple specialists work together in a shared persistent channel. Tag specific specialists (@engineer, @cloud, @analyst) inside the same thread — their handoffs and sub-runs preserve full context across messages without overwriting each other.
Next Steps
- Automate pipelines via Webhooks & Events
- Build custom internal tooling in MCP Providers

