Skip to content

Releases: Zetsu4i/vscode

Dev build 39 (tauri-rewrite)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 10 Sep 19:06
d9637b3

Automated build of 4b956651ba75dc812f6020ce92b84fa2383336b5 on tauri-rewrite.

  • Windows: *-setup.exe (NSIS)

VSTauri (by Mouri Younes) — the original VS Code workbench
in a Tauri v2 native shell (WebView2, vscode-file://
protocol). No Electron, no HTTP server, no vscode-web.

This build ships: full file-system + watcher services, the
integrated terminal backend (ConPTY) with the xterm renderer
addons, editor state persistence + hot exit (window bounds,
workspace session, unsaved-content backups), multi-window
(agents window, window.open popups), the theme-aware
"Starting…" boot splash, DPAPI-encrypted secret storage, the
Node.js sidecar runtime (extension host bring-up) and the
copilot extension with the BYOK AI providers (custom OpenAI
base URL + key; models list from /v1/models; no
GitHub/Google account required).

Diagnostics: vstauri.log + ipc-calls.jsonl in
%APPDATA%\VSTauri\logs. Remaining work is tracked in
ROADMAP.md (extension host bring-up, search via ext host,
debug/tasks, parity audit).

Dev build 37 (tauri-rewrite)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 10 Sep 07:36
d9637b3

Automated build of 05baf370f963de99003b4ee7d1cc32a37cdc7334 on tauri-rewrite.

  • Windows: *-setup.exe (NSIS)

VSTauri (by Mouri Younes) — the original VS Code workbench
in a Tauri v2 native shell (WebView2, vscode-file://
protocol). No Electron, no HTTP server, no vscode-web.

This build ships: full file-system + watcher services, the
integrated terminal backend (ConPTY) with the xterm renderer
addons, editor state persistence + hot exit (window bounds,
workspace session, unsaved-content backups), multi-window
(agents window, window.open popups), the theme-aware
"Starting…" boot splash, DPAPI-encrypted secret storage, the
Node.js sidecar runtime (extension host bring-up) and the
copilot extension with the BYOK AI providers (custom OpenAI
base URL + key; models list from /v1/models; no
GitHub/Google account required).

Diagnostics: vstauri.log + ipc-calls.jsonl in
%APPDATA%\VSTauri\logs. Remaining work is tracked in
ROADMAP.md (extension host bring-up, search via ext host,
debug/tasks, parity audit).

Dev build 36 (tauri-rewrite)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 09 Sep 18:50
d9637b3

Automated build of 5a158f287ca6e32a66e485822170bcc1eef1b64a on tauri-rewrite.

  • Windows: *-setup.exe (NSIS)

VSTauri (by Mouri Younes) — the original VS Code workbench
in a Tauri v2 native shell (WebView2, vscode-file://
protocol). No Electron, no HTTP server, no vscode-web.

This build ships: full file-system + watcher services, the
integrated terminal backend (ConPTY) with the xterm renderer
addons, editor state persistence + hot exit (window bounds,
workspace session, unsaved-content backups), multi-window
(agents window, window.open popups), the theme-aware
"Starting…" boot splash, DPAPI-encrypted secret storage, the
Node.js sidecar runtime (extension host bring-up) and the
copilot extension with the BYOK AI providers (custom OpenAI
base URL + key; models list from /v1/models; no
GitHub/Google account required).

Diagnostics: vstauri.log + ipc-calls.jsonl in
%APPDATA%\VSTauri\logs. Remaining work is tracked in
ROADMAP.md (extension host bring-up, search via ext host,
debug/tasks, parity audit).

Dev build 34 (tauri-rewrite)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 08 Sep 08:33
d9637b3

Automated build of 52aba75fa4eecec97ccd01fe4f2484f8d16dd186 on tauri-rewrite.

  • Windows: *-setup.exe (NSIS)

Phase 1 shell: the original VS Code workbench renderer served
natively through the Tauri v2 vscode-file:// custom protocol
(WebView2). No Electron, no HTTP server, no vscode-web. The
renderer boots against a native window configuration and an
instrumented IPC bridge (ipc-calls.jsonl + vstauri.log in
%APPDATA%\VSTauri\logs) that feeds the next phases.

NOTE: Phase 1 scope is "workbench renders". Terminal, file
dialogs, storage and extensions land in later phases (see
ROADMAP.md); their IPC channels currently resolve to null and
are logged.

Dev build 31 (tauri-rewrite)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 07 Sep 20:43
d9637b3

Automated build of fe8813e0da95f75ae8a8d53472e3e79871bc5373 on tauri-rewrite.

  • Windows: *-setup.exe (NSIS)

Phase 1 shell: the original VS Code workbench renderer served
natively through the Tauri v2 vscode-file:// custom protocol
(WebView2). No Electron, no HTTP server, no vscode-web. The
renderer boots against a native window configuration and an
instrumented IPC bridge (ipc-calls.jsonl + vstauri.log in
%APPDATA%\VSTauri\logs) that feeds the next phases.

NOTE: Phase 1 scope is "workbench renders". Terminal, file
dialogs, storage and extensions land in later phases (see
ROADMAP.md); their IPC channels currently resolve to null and
are logged.

Dev build 20 (tauri-rewrite)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 05 Sep 22:00
d9637b3

Automated build of 8947d1a78a317ff256f73fe75f9b937bae56bac5 on tauri-rewrite.

  • Windows: *-setup.exe (NSIS)

Phase 1 shell: the original VS Code workbench renderer served
natively through the Tauri v2 vscode-file:// custom protocol
(WebView2). No Electron, no HTTP server, no vscode-web. The
renderer boots against a native window configuration and an
instrumented IPC bridge (ipc-calls.jsonl + vstauri.log in
%APPDATA%\VSTauri\logs) that feeds the next phases.

NOTE: Phase 1 scope is "workbench renders". Terminal, file
dialogs, storage and extensions land in later phases (see
ROADMAP.md); their IPC channels currently resolve to null and
are logged.

Dev build 19 (tauri-rewrite)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 05 Sep 20:16
d9637b3

Automated build of c44ac9a1669c37159f72bc61da3f5b08936c5f1a on tauri-rewrite.

  • Windows: *-setup.exe (NSIS)

Phase 1 shell: the original VS Code workbench renderer served
natively through the Tauri v2 vscode-file:// custom protocol
(WebView2). No Electron, no HTTP server, no vscode-web. The
renderer boots against a native window configuration and an
instrumented IPC bridge (ipc-calls.jsonl + vstauri.log in
%APPDATA%\VSTauri\logs) that feeds the next phases.

NOTE: Phase 1 scope is "workbench renders". Terminal, file
dialogs, storage and extensions land in later phases (see
ROADMAP.md); their IPC channels currently resolve to null and
are logged.

Dev build 1 (upstream 1.136.1)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 05 Sep 00:34

Automated build of df8ddcc3cb22a543ff187f779bc5a2e49a5698d0 (upstream 1.136.1).

  • Windows: *-setup.exe (NSIS)

The bundled UI is the pristine Visual Studio Code web workbench
served by the Rust backbone — no Electron, no Node runtime.

Dev build 5 (upstream 1.136.1)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 04 Sep 23:12
167a0e8

Automated build of 3557b782ce2bcf73a6308d281186697848f17c25.

  • Windows: *-setup.exe (NSIS)
  • Linux: *.deb, *.AppImage

The bundled UI is the pristine Visual Studio Code web workbench
(upstream 1.136.1) served by the Rust backbone.

Dev build 4 (upstream 1.136.1)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 05 Sep 01:26
a44adf7

Automated build of af36f7cd806af29dbcaa5f24af0a086ba7c5331f (upstream 1.136.1).

  • Windows: *-setup.exe (NSIS)

The bundled UI is the pristine Visual Studio Code web workbench
served by the Rust backbone — no Electron, no Node runtime.