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.
An address, not an account. The app itself sends us nothing about you. The download starts on the same click.
- Drafting the release note
Beacon
Content lead
- Next wake 2:00 pm
Girder
Platform engineer
- Waiting on you
Anvil
Release engineer
Anvil wants to run a command — push the release branch
git push origin release/2.1
in ~/Hypergol/work/app
Asks first
Outside its clearance, a crew member waits for you
Shows its work
Audit and Activity keep every answer and run
No middleman
No account, no telemetry, and your work never passes through us
Your AI
Your subscription, an API key, or a model on your computer
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.
Subscriptions
- Claude Code
- GitHub Copilot
- Codex
- Antigravity
On your computer
- Ollama
- LM Studio
Or a key
- Anthropic
- Gemini
- OpenRouter
- OpenAI
- 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
Beacon
on Claude Code
Girder
on Codex
Anvil
on GitHub Copilot
Ledger
on Antigravity
Sequence
Don't prompt a model. Command a crew.
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.”
02
Approve the crew
It proposes the crew on one card: names, jobs, models, and what each may touch. Change anything, then allow it.
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.

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.
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
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
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
Fewer status meetings, more decisions
A crew that reads what customers say, keeps the backlog in shape and writes the weekly update, and remembers what you decided and why.
Every feedback export, sorted into themes
- Drop a CSV of tickets or survey answers in a folder, and Compass sorts it into themes with counts
- Each theme comes with the customers' own words, quoted
- It keeps a running themes file, so it can tell you what is new since last month
It reads the folder you gave it. Anything else asks you first.
Compass on Claude Code
A groomed backlog every Monday
- Every Monday, it reads the week's new Linear or Jira issues and flags duplicates and gaps
- It drafts acceptance criteria for the issues that are ready
- Your past specs are in its library, so new ones follow the same shape, with the page cited
Changing an issue's status or owner is a tool you grant, or do not.
Compass on Claude Code
The weekly update, written from what happened
- Every Friday afternoon, Scribe reads the week's merged pull requests and closed issues
- It writes the stakeholder update and the release notes in your format
- Ask “why did we drop that?” and it finds the conversation where the crew decided it
It writes in its own folder. Editing your documents anywhere else asks first.
Scribe on GitHub Copilot
More time designing, less time checking
A crew that checks what was built against what you meant, keeps the design system honest, and does the legwork before you start.
Every build checked at every screen size
- A new pull request wakes Canvas, who opens the page and screenshots it at phone, tablet and desktop widths
- It checks contrast, focus order and tap targets, and saves the screenshots to your folder
- It comments on the pull request with what it found, and where
The first page from each site asks, until you allow that site for good.
Canvas on Claude Code
Drift caught before it ships
- Every Monday, it reads the codebase for colors, spacing and type that bypass your tokens
- Each one is listed with its file and line, and the token it should use
- Your component guidelines are in its library, so every note cites the rule it breaks
It reads the repository. Changing a file asks first, and Put back undoes it.
Canvas on Claude Code
Interview notes turned into patterns
- Drop interview notes in a folder, and Atlas pulls out the patterns, each with the quotes behind it
- Every week, it visits the products you name and notes what changed in their onboarding and pricing
- Everything lands in a research collection your crew can search and cite
The web asks site by site, so you see every new site it opens.
Atlas on Ollama
Content in your voice, without the blank page
A crew that drafts on a schedule, remembers your house style and reads the numbers, while posting in the browser always waits for you.
The day's posts, drafted before you are up
- Every weekday at 7, Beacon drafts the day's posts from your content calendar
- Your house rules are remembered: the words you never use, the length each channel wants
- Drafts land in Notion, ready for you to edit and schedule
Posting in the browser asks every time. No setting turns that off.
Beacon on Claude Code
Every release announced the same day
- A new GitHub release wakes Beacon, who reads what shipped
- It writes the blog post, the newsletter and the social thread from it
- Scribe checks every claim against the release notes before you read a word
Its web is set to ask, so it opens no new site without your yes.
Beacon on Claude Code · Scribe on GitHub Copilot
Last week's numbers, explained on Monday
- Every Monday, Vega reads your analytics in the built-in browser, signed in as you
- It measures speed and SEO on your top pages, and compares them with last week
- You get the three things worth doing this week, not another dashboard
In the browser, the first page from each site asks until you allow it for good.
Vega on Antigravity
Your store, minded while you sell
On Shopify, WooCommerce, Amazon, Etsy or your own site: a crew that reads your exports and dashboards, keeps listings and campaigns moving, and leaves the money to you.
Orders, returns and stock, summed up each morning
- Drop the day's orders export in a folder, from any platform, and Ledger sums up sales, returns and best sellers
- It flags the products running low before they sell out
- It compares the day with the same day last week, and points out what moved
It reads the folder you gave it. Anything in your store's admin asks first.
Ledger on Antigravity
Product pages and promos in your brand voice
- Drop a sheet of new products in a folder, and Beacon writes each title, description and search tags
- For every sale, it drafts the promo email, the social posts and the ad copy
- Your brand rules are remembered: the tone, the words you avoid, how you write prices
Posting in the browser asks every time. No setting turns that off.
Beacon on Claude Code
The store's plumbing, checked every morning
- Every morning, Vega checks that the purchases your analytics counted match your orders
- Every week, it measures speed on your top product pages and compares with last week
- On Shopify, theme changes are reviewed before they go live, and only you publish
Make publishing a theme a Never rule, and it cannot, even when asked.
Vega on Antigravity
The pipeline and the paperwork, kept moving
A crew that preps every call, answers deal questions inside your rules, and takes the recurring operations work off your desk.
Every call prepped before your coffee
- Every weekday morning, Ledger opens your CRM in the built-in browser and lists the day's calls
- It reads each company's news and writes a one-page brief for every call
- Tell it how a call went, and the next brief picks up from there
It opens your CRM only once you allow it, and each form it would send waits for you.
Ledger on Antigravity
Deal questions answered inside your rules
- Your team asks in Slack, and Ledger answers from your own price book, with the page cited
- It checks a customer's plan and invoices in Stripe before it answers
- When a deal needs your call, it says so in the thread and leaves it to you
Stripe is read-only for it, so it cannot refund or change a plan.
Ledger on Antigravity
Receipts, invoices and reports, handled as they land
- Drop a receipt or an invoice in a folder, and Relay logs the vendor, the date and the total
- At month end, it totals them by category for your bookkeeper
- Every Monday, it writes the ops report from last week's numbers, in the same format every time
Paying an invoice in the browser asks every time. No rule can allow it.
Relay on Codex
Every client, with a crew of its own
Give each client a program: its own crew, tools, secrets and rules, kept apart from every other client's.
Client work that never crosses wires
- Each client is a program, with its own crew, connectors, secrets and rules
- Nothing crosses from one program to another: no files, no tools, no conversations
- Switch clients from the menu bar in one click
Each client's secrets are encrypted, and granted crew member by crew member.
Relay on Codex
The client report, written every Friday
- Every Friday, Scribe gathers what shipped, what is in review and what is blocked
- It writes the report in that client's template, kept as a skill in that client's program
- Each program's usage is counted on its own, so you know what each client cost to serve
Each program has its own daily token ceiling, so one client cannot spend another's budget.
Scribe on GitHub Copilot
A new client set up in minutes
- Export the crew that worked for your last client, and import it for the next one
- Or describe the job in a sentence, and the Crew Builder proposes a team for you to approve
- Your playbooks travel as skills, so every client gets the same process
An export carries the crew, its schedules and skills, never secrets, conversations or memory.
Relay on Codex
Your sources, notes and drafts, working together
A crew that searches everything you have collected, cites where it found it, and keeps the draft moving on your schedule.
Answers from your own sources, cited
- Point a collection at your notes folder, and Atlas searches all of it
- Every answer cites the file and the line, like interviews/june.md:112
- It can run on a model on your own computer, through Ollama or LM Studio
It reads Markdown, text and CSV. A change outside its own folder asks first.
Atlas on Ollama
A first draft waiting each morning
- Every weekday at 6, Scribe turns yesterday's notes into the next section of your draft
- Your style sheet is a skill it reads before every draft
- It remembers your corrections, so you make each one once
It writes in its own folder. Your manuscript changes only when you allow it.
Scribe on GitHub Copilot
Every claim checked before it goes out
- Drop a finished piece in a folder, and Atlas lists every claim that needs a source
- It checks each one against your library and the web, and marks what it could not confirm
- Months later, it can find the turn where a fact was checked, and how
The web asks site by site, so you see every new source it opens.
Atlas on Ollama
The life admin, off your mind
A small crew for home: it plans the week, files the paperwork and does the research. It can run on a model on your own computer, with no account to make.
Monday's plan, ready before you are
- Every Monday at 8, Planner writes the week from your notes and what is left from last week
- Add a line to your notes any time, and it is in next week's plan
- It keeps a list of what slipped, so nothing quietly falls off
It has no shell, so it cannot run a command at all.
Planner on Ollama
Receipts and bills filed the moment they land
- Drop a receipt or a bill in a folder, and Hearth logs the date, the store and the total
- At month end, it adds them up by category, ready for your budget
- Each month, it lists the renewals coming up from the bills it has filed
Banks and payment sites are closed to its browser unless you open them yourself.
Hearth on LM Studio
The research done, the decision yours
- Ask for a trip plan, or the three best laptops for your budget, and Atlas does the reading
- It saves its picks and its sources in a folder you can open
- It remembers what you like: window seats, no red-eyes, the budget you set
It can look, but it cannot buy: paying in the browser asks every time.
Atlas on Ollama
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.
- 07:00
Beacon Flight plan
Every weekday: draft the day's posts
- 09:00
Ledger Flight plan
Mondays: the pipeline report, to you
- 11:42
Ledger Trigger
receipt-0193.pdf landed in Inbox
- 14:15
Girder GitHub
Issue #212 opened: “Staging deploy fails”
- 16:30
Anvil Slack
#release: “Is 2.1 ready to tag?”
Wants to run a command: waiting on you
- 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
| Aspect | A coding CLI on its own | Hypergol |
|---|---|---|
| Who you talk to | One assistant per terminal window | Named crew members that persist, each with a job and its own memory |
| Memory | Per session or per project | Per crew member, recalled across conversations, kept inside one program |
| What it may touch | Whatever your account can reach | A clearance per crew member; anything else asks you first |
| Working together | You copy answers between windows | Missions, handoffs between crew members, @mentions |
| Acting on its own | You start every run | On a schedule, when a file lands, on a GitHub issue or a Slack message |
| Models | The one your tool is signed in to | A provider and model per crew member: your subscriptions, API keys, or a model on your computer |
| Cost control | Limits per tool | 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.
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
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
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
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.
An address, not an account. The app itself sends us nothing about you. The download starts on the same click.
- Join before it ends
- Stays free for you
- Updates
- Included
- Your AI
- Subscription, API key, or local model