DonaldMurillo/system-one-playground
User repository on GitHub
Readable scripting, semantic code checks, a Go System One client, and Studio.
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.Homepage
CommunityJev Repos & SDKs
System One Playground
A Go repository around the TypeSafe System One API that also ships a released CLI and a VS Code extension. SysOneScript scripts run offline, semlint inspects source and proposes checks, Studio is the editor front end, and the typesafe subpackage talks to Jev from your own module.
- Stars
- 1
- Language
- Go
- License
- MIT
- Published by
- Community
- Author
- DonaldMurillo
- Last verified
- Oct 2026
About this project
Build readable scripts, semantic code checks and developer tools with the TypeSafe System One API. Use SysOneScript from your terminal or Studio, call the API directly from Go, or try semlint on your code. Start offline. Add Jev judgments when you need them. Repository name: system-one-playground. MIT licensed · SOS 0.5 preview. You do not need to clone this repository or install Go to use the released CLI or VS Code extension. Install the latest standalone CLI on macOS or Linux:
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- Go
Highlights
- The released CLI installs sos and sysone from a checksum-verified script, and sysone build turns a .sos file into a standalone executable.
- The VS Code extension bundles its own runtime, language server, runner, builder, formatter and debugger, so no Go toolchain or separate CLI install is needed.
- semlint ships twice, as Go and as an SOS script; sites-only mode inspects source and prints planned checks without making any API call.
- Parallel workers share request and time limits, and the README is explicit that those limits are not an account-wide monetary cap.
Watch out
SOS is a 0.5 preview: local packages and native builds work, but remote package resolution and a plain JavaScript emitter are not implemented, browser and WASI behaviour depends on the libraries you import, and live Jev host adapters are not available. Installing means piping a release script into a shell. The installers do verify a release checksum and let you pin a version or choose a directory, but the Unix one writes to ~/.local/bin and only warns you when that is not on PATH, and sysone and sos must stay together because sysone delegates language commands to sos. Studio needs Node.js 18+ and pnpm even though the extension does not, and the stated Go versions differ: 1.25+ to build the CLI, 1.27+ for the docs site. The project uses the TypeSafe System One API but is not the provider's official SDK or documentation. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
It is a normal release-script install with a few guards. Both the Unix and the PowerShell installer detect the platform, verify the release checksum, and install sos plus sysone. You can pin the release with SYSONESCRIPT_VERSION or redirect it with SYSONESCRIPT_INSTALL_DIR. On macOS and Linux the default is ~/.local/bin and the installer tells you if that is not on PATH; on Windows it uses %LOCALAPPDATA%\Programs\SysOneScript\bin and adds it to the user PATH. Later releases are explicit: sysone update --check then sysone update, and the CLI never updates itself silently.
Not for normal use. The README states you do not need to clone the repository or install Go to use the released CLI or the VS Code extension, since the extension ships the matching runtime and language server for your platform. Building from source needs Go 1.25+ to produce sos and sysone into bin. The documentation site separately asks for Go 1.27+, which is worth knowing if you only intend to work on the docs. Studio's frontend adds Node.js 18+ and pnpm on top of the three Go executables.
Only the model-backed operations need a token. Canonical scripts run offline, and the first script the README walks through prints its output with no API key and no Node.js. The sites-only semlint mode inspects source and shows planned checks without calling the API at all; the example that stresses Jev with eight semantic decisions, and go run ./cmd/playground 01, do make paid provider requests. Parallel workers share request and time limits, and the README states plainly that those are not an account-wide monetary cap, so a spend ceiling is yours to enforce.
Less than the feature list suggests, and the README says so. Local packages and native builds work, and sysone build ships a checksummed standalone executable whose recipients need neither Go nor SysOneScript. Remote package resolution and a plain JavaScript emitter are not implemented, browser and WASI capabilities depend on the imported libraries, and live Jev host adapters are not available. The language docs are linked for the limits, and the Go API demonstration in cmd/playground is the direct route if you only want the client.
Create hello.sos with make and show statements, then run sysone run hello.sos; it prints with no API key or Node.js, and sysone build hello.sos --output bin/hello turns it into a standalone executable.
A code-checking tool that ships twice, as Go and as an SOS script; sites-only mode inspects source and prints planned checks without making any API call, so you can try it offline.
Set TYPESAFE_API_KEY in your environment or use Set Jev token in the VS Code project panel; canonical scripts run offline, and only the model-backed Jev operations need the token and can make paid requests.
More Jev resources like this
45GitHub stars
Go SDK plus a pipeline-friendly CLI for typed decisions, covering single questions, batched question maps, retries, and line-oriented filtering over stdin.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
mattn/go-jevGo
mattn/go-jevGo9GitHub stars
Go SDK for the TypeSafe API that asks typed Noul, Choice, and Score questions about a state and returns probability distributions with confidence and typed accessors.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
Tangerg/typesafe-sdk-goGo
Tangerg/typesafe-sdk-goGo8GitHub stars
Unofficial Go client for the TypeSafe System One API that sends a state plus typed Noul, Choice, and Score questions in one call and returns typed answers with model, usage, and request ID.
Jev Repos & SDKs#community#awesomejev#catalog-import
Community
devbackend/jevgoGo
devbackend/jevgoGo4GitHub stars
Community Go client for the TypeSafe System One evaluation API with raw structs and a builder that produce the same EvaluationRequest, defaulting to jev-latest.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
kisshan13/typesafe-ai-goGo
kisshan13/typesafe-ai-goGo1GitHub stars
Unofficial, independently maintained Go client for the TypeSafe AI System One API with no third-party dependencies: choice, score and noul questions, typed accessors that error instead of returning zero, and per-call timeout, retry and header overrides.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
cole-gillespie/typesafe-goGo
cole-gillespie/typesafe-goGo2GitHub stars
Community Go client for the TypeSafe AI System One API covering the same surface as the official Python and TypeScript SDKs, using functional options, context cancellation, sentinel errors, `log/slog`, no dependencies outside the standard library, and optional Langfuse tracing.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
fgn/jevgoGo
fgn/jevgoGoFrom the Jev guides
Original write-ups on what this entry is for.
Closed weights have not stopped the ecosystem from rebuilding the shape in the open. API-compatible servers, retrained heads on small models, and inference-time tricks that skip generation entirely.
Jev Repos & SDKs#open-models#research#local
Read article
From the Jev community
Posts from builders shipping with Jev right now.