Jev directory
CommunityJev Tools & CLIs
SysOneScript for VS Code
Language support for SysOneScript (.sos) that wires VS Code to the native language server and runtime: a DAP debugger, stream inspection, a project-control dashboard, and Jev tokens stored in SecretStorage.
- Reading time
- 2 min
- Published by
- Community
- Author
- donaldmurillo
- Last verified
- Oct 2026
Highlights
- Publisher donaldmurillo, 6 installs; adds .sos support backed by the repository's stdio language server and native runtime.
- No runtime npm dependencies: it uses the VS Code API plus Node's built-in process and stream modules.
- The DAP debugger offers breakpoints, stepping, locals, stack frames, conditional breakpoints, logpoints, and Jev trace output.
- Jev tokens live in VS Code SecretStorage and reach the language server, runner, and debugger as TYPESAFE_API_KEY only at start.
- The panel does folder-level Run, Check, Build, Debug, and Stop, and follows the active .sos file to its nearest sos.toml.
Watch out
The page names no licence, and the marketplace install count is 6, so treat it as an early project. It compares the bundled runtime with sysone on PATH and warns once per session when versions differ; helpers and generators come from .vscode/sysonescript.json.
Questions about this entry
Short answers drawn from the linked project or page.
An extension that adds .sos language support and connects VS Code to the repository's stdio SysOneScript language server and native runtime, with no runtime npm dependencies beyond the VS Code API and Node's built-in process and stream modules.
Install from the Marketplace, or build and package it: go generate ./internal/sosbuild, go build -o vscode/bin/sos ./cmd/sos, pnpm --dir vscode check, test, and package, then code --install-extension vscode/sysonescript-vscode-0.5.1.vsix.
Use SysOneScript: Set Jev Token or the panel's key button. The token is stored in VS Code's encrypted SecretStorage and injected into the language server, runner, and debugger only when they start; it is never written to workspace settings or shown in output.
A native Debug Adapter Protocol debugger launched with sos debug, offering breakpoints, stepping, locals, stack frames, expression evaluation, conditional breakpoints, logpoints, and Jev trace output, with credential-shaped names redacted from the Variables view.
It is a project-control dashboard, not a second Explorer: it shows the active project and resolved entrypoint, then exposes folder-level Run, Check, Build, Debug, Stop, helper, generator, and Jev controls, following the active .sos file to its nearest sos.toml in nested workspaces.
No for Marketplace releases: they include a platform-matched sos language-server binary. Development checkouts without a bundled binary can use sos on PATH or set sysonescript.server.command to an absolute executable path.
Add project-defined actions to .vscode/sysonescript.json under helpers. Known SysOneScript commands (run, check, build, fmt, explain, config, vocabulary) use the bundled runner; other commands resolve as executables on PATH or through the configured runner environment.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.