Talk to HAL
Choose a thinking mode and turn a rough idea into a clear next move.
Open chatStart with what works today. Follow the source. Bring your own models. Keep machine authority explicit. Build a small piece, prove it, then let the system grow.
No roadmap maze. These are the most useful entry points into the current public system and its source.
Choose a thinking mode and turn a rough idea into a clear next move.
Open chatWatch the newest promotion-gated film with chapters, transcript, captions, and provenance.
Open WatchUse the OpenAI-compatible surface with your own providers, policy, and credentials.
Self-hostTrace the architecture, run tests, open an issue, or offer one focused improvement.
GitHub ↗HAL should own the build loop, not just describe it. Here is the current boundary, without a pretend green light.
Ask for code, a design, or help debugging. A code answer is not proof that files were changed or tests ran. Public chat does not gain access to your computer.
Discuss a buildThe open-source operator adapter prepares a task for one selected project and an exact verification command. Preparation stays blocked until explicit local release.
Local implementation candidateThe existing worker edits through a bounded coding client; passing workspace verification goes to human review. This is not yet a verified end-to-end build from public chat.
Keep claims attached to proofSelf-host, inspect the adapters, and contribute a test or integration. Release, paid compute, uploads, and deployment remain separate decisions.
Choose your setupHAL owns durable intent and evidence. Models and workers are replaceable. Public pages are projections, never a second source of authority.
A mission becomes bounded tasks with dependencies, ownership, and visible acceptance.
WorkGraphEvents and receipts preserve what actually happened without rewriting history.
EventStoreLocal and hosted models can route by privacy, cost, latency, quality, and current health.
Provider fabricChat, sound, video, and embodied runtime surfaces make accepted work visible.
Public + local surfacesOpen source does not mean open season on your machine. Capabilities become useful through named grants, readable policy, and receipts.
Connect through familiar model and chat routes.
Grant one project, propose exact file changes, and run named checks.
Add bounded capabilities without handing one tool every permission.
Bring a compatible endpoint or keep the entire path local.
A useful system makes the boundary legible: what it can read, what it may change, what costs money, and which action still needs a person.
The open-source path is not a license paywall. More funding could support stronger model capacity, reliable build sandboxes, hosting, accessibility testing, and better media production. These are improvement priorities, not delivered features or unlimited-compute promises.
Code, bug reports, documentation, and thoughtful review help too. No checkout or donation collection is enabled by this page.
The repository is the workshop floor. Start with a reproducible issue, an accessibility improvement, a focused test, a clearer document, or a new bounded integration.