For agents

Use this site to learn the TypeSafe Go client, SysOneScript, Studio and semlint. The public GitHub Pages site serves static documentation. It does not execute code or host MCP or A2A tools.

Read the documentation

  1. Fetch llms.txt for discovery and setup.
  2. Read the Markdown index to find relevant pages.
  3. Fetch a page's explicit Markdown URL, such as Jev enablement, the language reference, or the project CLI/MCP reference.

Use the explicit /llm.md URLs: GitHub Pages does not provide dynamic content negotiation. The exported agent card is descriptive metadata with no callable interfaces. There is no live /mcp on this public site. Search and the sitemap provide additional discovery; no API key is required to read docs.

Install and inspect a project

9 lines
git clone https://github.com/DonaldMurillo/system-one-playground.gitcd system-one-playgroundgo 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 --project examples/sos/repo-assistant treesysone --project examples/sos/repo-assistant config main.sossysone --project examples/sos/repo-assistant check main.sos

Go 1.25+ is required. Keep the three binaries together. Global --project precedes the command. tree, config and canonical check do not make provider requests. Read the source and effective limits before running or analyzing unfamiliar code.

Connect a local MCP client

Configure your agent's MCP client with absolute paths:

8 lines
{  "mcpServers": {    "sysone": {      "command": "/absolute/path/system-one-playground/bin/sysone",      "args": ["--project", "/absolute/path/your-project", "mcp"]    }  }}

This starts the project service over stdio, not HTTP. It exposes file tools, settings, check, analyze, run and build. It operates on project files or explicitly supplied source, not an existing Studio window's unsaved buffer. See tool schemas and behavior.

The separate Go documentation server exposes documentation MCP when run locally with cd docs-site && go run .. That service is for docs and is not a substitute for sysone mcp. It is absent from static deployment.

A useful working sequence

  • Inspect the project tree, read the relevant files and effective settings.
  • Use check for local validation; analyze/explain may spend Jev requests.
  • Use revision-aware writes: read first, then supply the returned revision when replacing a file. Reconcile conflicts rather than overwriting blindly.
  • Run with appropriate request/time limits. Inspect output, errors, interpretation, traces and usage.
  • Build from saved files. Test the resulting CLI; a build succeeding does not prove a judgment was appropriate.

For structured scripting without an MCP client, sysone api run accepts JSON on stdin. Provider credentials belong in the launching environment or project settings, not source or committed client configuration. Environment listing returns names/status only; secret writes can still be logged by the invoking agent client.

Enable Jev deliberately

Follow Add Jev to your application for all enablement paths. Explicit judgments, semantic interpretation and editor assistance have separate controls. Execution may write files, run subprocesses or make paid requests. Budgets constrain requests and time, not account-wide monetary spend. Do not treat model confidence as authorization to perform an external action.

← PreviousAdd Jev to your applicationNext →External modules