Try the current build
Install the published Windows Developer Alpha and use PAI on a real project. The updater keeps you on the active testing channel as new builds are released.
PAI is an autonomous, local-first development system built to work across an entire project. It maps the codebase, plans the change, edits the right files, runs checks, diagnoses failures, repairs them, and verifies the result before calling the work complete.
The current Developer Alpha is public. Alpha 9 is in final release-candidate validation, and feedback from real projects is what determines what gets fixed and hardened next.
Install the published Windows Developer Alpha and use PAI on a real project. The updater keeps you on the active testing channel as new builds are released.
Give PAI actual coding, debugging, refactoring, or project-wide work. The most useful feedback comes from places where the system gets confused, stalls, or fails verification.
Join the Discord for release announcements, tester discussion, bug reports, suggestions, development previews, and the fastest path back to the project.
The target is a coding system you can hand real work to—not a chat box that stops at “here’s some code.”
PAI maps the project, languages, frameworks, requirements, dependencies, and cross-file contracts before deciding what needs to move.
It creates and edits files, follows the project’s existing structure, and keeps the requested scope connected to actual implementation.
Builds, tests, deterministic checks, and repair passes give PAI evidence that the request is complete before it calls the task finished.
PAI combines project understanding, coding, verification, local model execution, and recovery into one desktop workflow.
PAI is designed to determine which files matter, preserve surrounding behavior, make bounded changes, and keep moving until the work reaches a verified outcome.
PAI-Coder ships as a native local runtime with CPU fallback and CUDA acceleration where supported, reducing setup friction and keeping local development local.
PAI uses compiler output, tests, runtime evidence, requirement checks, and project contracts to decide whether a change can actually be accepted.
Checkpointing, bounded repair, update rollback, preserved originals, and explicit outcome states are part of the architecture—not cleanup added later.
PAI is designed to stay model-independent. The application owns project understanding, planning, editing, execution, verification, recovery, and the user experience while coding models do the language work inside that system.
Download the current developer alpha, put it on a real project, and bring the results to the Discord. Tester feedback is feeding directly into the reliability work leading from Alpha 9 toward Beta.