Skip to content

RSO Context Alpha 0.9.3

Pre-release
Pre-release

Choose a tag to compare

@paulrus paulrus released this 25 Sep 04:14
· 19 commits to main since this release
330b0f1

An MCP host no longer needs a config edit to give RSO a new project, and two startup failures that a host could only see as a timeout now report themselves.

Install

Download RSOContextAlpha-0.9.3.zip, extract it, and run python -B install.py from the extracted folder. rso-context --version should report 0.9.3 and doctor should report ready: true. INSTALL.md covers Windows, Linux and macOS paths; QUICKSTART.md is the beginner walkthrough.

Requires Python 3.11 or newer, Git on PATH, and Python's standard-library SQLite with FTS5. The core CLI needs no pip packages, API key or network service.

sha256 of the attached ZIP: 7e6cd1c123febd0cf2f15b94e7094b8dde8769f5551cb5c1431acd289fbdb86a (62 files, 199,271 bytes).

Added

  • An MCP launch with no --root binds the directory the host started the server in, which is the project the user opened. One configured entry serves every project. This is a launch-time bound rather than run-time widening: a user profile or an unbounded home child is still refused, and --root still wins when given.
  • mcp --setup --client opencode writes that host's entry. OpenCode keys servers under mcp with a command list rather than mcpServers, and its config may be .jsonc, so the writer tolerates comments while leaving unrelated settings alone. --setup may now omit --root and use the current directory.
  • Generated host entries carry RSO_CONTEXT_HOME and, on Windows, SystemRoot with a two-entry system PATH. A host that replaces rather than augments the child environment otherwise spawns a server that can neither locate a ledger nor load winsock. The user's own PATH is deliberately not copied into a config file.
  • rso-context replay re-runs the queries and checks already recorded in the ledger against the current build and reports which packets changed, separating a moved corpus and edited sources from a real regression. It writes nothing.
  • benchmarks/budget_sweep.py sweeps --limit and --token-budget over recorded runs and prints a coverage-against-cost table. Advisory only.

Fixed

  • The stdio adapter no longer dies before answering initialize when the spawn environment carries no home directory. Path.home() raises RuntimeError, not OSError, so the existing handler never fired. A host that replaces the child environment produced exactly that and reported the silent exit as -32001 Request timed out.
  • Startup failures now emit a JSON-RPC error frame on stdout as well as the JSON on stderr: code -32099, null id, cause in the message. A client watching only stdout previously could not tell a crash from a hang.
  • The --db default no longer needs a home directory to build the argument parser. In a home-less environment that raised before the CLI could report it, giving a bare traceback and exit 1 even when --db was passed explicitly.
  • default_home() names RSO_CONTEXT_HOME and --db instead of surfacing pathlib's RuntimeError, and an unreadable working directory is reported as a launch-root failure rather than an uncaught OSError.
  • The user-profile root refusal no longer disappears when Path.home() is unavailable. It also reads USERPROFILE, HOME and HOMEDRIVE+HOMEPATH, so a partial environment keeps the guard.

Verified, and what is not

161 regression tests pass with one POSIX-only skip. GitHub Actions passed on Windows, Ubuntu and macOS with Python 3.11 and 3.12 for every merge in this release.

The startup changes were also checked live over stdio against the isolated runtime with a deliberately stripped environment, not only in unit tests: no home with --db starts; no home without --db exits 2 with the frame on stdout; a working directory set to the user profile still refuses.

Two limits stated plainly. The SystemRoot half of the original failure is environmental — a Windows child process without it cannot load winsock, and no code here changes that, which is why setup writes the variable into the host entry. Live OpenCode acceptance is unverified: the generated entry was checked by round-tripping the config file and starting the server with that entry's own command and environment, not by driving OpenCode. Native macOS live-agent acceptance also remains unverified. See VERIFICATION.md for the recorded scope.

This is an alpha pre-release.