Osy# is a language for whole applications — data, rules and screens in one program — with a compiler that decides where each line runs, secures every read, makes outside calls happen exactly once, and refuses a deploy that would lose your data. This repository is where the toolchain binaries are released and where issues are filed. The language, the reference and the guides live at osysharp.com.
macOS and Linux:
curl -fsSL https://osysharp.com/get | shIt puts one binary in ~/.osy/bin. The first run fetches its database bundle — a real PostgreSQL — once.
Windows: download osy-windows-x64.zip from the latest release
and put its folder on your PATH (osy.cmd is the local surface). Homebrew and winget channels follow.
osy init --agent claude # a complete app with its tests, and a CLAUDE.md for your coding agent
osy check # validate, lint, test — one verdict
osy launch # run it in your browser on a local platformStart here: osysharp.com/reference/local.
osy feedback opens a prefilled issue here with your version and the last diagnostic. osy feedback --full adds
a diagnostic bundle, uploaded privately — the issue carries only its id, never the file. Or just
open an issue.
The toolchain sends anonymous usage counts — command names, versions, OS, error codes — with two random ids so a
person is counted once and a project can be followed to its first deploy. Never your source, your data, your
paths, your name or your address. osy telemetry off stops it; the first run tells you it is on. Exactly what is
sent: osysharp.com/reference/project/statistics.
Beta. The language and the local platform are ready to build with; hosting is opening. Things will move between
versions — --new-version on a deploy is how nothing you already shipped breaks when they do.