The manual.
Everything you need to run Hyperconsole, in 58 short guides.
Most read
- 01Start your first loopGetting started · 4 min
- 02Bring in a vibe-coded appProjects · 5 min
- 03Write your first policyPolicies · 6 min
- 04Choose an assurance levelLoops · 3 min
- 05Approve from your phoneApprovals · 3 min
- 06A loop keeps failingTroubleshooting · 4 min
Quick start.
From download to your first shipped pull request in about fifteen minutes.
Contents.
Getting started
- What is Hyperconsole?
- Install the app
- Connect your first model
- Start your first loop
- Invite your team
Projects
- Create a project
- Import an existing repository
- Bring in a vibe-coded app
- Project settings
- Archive a project
Loops
- How a loop works
- Write a good request
- Choose an assurance level
- Set a pass limit
- Stop or pause a loop
The crew
- Roles at a glance
- Choose a model per role
- Restrict a role
- Hand work between roles
- Run roles in parallel
Policies
- Write your first policy
- Package allowlists
- Network egress rules
- Protected paths
- Test policies in CI
Approvals
- Approval gates
- Code-owner sign-off
- Production deploy gate
- Approve from your phone
- Delegate approvals
Secrets
- Connect a vault
- How secret brokering works
- Redaction rules
- Rotate a leaked key
- Audit secret access
Runners
- Local sandboxes
- Cloud runners
- Install a runner in your VPC
- Air-gapped installs
- Runner health
Audit & compliance
- Replay a loop
- Export audit records
- Stream to your SIEM
- Evidence packs
- Retention settings
Previews
- Open the live preview
- How agents use the browser
- Share a preview link
- Preview environment variables
Schedules
- Put a loop on repeat
- Weekly vulnerability patching
- Nightly flaky-test sweeps
- Release-note loops
Troubleshooting
- A loop keeps failing
- A model won’t connect
- A policy blocked something it shouldn’t
- Runner is offline
- Contact support
Nothing matches that yet. Try another word, or ask us.