Projects
Separate goals, people, connections, permissions, budgets, and work history. A project is context—not a second scheduler.
Planned after identityCreate projects, keep artifacts and memory together, connect the systems you choose, and let HAL help build—without turning your computer into an unrestricted remote shell.
The personal workspace is the durable center. Chats become useful when decisions, files, receipts, preferences, and lessons can stay attached to the project that produced them.
Separate goals, people, connections, permissions, budgets, and work history. A project is context—not a second scheduler.
Planned after identityFiles, code, media, receipts, and releases with source lineage, review state, and clear private/public boundaries.
Existing HAL foundationUser-controlled facts and preferences with edit, export, expiration, and delete controls. No invisible permanent profile.
Planned user surfaceLessons, decisions, contradictions, and next actions that improve future work without rewriting canonical history.
Existing HAL patternConnections bring data or capability. Plugins package a bounded workflow. Skills teach HAL how to use them. Every item shows what is live, what is a developer preview, and what is only planned.
Sign in and establish an opaque HAL user and private workspace identity.
Grant specific local project folders, propose file changes, and run named checks.
Projects, issues, commits, reviews, and release evidence through user-authorized access.
Bring selected documents and media into a project without giving blanket account access.
Slack, Teams, email, calendars, and project tools with per-action approval controls.
Connect compatible tools locally now; authenticated remote MCP remains a separate gated release.
Machine-readable product truth: HAL capability and plugin catalog.
HAL should choose from resources the user has authorized—not trap users inside one model company. Provider health, privacy, latency, quality, and estimated cost remain visible.
Connect OpenAI, Anthropic, Google, xAI, or other compatible providers through account-bound credentials that never enter prompts or public projections.
Connection UI plannedConnect OpenAI-compatible local endpoints for private or low-cost work. Discovered does not mean healthy; each route needs a live canary.
HAL routing foundationOffer selected local compute to your own HAL workspace with thermal, memory, time, privacy, and job-type limits. No public GPU marketplace or payouts in V1.
Planned connectorIsolated, disposable build environments for paid users. Cloudflare Sandbox/Containers is the intended lane; usage has real compute cost and must be quota-bound.
Planned paid capabilityThe current prototype is local stdio MCP. A future cloud connection must be outbound-only, authenticated, revocable, and unable to approve its own mutations.
Local approval stays local. A proposal becomes invalid if the file changes, and every approval is single-use. The current process boundary is not represented as an OS-enforced sandbox.
Each project will expose the same permission model in plain language: what can be read, what can change, which providers can run, what may cost money, and what needs a person.
A subscription funds the workspace, orchestration, memory controls, integrations, and support. Expensive model, music, video, GPU, and sandbox usage stays separately capped so one heavy job cannot consume everyone’s service.
Try the signed-in identity workspace and follow verified product progress.
For an individual connecting projects, tools, and their own model accounts.
For creators using voice, music, image, and video workflows with explicit limits.
For a small design partner that needs shared projects and a guided integration.
Customer usage price = Provider cost ÷ 0.70. That targets a 30% gross margin before payment processing, billing, storage, support, refunds, and taxes. Every job still shows a maximum price before admission.
A $10 estimated provider cost becomes $14.29. At PayPal's currently published US domestic Checkout rate of 3.49% + $0.49, about $3.30 remains before storage, support, refunds, taxes, and other costs. It is not net profit.
PayPal's fixed transaction fee makes per-job micropayments inefficient. Launch with prepaid, non-transferable platform usage or a capped monthly balance, then reconcile every provider receipt. Current PayPal fees.
Turn the current working system into evidence investors and partners can evaluate: a small paid pilot, one connected project, one trustworthy local build flow, clear unit economics, and repeatable proof.
Partner and investor conversations are private, individualized discussions. This page is not investment advice and is not a public offer of securities.