Prerequisites

Prerequisites

These are the requirements for the current private-alpha source build. They are development requirements, not a promise about what the eventual public installer will need.

Required toolchain

Right now the exact versions matter:

• CPython 3.14.7;
• the normal standard-GIL CPython build;
• callable sys._is_gil_enabled() returning True;
• Node.js 24.19.0;
• npm 11.17.0;
• Git.

The setup scripts check these versions for you. They do not try to become a general-purpose Python or Node version manager.

Optional tools

Some workflows also use:

• Docker;
• Git LFS;
• external llama.cpp tooling;
• Hermes or OpenCode CLI integrations.

You only need these if you plan to use the workflows that depend on them.

Platform support today

Native Windows PowerShell

Native Windows PowerShell is the current primary development environment and the best-validated platform.

The current full-stack validation exercised the root launcher, backend/frontend, registered modules, ConPTY/pywinpty Terminal flow, Agent Runtime, Model Manager, durable run state, and Nexus-owned process cleanup together on a real native-Windows host.

Linux

Linux remains a portability target with Bash setup/startup and POSIX PTY paths in the repository.

It has not had the same recent maintainer validation as native Windows, so current parity should be validated rather than assumed from older evidence.

Windows through WSL

WSL remains an optional compatibility path, not the current recommended Windows development route.

If you use it, keep the repository inside the WSL filesystem for the normal Linux/WSL workflow instead of putting it on a mounted Windows drive.

macOS

macOS is not currently part of the validated support target.

Do not assume macOS support just because the browser UI, Python, or Node can run there.

Next

Continue with Private-alpha setup.