Get started
SysOneScript source files end in .sos. Clone https://github.com/DonaldMurillo/system-one-playground.git. The preview ships source; prebuilt installers are not available.
Build the language tools
Use Go 1.25 or newer from the repository root:
go build -o bin/sos ./cmd/sosgo build -o bin/sysone ./cmd/sysonego build -o bin/sos-studio ./cmd/sos-studioexport PATH="$PWD/bin:$PATH"sysone version
Keep these three executables together. sysone delegates language commands to sos; the browser workspace uses sos-studio. The documentation site is a separate Go 1.27 module and is not required to run the language.
Run an offline script
Create hello.sos:
make message "hello from SysOneScript"show message
sysone check hello.sossysone run hello.sossysone build hello.sos --output hello./hello
The output is hello from SysOneScript. No API key is required. Building requires Go; running the resulting native executable does not.
Open a project
sysone --project examples/sos/repo-assistant open studioSelect main.sos in the file tree. The repository example includes commands, a local multi-file package, fixtures and a project configuration. Follow Build a repository CLI for the offline import, triage and report workflow.
Use open examples for the smaller example experience. The selection persists per project. The browser launcher stays in the foreground; Ctrl-C stops it.
Add Jev when needed
Use Studio's Settings to set TYPESAFE_API_KEY for your project. Values are saved in a local .env with restrictive permissions; keep it out of version control. CLI scripts can also use the launching environment. See environment precedence for the differences.
Start with Add Jev to your application for credentials, every enablement switch and complete workflows. Then use the interpretation guide and configuration and budgets. Inspect Interpretation for sentence resolution, and Trace for runtime judgments and reported usage. A successful run alone does not explain which records were selected.