Skip to content

SpaceApp setup 1.1.3

Choose a tag to compare

@oll4com oll4com released this 13 Oct 05:07

SpaceApp setup 1.1.3 lets the first OpenCode task run without stopping at a permission prompt, ships the current SpaceApp application, and makes the contributor path work on a fresh clone.

Fixes

  • No permission prompt on the first task. OpenCode's first run now authorizes only its own private scratch directory, and the bootstrap instructions send temporary files there. Before, a first task on macOS stopped at "Access external directory /tmp" until someone answered. Other paths outside the workspace still ask.
  • The Getting Started pane always starts. The default room project now resolves to the documented session directory inside the CLI container, so the OpenCode pane no longer exits with "chdir(2) failed". If the first-run free-model check fails, OpenCode starts anyway and explains how to pick a model.
  • Current application. The app is updated to the current SpaceApp source, including guided setup on every screen size and session sign-outs that survive restarts. The gateway's Antigravity sign-in uses an OAuth client you supply, as the API already did.

For contributors

  • npm run check works on a fresh clone, npm test runs the public test suite, and the offline smoke and dependency-boundary checks are included. README and CONTRIBUTING link only to files in this repository.

Install or update

npx --yes run-spaceapp@latest install
npx --yes run-spaceapp@latest update

Validation

  • Candidate tested on Linux, Windows 11 (signed-in desktop) and macOS Sonoma (the published commit adds only an export-tooling fix to it): fresh install with automatic browser opening, owner setup, a first native AI task on Big Pickle with no permission prompt, two OpenCode panes without out-of-memory kills, update from 1.1.2 and from 1.1.1, repair, stopped Docker, doctor --fix, and small/medium/large profiles.
  • Release workflow: https://github.com/oll4com/spaceapp/actions/runs/38341179443. The published package and images were verified against their attestations; the lab upgrade from the registry package was not repeated for this release.

Known limitations

  • Free models can change upstream at any time. If the selected free model stops responding, choose another model in OpenCode.
  • The core and browser images are larger than in 1.1.2 (about 1.0 GiB and 1.7 GiB) because of new application dependencies.