Describe. Inspect. Accept.
Choose the context to share, explain the workflow, and try an isolated preview. No proposed behavior becomes your packaged app until you accept it.
NEW / BROWSER PLAYER PREVIEW
Your export. A working app. No install.
Bring your own JSON or CSV, review a workflow, and download a self-contained HTML app. No live AI calls.
LOCAL-FIRST SOFTWARE, DESIGNED WITH GPT-6 ASTRA
AI builds the workflow.
You keep
the app.
An export saves your records. Lifeboat turns them into a working local tool. Describe a workflow to GPT-6 Astra, inspect the rules it proposes, and keep the app after the AI connection ends.
No sign-up. No API key for the sample. No pretend AI chat.
THE OWNERSHIP TRANSFERFIG. 01
01 / BRING YOUR DATA
One export.A fresh start.
GitHubJiraTrelloCSV
02 / REVIEW THE RULES
+ Add priority
+ Move to Open
Only if the item is not archived.
Designed with Astra. Approved by you.
03 / TAKE IT WITH YOUYour local appNo AI connection required to run.
START WITH A SNAPSHOTGitHub IssuesJiraTrelloCSVImport once. Nothing writes back.
NOT A CHATBOT YOU HAVE TO KEEP PAYING TO RUN
The output isn't a reply.
It's a rule you keep.
For maintainers archiving a project, teams moving between issue trackers, and people who need an export to remain useful, not just readable.
Turn intent into explicit rules.
Astra proposes guards and compositions of supported actions from your reviewed context. Its output is an inspectable contract, not unrestricted generated code.
Run the accepted behavior locally.
Deterministic code checks the guard and applies the steps. No model decides what to do each time you click. No runtime API key or AI call is required.
ONE REAL ASTRA BUILD / ACCEPTED SEPTEMBER 17
A regression report becomes
a repeatable triage action.
The intent: reopen the issue and add priority, but never touch archived items.
The accepted behavior: check card_not_archived, add the existing priority label, then move the item to Open.
The handoff: the reviewed contract travels inside the downloadable Player. Source history stays separate from the local working state.
INSPECT THE ACTUAL RELEASE ARTIFACTSOpen the real app contract Open its acceptance record Read what passed and what did not
Contract SHA-256
16ca01a5477b0c38cccdb8e807722af9802195638148980159f2423f538f21bdThis is a small example on fictional data, not proof that arbitrary workflows are supported. The browser sample below illustrates the same idea; it is not a live Astra session.
A SMALL DEMO. A DIFFERENT RELATIONSHIP WITH AI.
Give this issue
a second life.
Review the rule on the right. Accept it. Reopen the closed issue with a priority label in one action. Then export what changed.
BROWSER SAMPLE
Fictional Harbor CLI data. Pre-generated Astra workflow. No live model calls. This is an interactive illustration, not the downloadable Studio or Player.
Preserve executable permissions when restoring a backup
REPORT FROM THE FICTIONAL TEAM
Local revision 1
YOUR CUSTOM ACTION
First, review and accept the sample contract.
Try the guard: archive the selected issue, then run the action. The workflow must refuse it, rather than silently changing your data.
Browser storage is not a backup. Export your sample changes, or get the standalone Player for the real local-app experience.
FROM A SNAPSHOT TO SOMETHING YOURS
Build with AI.
Don't depend on it.
Use intelligence where it matters: designing the behavior. Keep the everyday execution explicit, inspectable, and local.
Start with what
you already have.
Bring a GitHub, Jira, Trello, or CSV snapshot. Review the import report and the context you choose to share with Astra.
Describe the job.
Read the rules.
GPT-6 Astra proposes a workflow contract with guards and supported actions. Try an isolated preview before you accept it.
Take your app.
Leave the dependency.
Download a Player with your data and accepted behavior. Run locally without Studio, an API key, or an AI connection.
A REAL CHECK, NOT A FUTURE PROMISE
We switched
the connection off.
In our September 17 standalone check, the real Astra-designed workflow ran in a downloaded Player with Studio stopped, no API keys, and external outbound networking denied for the Player process.
We restarted it. The edits were still there. The original export's checksum had not changed.
Read the preview release notesSTANDALONE PLAYER CHECK2026-09-17
- Studio process
- Stopped
- API keys
- Absent
- External outbound access
- Denied
- Workflow + saved edits
- Worked after restart
- Original export
- Unchanged
One fictional GitHub-format dataset, macOS Apple Silicon. This is a bounded validation result, not a claim that every environment has been tested.
THE ACTUAL PRODUCT, NOT UI MOCKUPS
From Studio
to your own workspace.
Real interface captures, with the test context kept explicit. Click either image to inspect it at full size.
TAKE IT FROM HERE
Not just an export.
Your next tool.
An early preview for people who want more ownership of the tools they use. Start with a ready-made app, or design a workflow of your own.
Known install blocker
This preview is not Developer ID-signed or notarized. In our September 18 check, macOS rejected a quarantined Player downloaded through the browser, despite its binary matching the earlier tested build. We have not resolved that installation path. Use the browser sample if macOS blocks the download; do not disable system security. Windows and Linux binaries are not provided. A separate clean-machine walkthrough is still pending. Read the exact validation scope.
THE SMALL PRINT, IN NORMAL TYPE
Good questions.
Is this a live integration with my issue tracker?
No. Lifeboat imports snapshots. Actions in your local app do not write back to GitHub, Jira, or Trello. Some source fields remain raw-only rather than becoming editable app fields.
Where does GPT-6 Astra fit in?
In Studio, Astra helps turn reviewed context and a workflow request into an inspectable contract. You accept the behavior before packaging. The downloaded Player executes supported actions locally, without calling the model for each action. The browser sample above uses a pre-generated workflow and makes no model calls.
Does my data leave my device?
The browser sample uses only fictional data and stores changes locally when browser storage is available. It does not upload issues. In Studio, the context you submit for AI design is sent to the model provider using your API access. Review that context before submitting. The public site is hosted by GitHub Pages; following external links or loading the optional Product Hunt badge contacts those services.
Is the preview free?
The preview downloads and browser sample are free. Designing new AI workflows requires your own API access, which can incur provider charges. The ready-made Player does not need a key.
Is the browser sample the full product?
No. It is a small, client-side illustration of reviewing and running a contract. It does not import your files, call Astra, generate applications, or implement the full Player runtime. Download Studio or Player to try those local workflows.
LOOKING FOR OUR FIRST INDEPENDENT TESTERS
Three minutes.
Honest friction welcome.
Try the browser sample, test the archive guard, and export the result. Tell us where you hesitated and which real workflow would make this useful. We are collecting feedback, not claiming testimonials we do not have.
Open the first-user checklist
GitHub comments are public and require a GitHub account. Never post API keys, tokens, or private exports. You can also reply on Product Hunt. No votes or purchase required.
BUILT WITH GPT-6 ASTRAA small launch.
A small launch.
A bigger idea about ownership.
Tell us which workflow you would want to take with you.
Join the conversation on Product Hunt