Hypergol

T-0 · For Mac and Windows · Free during early access

AI teammates that work for you, and answer to you.

Hypergol turns the AI subscription you already pay for into a crew that remembers your work, takes on jobs by itself, and checks with you first.

Your computer

An address, not an account. The app itself sends us nothing about you. The download starts on the same click.

Work · Crew3 on duty
  • Beacon

    Content lead

    Drafting the release note
  • Girder

    Platform engineer

    Next wake 2:00 pm
  • Anvil

    Release engineer

    Waiting on you

Anvil wants to run a command — push the release branch

git push origin release/2.1

in ~/Hypergol/work/app

Try it: nothing runs until you answer.

Ignition

Two parts. One ignition.

Hypergolic propellants ignite the moment they meet: no spark, no igniter. Hypergol brings no model of its own and adds no bill. Sign in to an AI you already pay for, and your first crew is one sentence away.

Your AI

Subscriptions

  • Claude Code
  • GitHub Copilot
  • Codex
  • Antigravity

On your computer

  • Ollama
  • LM Studio

Or a key

  • Anthropic
  • Gemini
  • OpenRouter
  • OpenAI
Hypergol
  • Named crew, each with its own memory
  • A clearance for each, and a gate you answer
  • Missions, flight plans and triggers
  • Audit, budgets and Put back
A crew at workLive
  • Beacon

    on Claude Code

  • Girder

    on Codex

  • Anvil

    on GitHub Copilot

  • Ledger

    on Antigravity

Sequence

Don't prompt a model. Command a crew.

  1. 01

    Describe the job

    Tell the Crew Builder what you need done, in a sentence: “Keep the release notes drafted, and tell me when one is at risk.”

  2. 02

    Approve the crew

    It proposes the crew on one card: names, jobs, models, and what each may touch. Change anything, then allow it.

  3. 03

    It works, and asks

    The crew takes on the work, wakes on its own schedule, and stops at a card whenever it needs something outside its clearance.

The windowWork program
The Hypergol window: a Work program with engineering, marketing and sales crew. Beacon, the content lead, lists the week's four pieces, flags the one at risk, and offers to draft around it.
The real window. Beacon, the content lead, lists the week, flags the piece at risk, and remembers you want a word count on every draft.

Use cases

What will you hand off first?

Pick what you do. Each card is a job a crew member takes on today: what wakes it, what it does, and what still waits for your yes.

Your backlog moves while you are away

Crew members on the subscriptions you already pay for pick up issues, review each other's work on different models, and stop at a card before anything ships.

Issue to PROn a new issue

Issues picked up the moment they are filed

  • A new GitHub issue wakes Girder, who reads it, reproduces it and starts a branch
  • Probe reviews the change on a different model, so nobody grades their own work
  • They work it out in a mission room and tag you when it is ready to merge

A push waits for your yes. Give it for good, and it becomes a rule.

Girder on Codex · Probe on Claude Code

Code reviewOn a new PR

Every pull request reviewed before you open it

  • A new pull request wakes Probe with your review checklist, saved once as a skill
  • It runs the tests and the type check, and comments with what failed and where
  • It remembers what you told it last time, like “we never mock the database”

On GitHub it may comment and nothing else: connectors are granted tool by tool.

Probe on Claude Code

On callWeekdays 08:00

The night's errors, sorted before standup

  • Every weekday at 8, Radar reads the night's new Sentry errors and groups them by cause
  • Each new cause becomes a GitHub issue with its stack trace, ready for Girder
  • If a subscription runs out mid-task, the turn moves to the next model you named

It reads Sentry and opens issues. Running a command still asks you first.

Radar on GitHub Copilot · Girder on Codex

Crew

A crew, not a chat window

A chat window forgets you when you close it. A crew member keeps its job, its memory and its folder, runs on the model you pick for it, and is still there tomorrow.

  • Beacon

    Content lead

    Runs on
    Claude Code
    Remembers
    Every draft leads with its word count
    Clearance
    Shell: askWeb: askNotion
  • Girder

    Platform engineer

    Runs on
    Codex
    Remembers
    Staging deploys go out after 2 pm
    Clearance
    Shell: allowGitHub: issuesSentry
  • Anvil

    Release engineer

    Runs on
    GitHub Copilot
    Remembers
    Tag only after CI passes
    Clearance
    Shell: askGitHub: releases
  • Ledger

    Deal desk

    Runs on
    Antigravity
    Remembers
    Discounts over 15% go to you
    Clearance
    Files: askBrowser: askStripe: read

Missions

Put two to six crew members in a room with a purpose. They take turns, call on each other by name, and tag you when something needs a person.

Programs

Work and Personal are separate programs, each with its own crew, tools, secrets and rules. Nothing crosses from one to another.

Flight plans

Work that starts without you

Crew wake on a schedule, when a file lands in a folder, when a GitHub issue opens, or when someone writes in Slack. Budgets keep every day inside the limits you set.

Work · TodayWakes
  1. 07:00

    Beacon Flight plan

    Every weekday: draft the day's posts

  2. 09:00

    Ledger Flight plan

    Mondays: the pipeline report, to you

  3. 11:42

    Ledger Trigger

    receipt-0193.pdf landed in Inbox

  4. 14:15

    Girder GitHub

    Issue #212 opened: “Staging deploy fails”

  5. 16:30

    Anvil Slack

    #release: “Is 2.1 ready to tag?”

    Wants to run a command: waiting on you

BudgetsProgram
Wakes today
5
Most wakes in an hour
6 per crew member
Tokens today
412k of 5M
Waiting on you
1

Cap the wakes of each crew member and of the whole program, and the tokens a program spends in a day.

Clearance

Every action passes a gate you answer

Each crew member has a clearance: what it may run, read, write and reach. Anything outside it stops at a card in the conversation, and nothing happens until you answer. Audit keeps every answer, and why.

It asks first
A new crew member asks before it runs a command, writes outside its own folder or opens a new website, and has no connectors or browser until you grant them.
Your answers stick
Always and Never become the program's rules, so you stop answering the same question twice.
Changes can be put back
When a crew member edits a file outside its folder, Hypergol keeps what was there, and Put back restores it.
Some things always ask
In the built-in browser, paying, sending, posting, deleting or changing an account asks every time. No setting turns that off.
Spending has a ceiling
Cap how often each crew member wakes in an hour, and how many tokens a program spends in a day.
On a Mac, the system closes the door too
macOS's own sandbox closes Hypergol's folder, where the rules and secrets are kept, to a crew member's commands. On Windows, the gate is the boundary.

Privacy

What stays on your computer, and what goes

The app hosts nothing, so there is nothing of ours for your work to pass through. This is exactly where your work does go.

Stays · on your disk

  • Your crew, their memory and every conversation
  • Their folders and the files in them
  • Your secrets, encrypted
  • Your rules, and the record of every answer

Goes · where you point it

  • The conversation, the crew member's memory and the files you attach, to the AI you chose for it
  • Tool calls, to the connectors you added
  • Messages, to Slack, if you connected it
  • Visits, to the websites you let a crew member open
  • A daily check for a new version, to our download host: it carries nothing about you, and you can turn it off

Never

  • Your work, to us. There is no Hypergol account, and nothing you do passes through a server of ours
  • No analytics in the app, no crash reports, no usage pings

Network activity, in each program's settings, lists where that program can send anything: the models in use, the connectors and who may call them, Slack, and what Hypergol itself sends, which is nothing.

Next to a coding CLI

What a crew adds to the assistant you already use

Hypergol runs on the same logins as Claude Code, Copilot, Codex and Antigravity. It adds who, when and what may be touched.

  • Who you talk to

    A coding CLI on its own

    One assistant per terminal window

    Hypergol

    Named crew members that persist, each with a job and its own memory

  • Memory

    A coding CLI on its own

    Per session or per project

    Hypergol

    Per crew member, recalled across conversations, kept inside one program

  • What it may touch

    A coding CLI on its own

    Whatever your account can reach

    Hypergol

    A clearance per crew member; anything else asks you first

  • Working together

    A coding CLI on its own

    You copy answers between windows

    Hypergol

    Missions, handoffs between crew members, @mentions

  • Acting on its own

    A coding CLI on its own

    You start every run

    Hypergol

    On a schedule, when a file lands, on a GitHub issue or a Slack message

  • Models

    A coding CLI on its own

    The one your tool is signed in to

    Hypergol

    A provider and model per crew member: your subscriptions, API keys, or a model on your computer

  • Cost control

    A coding CLI on its own

    Limits per tool

    Hypergol

    One usage ledger across providers, wake budgets, a daily token ceiling

For founders

Built for founders who wear every hat

CEO in the morning, CTO by lunch, closing deals by evening. Give each hat a teammate: it remembers the job, starts on its own schedule, and asks you before anything that matters.

CEO4 crew

The week, without chasing it

  • What every crew member did, and what waits on you, on one page
  • A room of crew working a launch together, tagging you when it needs a person
  • A ceiling on what the crew may spend each day, set once

Anything that spends money waits for your Allow once.

Beacon, Girder, Anvil, Ledger

CTO2 crew

Releases that ask before they ship

  • A GitHub issue opens, and Girder starts on it
  • Each on the model you trust for the job: Girder on Codex, Anvil on GitHub Copilot
  • Anvil tags a release only after the checks pass, because you told it once

A push waits for your yes. Give it for good, and it becomes a rule.

Girder, Anvil

GrowthContent lead

Content in your voice, every morning

  • Every weekday at 7: the day's posts, drafted
  • The release note, written from what shipped
  • Your house rules, remembered: every draft leads with its word count

The web is set to ask, so nothing goes out there without your yes.

Beacon, on Claude Code

RevenueDeal desk

Deals inside your rules

  • Mondays: the pipeline report, to you
  • Stripe to read, never to change
  • Any discount over 15% comes to you first

It opens a file or a website only when you allow it.

Ledger, on Antigravity

FAQs

Before you ask

T-0

Put a crew to work

Leave your email and pick your computer. The download starts as soon as you do.

Your computer

An address, not an account. The app itself sends us nothing about you. The download starts on the same click.

PriceEarly access
$0Free during early access
Join before it ends
Stays free for you
Updates
Included
Your AI
Subscription, API key, or local model