open-steamgate 0.7.2118 (stable, vscode.dev, manual Marketplace upload)

open-steamgate 0.7.2118 (stable): VS Code extension for desktop and vscode.dev. Upload this file to the Marketplace by hand; it replaces 0.7.2117.

• Commit: dfa44b0 (PR #835 head: the gear-gate launchpad logo split one element per line for BSP, and docs)
• Gear-gate icon and launchpad logo. Marked as a web extension (ExtensionKind workspace,ui,web; tag __web_extension). Browser entry, Fiori apps, media, lazy DuckDB-Wasm. No PreRelease property.
• Built locally with the marketplace profile, not through release.yml.

SHA-256 ef566fc43fde9b6c452fa816e2c8ee6e5243c4560845b0714763e3222c0d8388

Upload: Marketplace publisher oisee -> open-steamgate -> Update -> this .vsix.

open-steamgate 0.7.2117 (vscode.dev, manual Marketplace upload)

open-steamgate 0.7.2117: VS Code extension, desktop + vscode.dev (browser entry). Built for a manual Marketplace upload as the stable release.

• Commit: 2ee859c (PR #835 head: #828 + #833 on main, plus the gear-gate launchpad logo and docs)
• Gear-gate icon and launchpad logo (2026-10-20)
• Marked as a web extension: ExtensionKind workspace,ui,web, tag __web_extension
• Browser entry dist/web/extension.js, Fiori apps, media, lazy DuckDB-Wasm; packs: zork
• Stable (no PreRelease property)
• Built locally with the marketplace profile (OSD_VSIX_PROFILE=marketplace OSD_VSIX_WEB=1 OSD_VSIX_PRERELEASE=0, pinned transpiler fork), not through release.yml: its tagged tests did not run on this exact commit; CI on #835 is in progress.

SHA-256 64b19f953df0b1768e57f0676b14d50e0405a457a7f972f4282af03fdb1df550

Upload: Marketplace publisher page (oisee) -> open-steamgate -> Update -> this .vsix, or npx @vscode/vsce publish --packagePath open-steamgate-0.7.2117.vsix.

vscode-v0.7.2114

Start here

Pick the VSIX for VS Code, a self-contained Bun binary, a static OSGo binary, or a Compose file for Docker. SQLite is the default Compose database.

open-steamgate-0.7.2114.vsix

In VS Code 1.101 or newer, run Extensions: Install from VSIX... and select this file. Then run osd: Start (build + run this system) from the Command Palette. If asked whether to run an open-steamgate checkout, choose the bundled copy to use the packaged system. Its first start copies and builds the system; allow time for that build.

The bundled working copy lives at <globalStorageUri>/osd-home-<seedId>/; the database lives under <globalStorageUri>/osd-instance/<home-hash>/db/osd.sqlite. VS Code owns the actual global storage path. After an update, run osd: Remove old working copies to review and remove stale bundled copies.

osd-linux-x64

Download this file into any folder. Run mv osd-linux-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Measured Linux x64 executable size: 109.5 MB (decimal, local Bun 1.4.2 build).

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-linux-arm64

Download this file into any folder. Run mv osd-linux-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-arm64

Download this file into any folder. Run mv osd-darwin-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-x64

Download this file into any folder. Run mv osd-darwin-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-x64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-arm64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osgo-linux-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-linux-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-x64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-arm64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo...

vscode-v0.7.2109

Start here

Pick the VSIX for VS Code, a self-contained Bun binary, a static OSGo binary, or a Compose file for Docker. SQLite is the default Compose database.

open-steamgate-0.7.2109.vsix

In VS Code 1.101 or newer, run Extensions: Install from VSIX... and select this file. Then run osd: Start (build + run this system) from the Command Palette. If asked whether to run an open-steamgate checkout, choose the bundled copy to use the packaged system. Its first start copies and builds the system; allow time for that build.

The bundled working copy lives at <globalStorageUri>/osd-home-<seedId>/; the database lives under <globalStorageUri>/osd-instance/<home-hash>/db/osd.sqlite. VS Code owns the actual global storage path. After an update, run osd: Remove old working copies to review and remove stale bundled copies.

osd-linux-x64

Download this file into any folder. Run mv osd-linux-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Measured Linux x64 executable size: 109.5 MB (decimal, local Bun 1.4.2 build).

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-linux-arm64

Download this file into any folder. Run mv osd-linux-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-arm64

Download this file into any folder. Run mv osd-darwin-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-x64

Download this file into any folder. Run mv osd-darwin-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-x64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-arm64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osgo-linux-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-linux-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-x64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-arm64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo...

vscode-v0.7.1914

Start here

Pick the VSIX for VS Code, a self-contained Bun binary, a static OSGo binary, or a Compose file for Docker. SQLite is the default Compose database.

open-steamgate-0.7.1914.vsix

In VS Code 1.101 or newer, run Extensions: Install from VSIX... and select this file. Then run osd: Start (build + run this system) from the Command Palette. If asked whether to run an open-steamgate checkout, choose the bundled copy to use the packaged system. Its first start copies and builds the system; allow time for that build.

The bundled working copy lives at <globalStorageUri>/osd-home-<seedId>/; the database lives under <globalStorageUri>/osd-instance/<home-hash>/db/osd.sqlite. VS Code owns the actual global storage path. After an update, run osd: Remove old working copies to review and remove stale bundled copies.

osd-linux-x64

Download this file into any folder. Run mv osd-linux-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Measured Linux x64 executable size: 109.5 MB (decimal, local Bun 1.4.2 build).

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-linux-arm64

Download this file into any folder. Run mv osd-linux-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-arm64

Download this file into any folder. Run mv osd-darwin-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-x64

Download this file into any folder. Run mv osd-darwin-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-x64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-arm64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osgo-linux-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-linux-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-x64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-arm64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo...

vscode-stable-v0.7.1696

Start here

Pick the VSIX for VS Code, a self-contained Bun binary, a static OSGo binary, or a Compose file for Docker. SQLite is the default Compose database.

open-steamgate-0.7.1696.vsix

In VS Code 1.101 or newer, run Extensions: Install from VSIX... and select this file. Then run osd: Start (build + run this system) from the Command Palette. If asked whether to run an open-steamgate checkout, choose the bundled copy to use the packaged system. Its first start copies and builds the system; allow time for that build.

The bundled working copy lives at <globalStorageUri>/osd-home-<seedId>/; the database lives under <globalStorageUri>/osd-instance/<home-hash>/db/osd.sqlite. VS Code owns the actual global storage path. After an update, run osd: Remove old working copies to review and remove stale bundled copies.

osd-linux-x64

Download this file into any folder. Run mv osd-linux-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Measured Linux x64 executable size: 109.5 MB (decimal, local Bun 1.4.2 build).

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-linux-arm64

Download this file into any folder. Run mv osd-linux-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-arm64

Download this file into any folder. Run mv osd-darwin-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-x64

Download this file into any folder. Run mv osd-darwin-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-x64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-arm64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osgo-linux-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-linux-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-x64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-arm64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo...

vscode-stable-v0.7.1681

Start here

Pick the VSIX for VS Code, a self-contained Bun binary, a static OSGo binary, or a Compose file for Docker. SQLite is the default Compose database.

open-steamgate-0.7.1681.vsix

In VS Code 1.101 or newer, run Extensions: Install from VSIX... and select this file. Then run osd: Start (build + run this system) from the Command Palette. If asked whether to run an open-steamgate checkout, choose the bundled copy to use the packaged system. Its first start copies and builds the system; allow time for that build.

The bundled working copy lives at <globalStorageUri>/osd-home-<seedId>/; the database lives under <globalStorageUri>/osd-instance/<home-hash>/db/osd.sqlite. VS Code owns the actual global storage path. After an update, run osd: Remove old working copies to review and remove stale bundled copies.

osd-linux-x64

Download this file into any folder. Run mv osd-linux-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Measured Linux x64 executable size: 109.5 MB (decimal, local Bun 1.4.2 build).

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-linux-arm64

Download this file into any folder. Run mv osd-linux-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-arm64

Download this file into any folder. Run mv osd-darwin-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-x64

Download this file into any folder. Run mv osd-darwin-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-x64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-arm64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osgo-linux-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-linux-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-x64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-arm64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo...

vscode-v0.6.1650

What's new in 0.6.1650

Patch release after 0.6.1621.

Fixed: release binaries start outside a checkout. In 0.6.1621 the osd-* binaries could not open SQLite away from a source checkout, because the sql.js wasm was not inside the binary. The wasm is now embedded for all six targets (+655 KB). CI now runs each binary from an empty, isolated folder before release (#589).

VS Code

• The status bar shows one consistent state while the system starts, with a kernel findings count and a bounded handoff to the running system (#574).
• Jobs show readable summaries, and the raw log is behind an explicit action (#574).
• New OSD: Open sample for the bundled notebooks and the book's hello class (#574).
• ABAP-FS no longer auto-mounts in a single-folder window; that mount had made a host restart kill the system (#573).
• The launcher's on-demand inspector can no longer hang (#570).

ADT, from the clean-room acceptance kit

• Active and inactive source versions (T05, #576).
• Activation answers as an SAP system does, including forced activation (T11) (#572, #587).
• Request XML is read by expanded names and is refused before anything changes (T12, T13) (#582).
• The ABAP Unit object answers its first request in 0.3 s (was 5.5 s) (#583).
• Where-used is current after a warm swap (#571).

Runtime

• Open SQL LIKE is case-sensitive, as on A4H (#590).
• JOB_OPEN "database is locked" is fixed at its cause (#590).
• ABAP Unit RISK LEVEL follows the executable calls and denies the unknown by default (#569).
• OSG-JS buffers xstring SECTION writes: the ABAPiti QuickJS suite now finishes 9/9 on JS (#575).

Build and tests

• The generation hash no longer depends on where the tree sits (#581).
• Source snapshots are replaced by rename, never written in place (#579).
• Test-isolation guards (#578, #584, #585, #586).

---

Start here

Pick the VSIX for VS Code, a self-contained Bun binary, a static OSGo binary, or a Compose file for Docker. SQLite is the default Compose database.

open-steamgate-0.6.1650.vsix

In VS Code 1.101 or newer, run Extensions: Install from VSIX... and select this file. Then run osd: Start (build + run this system) from the Command Palette. If asked whether to run an open-steamgate checkout, choose the bundled copy to use the packaged system. Its first start copies and builds the system; allow time for that build.

The bundled working copy lives at <globalStorageUri>/osd-home-<seedId>/; the database lives under <globalStorageUri>/osd-instance/<home-hash>/db/osd.sqlite. VS Code owns the actual global storage path. After an update, run osd: Remove old working copies to review and remove stale bundled copies.

osd-linux-x64

Download this file into any folder. Run mv osd-linux-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Measured Linux x64 executable size: 109.5 MB (decimal, local Bun 1.4.2 build).

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-linux-arm64

Download this file into any folder. Run mv osd-linux-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-arm64

Download this file into any folder. Run mv osd-darwin-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-x64

Download this file into any folder. Run mv osd-darwin-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-x64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-arm64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osgo-linux-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-linux-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run `./osgo -ver...

vscode-stable-v0.7.1673

Start here

Pick the VSIX for VS Code, a self-contained Bun binary, a static OSGo binary, or a Compose file for Docker. SQLite is the default Compose database.

open-steamgate-0.7.1673.vsix

In VS Code 1.101 or newer, run Extensions: Install from VSIX... and select this file. Then run osd: Start (build + run this system) from the Command Palette. If asked whether to run an open-steamgate checkout, choose the bundled copy to use the packaged system. Its first start copies and builds the system; allow time for that build.

The bundled working copy lives at <globalStorageUri>/osd-home-<seedId>/; the database lives under <globalStorageUri>/osd-instance/<home-hash>/db/osd.sqlite. VS Code owns the actual global storage path. After an update, run osd: Remove old working copies to review and remove stale bundled copies.

osd-linux-x64

Download this file into any folder. Run mv osd-linux-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Measured Linux x64 executable size: 109.5 MB (decimal, local Bun 1.4.2 build).

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-linux-arm64

Download this file into any folder. Run mv osd-linux-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-arm64

Download this file into any folder. Run mv osd-darwin-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-x64

Download this file into any folder. Run mv osd-darwin-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-x64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-arm64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osgo-linux-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-linux-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-darwin-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-x64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-windows-arm64.exe

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo.exe, then run .\osgo.exe -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run .\osgo.exe -version for the tag and commit. OSGo...

vscode-stable-v0.7.1671

open-steamgate 0.7 (stable)

The 0.7 line is about a first run that works on a clean machine and makes sense to a newcomer. This is a stable release: the VS Code Marketplace serves it on the stable channel.

Breaking for consumers

• The output channels are renamed: osd → OSD, osd console → OSD: Console, osd system → OSD: System log, and OSD jobs plus OSD jobs raw log → OSD: Jobs, with the raw log behind an explicit action (#608).
• F8 / ▷ never run ABAP Unit. On a class with IF_OO_ADT_CLASSRUN they run the classrun; on a report they run the report. Tests run only through Ctrl+Shift+F10, the beaker button, or the Test Explorer (#608).

What's new since 0.6.1666

• The editor title bar has Check and Activate buttons (a check mark and a match). Their results also appear in OSD: Console.
• F9 warns when the saved source is not activated yet.
• Test Explorer runs always end. No more spinner that never stops.
• Debugging: no debug session starts at system start. The first .abap breakpoint shows a one-time note saying that osd needs no launch configuration. The README has a "What connects to what" section (#608).
• A bare-system VSIX smoke checks every tag: a clean Ubuntu with no node or git, the real VS Code, then install, Start, $metadata, Stop, plus a layer that must fail loudly (#609).
• The ADT clean-room acceptance: editing sessions survive a cold publication (T15, #603), and locks answer as an SAP system does (T03/T04, #601).
• CI: six balanced shards, and runs on main are never cancelled (#602). The release has a stable channel (#606).

Known issues, fixed in the next 0.7.x patch

• The first answer after osd: Start can take about 13 s while the warm cache primes, so the first F9 right after start may report "fetch failed". Wait a moment, or press F9 again. The fix is #613.
• A workspace layer written for a newer osd fails with many check_syntax lines instead of one clear "needs osd ≥ x" message. The fix is on feat/layer-requires-osd-version.

---

Start here

Pick the VSIX for VS Code, a self-contained Bun binary, a static OSGo binary, or a Compose file for Docker. SQLite is the default Compose database.

open-steamgate-0.7.1671.vsix

In VS Code 1.101 or newer, run Extensions: Install from VSIX... and select this file. Then run osd: Start (build + run this system) from the Command Palette. If asked whether to run an open-steamgate checkout, choose the bundled copy to use the packaged system. Its first start copies and builds the system; allow time for that build.

The bundled working copy lives at <globalStorageUri>/osd-home-<seedId>/; the database lives under <globalStorageUri>/osd-instance/<home-hash>/db/osd.sqlite. VS Code owns the actual global storage path. After an update, run osd: Remove old working copies to review and remove stale bundled copies.

osd-linux-x64

Download this file into any folder. Run mv osd-linux-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Measured Linux x64 executable size: 109.5 MB (decimal, local Bun 1.4.2 build).

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-linux-arm64

Download this file into any folder. Run mv osd-linux-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-arm64

Download this file into any folder. Run mv osd-darwin-arm64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-darwin-x64

Download this file into any folder. Run mv osd-darwin-x64 osd && chmod +x osd && ./osd up; run ./osd doctor to check the bundled runtime.

If macOS Gatekeeper quarantines the download, run xattr -d com.apple.quarantine osd after checking its checksum.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-x64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osd-windows-arm64.exe

Download this file into any folder, rename it to osd.exe, and run .\osd.exe up in PowerShell. Run .\osd.exe doctor to check the bundled runtime.

Open http://localhost:3030/. On first start outside a checkout, the binary copies its bundled system into a content-keyed osd-home-<seedId> under the user data directory: $XDG_DATA_HOME/open-steamgate or ~/.local/share/open-steamgate on Linux, ~/Library/Application Support/open-steamgate on macOS, %LOCALAPPDATA%\open-steamgate on Windows. Later releases keep earlier working copies and user edits. The SQLite database lives in that working copy under .local/db/.
To override an ABAP object, copy its file from the materialized home's src/ or packs/ into your own folder, retaining its abapGit filename, then run osd up --layer <folder>. Repeat --layer for more folders, or set OSD_LAYERS to a platform path-list. Later layers win, and the build logs each override. A binary started inside a source checkout uses that checkout directly.

osgo-linux-x64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then run ./osgo -home <data-directory> -port 3095. Check http://127.0.0.1:3095/health for readiness. A new home directory starts a newly seeded database; -db <file> overrides its database path. Run ./osgo -version for the tag and commit. OSGo does not serve ADT yet. See docs/osgo-release.md for CI usage.

osgo-linux-arm64

OSGo is a single static Go executable with SQLite built in. Download and verify this file, rename it to osgo, then...