algal
Install

Use cases

Put living programs
to work.

Use ALGAL when the work around a model matters: a human decision, a restart, independent checks, or a reviewable history. Useful work, with a clear finish line.

Change review · Native VM

Draft privately.
Publish only what you approve.

Turn a small set of change notes and check results into a retained proposal. Leave it waiting, then approve that exact report in a new invocation. Denial publishes nothing.

You keep: the input evidence, proposal, decision, and local publication.

Run the fixture workbench Use the real on-device Apple model
Coding repair · Bun host

A coding attempt ends.
The checks decide what follows.

Admit a source revision and fixed acceptance commands. Retain the proposed patch, check that exact patch, and produce a review packet. An uncertain launch stays unresolved instead of quietly starting again.

You keep: the patch digest, source binding, check outcomes, and custody record.

Run the deterministic repair episode Understand adapter reconciliation
Execution audit · Either runtime

Share the history.
Verify it elsewhere.

Export a bounded execution capsule. Verification needs no model or credentials and works after the source store is moved away. Altered hashed records and missing dependencies fail verification.

Inspect retained prompts, outputs, and capability strings before sharing; the export does not redact them.

You keep: one portable file and a verified process head.

Export and verify a history See what the evidence proves
Support workflows · Readable source

Route the request.
Reuse the part that works.

Classify an email, execute only its selected response branch, and use the same draft helper over a bounded inbox. Each effect receives declared context; inactive branches make no model calls.

You keep: reusable program artifacts, ordered results, and replayable receipts.

Inspect three recorded routing paths Explore the reusable inbox

Also included: a read-only PR shepherd that waits for CI and collects revision-bound evidence without model calls. Live coding providers require separate host configuration and qualification. All use cases, commands, and adoption boundaries

Choose the right boundary

Start with a bounded
workflow you own.

ALGAL fits local review queues, checked coding episodes, reusable judgment pipelines, and inspectable evidence. A single unstructured prompt may need less machinery. Existing durable workflow engines may already meet your recovery needs.

This is an application VM prerelease. Packages are unsigned and unnotarized. Hosts still own tool permissions, external-effect reconciliation, storage operations, and any required OS isolation. Multi-tenant service operation, distributed custody, and global quotas are unfinished.

Receipts check execution consistency, not factual truth or provider attestation. Unknown external writes are not made exactly-once by replay. The adoption guide explains these boundaries before you connect a real system.

Ready to author? Compile your first readable program

Start with the working VM

One executable.
A review you can return to.

Download and verify a native prerelease. The built-in workbench needs no checkout, Bun, Cargo, credentials, or web server. Use a fresh directory for each demo.

Download the prerelease

Or take the guided tour first

Terminal · after installationRetain / review / prove
# Inspect the installed build identity
algal doctor

# Leave a real process waiting for your decision
algal demo start ./my-review
algal demo inspect ./my-review

# Open my-review/report.html for the exact decision command

# Kill owned VM children and check their recovery
algal demo prove ./crash-laboratory

Inspect crash-laboratory/proof.json: approved once, denied without publication, completed writes reused after a read crash, and an uncertain write blocked from redispatch. Fixture decisions; real processes, journals, and verification.