Skip to content

Extensions: install components, hooks, Moonlight apps and dashboard tabs from GitHub - #70

Merged
mlopezsegura merged 2 commits into
masterfrom
feature/extensions
Nov 17, 2026
Merged

mlopezsegura merged 2 commits into
masterfrom
feature/extensions

Conversation

@mlopezsegura

Copy link
Copy Markdown
Collaborator

Adds an Extensions tab to the dashboard. Extensions are installed from a GitHub link (repository, folder or release tag) or from catalogs, and can:

  • Components: install, detect and uninstall something on Windows with PowerShell scripts run as SYSTEM. If the install script fails, the previous package is restored; exit code 3010 asks for a restart.
  • Hooks: run scripts when sessions or seats start and stop, as SYSTEM or as the session's user.
  • Moonlight apps: add entries to each session's Sunshine apps.json, marked with osms-extension.
  • Dashboard tabs: a static page in a sandboxed iframe with an opaque origin, served under /ext/<id>/<token>/, with a read-only postMessage context.

Trust model

  • Nothing is installed straight from a link. The package is downloaded and validated first, and the dashboard shows what it does, who made it, the commit and the SHA-256.
  • The user has to tick "I trust ", and only that exact package is installed.
  • Catalogs (osms-catalog.json) can pin a ref and a hash.
  • Updates show the new version and ask for confirmation again.
  • Downloads only go to GitHub hosts (redirects are checked), with size limits and zip-slip checks.
  • The extensions folder is writable only by SYSTEM and Administrators.

Catalogs: the official catalog OpenstreamCo/osms-extensions is added once by default and can be removed. Users can add others.

Docs: author documentation is in docs/extensions.md.

Tests

  • 44 new unit tests: link parsing, manifest and catalog validation, safe extraction, app merging, and the full preview → install → apps → uninstall flow against a fake GitHub, including a catalog hash mismatch.
  • i18n tests: the 22 languages are updated.
  • The dashboard was checked in the browser with fixtures.

Not yet tested on a real service: installing real extensions, running hooks in real sessions, and apps appearing in Moonlight.

🤖 Generated with Claude Code

mlopezsegura and others added 2 commits November 16, 2026 23:18
…abs from GitHub

- Install from a GitHub link (repo, folder, release tag) or from catalogs (osms-catalog.json);
  the official OpenstreamCo/osms-extensions catalog is added once by default
- Preview first: download, validate osms-extension.json, show capabilities, commit and SHA-256;
  install only that exact package after the user confirms (catalogs can pin ref and hash)
- Components: install/uninstall/detect PowerShell scripts as SYSTEM, rollback if install fails,
  exit code 3010 asks for a restart
- Hooks on session and seat start/stop, as SYSTEM or as the session's user
- Apps merged into each session's Sunshine apps.json, marked with osms-extension
- Dashboard tabs served under /ext/<id>/<token>/ in a sandboxed iframe (opaque origin),
  with a read-only postMessage context
- Extensions folder writable only by SYSTEM and Administrators
- docs/extensions.md for authors; unit tests for parsing, packages, apps and the full flow

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ut as 504

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mlopezsegura
mlopezsegura merged commit 3b3392c into master Nov 17, 2026
2 checks passed
@mlopezsegura
mlopezsegura deleted the feature/extensions branch November 17, 2026 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant