v2.1.4

DevHub 2.1.4

This Linux desktop integration update restores DevHub's title and icon identity in Wayland application switchers.

Highlights

Linux Wayland Integration

• DevHub now explicitly publishes its DevHub window title and devhub-gpui application ID after GPUI creates the native Linux window.
• This works around GPUI 0.2.2 dropping the initial title on Wayland, allowing KDE and other compositors to render the correct Alt+Tab title and resolve the installed AppImage icon.

DevHub MCP Server (devhub-mcp)

A read-only MCP server exposes your DevHub catalog as AI-editor tools. The in-app server listens on 127.0.0.1:47821, requires bearer authentication, and provides 9 tools:

Tool	Description
list_projects	Catalog of all projects with metadata
project_overview	README, layout, git state, recent commit, todos
list_tree	Gitignore-aware file tree (depth/hidden controls)
read_file	Read line ranges of text files with editor-navigable paths
search_content	Full-text search across project files
git_status	Live branch, upstream, ahead/behind, changed-file stats
git_diff	Unified diffs, optionally filtered by path
git_log	Commit history pages
list_todos	Per-project DevHub todo items

How to Use

There are two ways to connect DevHub to your editor:

Option A: Standalone (stdio): use the installed MCP executable, or build it with cargo build --release -p devhub-mcp, and add it to Zed's context_servers settings:

{
  "context_servers": {
    "devhub-mcp": {
      "command": "/path/to/devhub-mcp",
      "args": [],
      "env": {}
    }
  }
}

Packaged stdio commands are:

• Windows: C:\Users\<you>\AppData\Local\Programs\DevHub\devhub-mcp.exe
• Linux: /path/to/DevHub-2.1.4-x86_64.AppImage with
  "args": ["--mcp-stdio"]
• macOS: /Applications/DevHub MCP.app/Contents/MacOS/devhub-mcp

Option B: DevHub HTTP (Streamable HTTP): toggle the MCP switch inside the DevHub desktop app, then point your editor to the running server:

{
  "context_servers": {
    "devhub-mcp": {
      "url": "http://127.0.0.1:47821/mcp",
      "headers": {
        "Authorization": "Bearer <token-from-devhub-settings>"
      }
    }
  }
}

DevHub generates a 256-bit HTTP token on first start. Copy or regenerate it from Settings. For tailnet access, run tailscale serve --bg http://127.0.0.1:47821, use the resulting HTTPS URL ending in /mcp, and send the same bearer header. Reverse-proxy Host headers are accepted; direct LAN binding is intentionally disabled. HTTP tool calls use stateless Streamable HTTP JSON responses, avoiding long-lived MCP sessions through the proxy.

Todo List

Lightweight per-project todo tracking accessible via devhub-mcp list_todos and the in-editor todo panel.

Artifacts

• Windows x64: DevHub-Setup-2.1.4-x64.exe
• Linux x64: DevHub-2.1.4-x86_64.AppImage
• macOS Apple Silicon: DevHub-2.1.4-arm64.dmg

Every package contains both executable identities, README.md, RELEASE.md, and LICENSE. Platform integration remains native and small:

• The Windows installer installs both .exe files, each with the DevHub PE icon, plus Start menu and optional desktop shortcuts for the GUI.
• The Linux AppImage is the visible branded file and includes both ELF executables, XDG desktop metadata, and .DirIcon. Pass --mcp-stdio to dispatch directly to the companion server.
• The macOS disk image contains DevHub.app and DevHub MCP.app, both with matching ICNS resources. The latter exposes the stdio executable inside its normal app-bundle path.

Raw Linux ELF and macOS Mach-O files do not embed file-manager icon resources. Branding belongs to the AppImage, desktop entry, and .app bundle rather than to an extracted internal command file.

SHA-256 hashes are published in checksums.txt.

Requirements

• Git for repository workflows.
• OpenSSH configuration and key-based authentication for SSH projects.
• A POSIX remote environment with standard command-line tools, or a Windows SSH host with Git for Windows installed.
• Linux requires a glibc-based system and a Vulkan-capable desktop stack.
• Release automation supports Authenticode signing on Windows and Developer ID signing plus notarization on macOS when maintainer credentials are configured. Otherwise Windows artifacts are unsigned and macOS bundles use ad hoc signing.

Maintainers configure Windows signing with the WINDOWS_CERTIFICATE_BASE64 and
WINDOWS_CERTIFICATE_PASSWORD repository secrets. macOS uses
MACOS_CERTIFICATE_BASE64, MACOS_CERTIFICATE_PASSWORD, APPLE_ID,
APPLE_TEAM_ID, and APPLE_APP_PASSWORD.

Before running a package, compare its SHA-256 hash with checksums.txt.

v2.1.3

DevHub 2.1.3

This maintenance update closes cross-platform MCP reliability gaps while preserving the branded native packages introduced in 2.1.2.

Highlights

Reliability

• MCP file paths now reject Windows drive paths, UNC paths, and backslash traversal on every server platform, including when a Linux DevHub instance serves Windows projects over SSH.
• Remote file reads identify binary content before UTF-8 decoding, so binary files return the intended refusal instead of a misleading SSH encoding error.
• Windows SSH failures suppress PowerShell progress/CLIXML framing while preserving the useful error message.
• The HTTP server is covered by concurrent authenticated requests, repeated start/stop cycles, tailnet Host headers, rejected credentials, and real-client reconnect tests.

DevHub MCP Server (devhub-mcp)

A read-only MCP server exposes your DevHub catalog as AI-editor tools. The in-app server listens on 127.0.0.1:47821, requires bearer authentication, and provides 9 tools:

Tool	Description
list_projects	Catalog of all projects with metadata
project_overview	README, layout, git state, recent commit, todos
list_tree	Gitignore-aware file tree (depth/hidden controls)
read_file	Read line ranges of text files with editor-navigable paths
search_content	Full-text search across project files
git_status	Live branch, upstream, ahead/behind, changed-file stats
git_diff	Unified diffs, optionally filtered by path
git_log	Commit history pages
list_todos	Per-project DevHub todo items

How to Use

There are two ways to connect DevHub to your editor:

Option A: Standalone (stdio): use the installed MCP executable, or build it with cargo build --release -p devhub-mcp, and add it to Zed's context_servers settings:

{
  "context_servers": {
    "devhub-mcp": {
      "command": "/path/to/devhub-mcp",
      "args": [],
      "env": {}
    }
  }
}

Packaged stdio commands are:

• Windows: C:\Users\<you>\AppData\Local\Programs\DevHub\devhub-mcp.exe
• Linux: /path/to/DevHub-2.1.3-x86_64.AppImage with
  "args": ["--mcp-stdio"]
• macOS: /Applications/DevHub MCP.app/Contents/MacOS/devhub-mcp

Option B: DevHub HTTP (Streamable HTTP): toggle the MCP switch inside the DevHub desktop app, then point your editor to the running server:

{
  "context_servers": {
    "devhub-mcp": {
      "url": "http://127.0.0.1:47821/mcp",
      "headers": {
        "Authorization": "Bearer <token-from-devhub-settings>"
      }
    }
  }
}

DevHub generates a 256-bit HTTP token on first start. Copy or regenerate it from Settings. For tailnet access, run tailscale serve --bg http://127.0.0.1:47821, use the resulting HTTPS URL ending in /mcp, and send the same bearer header. Reverse-proxy Host headers are accepted; direct LAN binding is intentionally disabled. HTTP tool calls use stateless Streamable HTTP JSON responses, avoiding long-lived MCP sessions through the proxy.

Todo List

Lightweight per-project todo tracking accessible via devhub-mcp list_todos and the in-editor todo panel.

Artifacts

• Windows x64: DevHub-Setup-2.1.3-x64.exe
• Linux x64: DevHub-2.1.3-x86_64.AppImage
• macOS Apple Silicon: DevHub-2.1.3-arm64.dmg

Every package contains both executable identities, README.md, RELEASE.md, and LICENSE. Platform integration remains native and small:

• The Windows installer installs both .exe files, each with the DevHub PE icon, plus Start menu and optional desktop shortcuts for the GUI.
• The Linux AppImage is the visible branded file and includes both ELF executables, XDG desktop metadata, and .DirIcon. Pass --mcp-stdio to dispatch directly to the companion server.
• The macOS disk image contains DevHub.app and DevHub MCP.app, both with matching ICNS resources. The latter exposes the stdio executable inside its normal app-bundle path.

Raw Linux ELF and macOS Mach-O files do not embed file-manager icon resources. Branding belongs to the AppImage, desktop entry, and .app bundle rather than to an extracted internal command file.

SHA-256 hashes are published in checksums.txt.

Requirements

• Git for repository workflows.
• OpenSSH configuration and key-based authentication for SSH projects.
• A POSIX remote environment with standard command-line tools, or a Windows SSH host with Git for Windows installed.
• Linux requires a glibc-based system and a Vulkan-capable desktop stack.
• Release automation supports Authenticode signing on Windows and Developer ID signing plus notarization on macOS when maintainer credentials are configured. Otherwise Windows artifacts are unsigned and macOS bundles use ad hoc signing.

Maintainers configure Windows signing with the WINDOWS_CERTIFICATE_BASE64 and
WINDOWS_CERTIFICATE_PASSWORD repository secrets. macOS uses
MACOS_CERTIFICATE_BASE64, MACOS_CERTIFICATE_PASSWORD, APPLE_ID,
APPLE_TEAM_ID, and APPLE_APP_PASSWORD.

Before running a package, compare its SHA-256 hash with checksums.txt.

v2.1.2

DevHub 2.1.2

This maintenance update hardens project identity, SSH platform behavior, process ownership, and MCP exposure, then replaces raw release archives with branded native packages.

Highlights

DevHub MCP Server (devhub-mcp)

A read-only MCP server exposes your DevHub catalog as AI-editor tools. The in-app server listens on 127.0.0.1:47821, requires bearer authentication, and provides 9 tools:

Tool	Description
list_projects	Catalog of all projects with metadata
project_overview	README, layout, git state, recent commit, todos
list_tree	Gitignore-aware file tree (depth/hidden controls)
read_file	Read line ranges of text files with editor-navigable paths
search_content	Full-text search across project files
git_status	Live branch, upstream, ahead/behind, changed-file stats
git_diff	Unified diffs, optionally filtered by path
git_log	Commit history pages
list_todos	Per-project DevHub todo items

How to Use

There are two ways to connect DevHub to your editor:

Option A: Standalone (stdio): use the installed MCP executable, or build it with cargo build --release -p devhub-mcp, and add it to Zed's context_servers settings:

{
  "context_servers": {
    "devhub-mcp": {
      "command": "/path/to/devhub-mcp",
      "args": [],
      "env": {}
    }
  }
}

Packaged stdio commands are:

• Windows: C:\Users\<you>\AppData\Local\Programs\DevHub\devhub-mcp.exe
• Linux: /path/to/DevHub-2.1.2-x86_64.AppImage with
  "args": ["--mcp-stdio"]
• macOS: /Applications/DevHub MCP.app/Contents/MacOS/devhub-mcp

Option B: DevHub HTTP (Streamable HTTP): toggle the MCP switch inside the DevHub desktop app, then point your editor to the running server:

{
  "context_servers": {
    "devhub-mcp": {
      "url": "http://127.0.0.1:47821/mcp",
      "headers": {
        "Authorization": "Bearer <token-from-devhub-settings>"
      }
    }
  }
}

DevHub generates a 256-bit HTTP token on first start. Copy or regenerate it from Settings. For tailnet access, run tailscale serve --bg http://127.0.0.1:47821, use the resulting HTTPS URL ending in /mcp, and send the same bearer header. Reverse-proxy Host headers are accepted; direct LAN binding is intentionally disabled. HTTP tool calls use stateless Streamable HTTP JSON responses, avoiding long-lived MCP sessions through the proxy.

Todo List

Lightweight per-project todo tracking accessible via devhub-mcp list_todos and the in-editor todo panel.

Artifacts

• Windows x64: DevHub-Setup-2.1.2-x64.exe
• Linux x64: DevHub-2.1.2-x86_64.AppImage
• macOS Apple Silicon: DevHub-2.1.2-arm64.dmg

Every package contains both executable identities, README.md, RELEASE.md, and LICENSE. Platform integration remains native and small:

• The Windows installer installs both .exe files, each with the DevHub PE icon, plus Start menu and optional desktop shortcuts for the GUI.
• The Linux AppImage is the visible branded file and includes both ELF executables, XDG desktop metadata, and .DirIcon. Pass --mcp-stdio to dispatch directly to the companion server.
• The macOS disk image contains DevHub.app and DevHub MCP.app, both with matching ICNS resources. The latter exposes the stdio executable inside its normal app-bundle path.

Raw Linux ELF and macOS Mach-O files do not embed file-manager icon resources. Branding belongs to the AppImage, desktop entry, and .app bundle rather than to an extracted internal command file.

SHA-256 hashes are published in checksums.txt.

Requirements

• Git for repository workflows.
• OpenSSH configuration and key-based authentication for SSH projects.
• A POSIX remote environment with standard command-line tools, or a Windows SSH host with Git for Windows installed.
• Linux requires a glibc-based system and a Vulkan-capable desktop stack.
• Release automation supports Authenticode signing on Windows and Developer ID signing plus notarization on macOS when maintainer credentials are configured. Otherwise Windows artifacts are unsigned and macOS bundles use ad hoc signing.

Maintainers configure Windows signing with the WINDOWS_CERTIFICATE_BASE64 and
WINDOWS_CERTIFICATE_PASSWORD repository secrets. macOS uses
MACOS_CERTIFICATE_BASE64, MACOS_CERTIFICATE_PASSWORD, APPLE_ID,
APPLE_TEAM_ID, and APPLE_APP_PASSWORD.

Before running a package, compare its SHA-256 hash with checksums.txt.

v2.1.1

DevHub 2.1.1

This maintenance update hardens project identity, SSH platform behavior, process ownership, and MCP exposure without expanding DevHub's product scope.

Highlights

DevHub MCP Server (devhub-mcp)

A read-only MCP server exposes your DevHub catalog as AI-editor tools. The in-app server listens on 127.0.0.1:47821, requires bearer authentication, and provides 9 tools:

Tool	Description
list_projects	Catalog of all projects with metadata
project_overview	README, layout, git state, recent commit, todos
list_tree	Gitignore-aware file tree (depth/hidden controls)
read_file	Read line ranges of text files with editor-navigable paths
search_content	Full-text search across project files
git_status	Live branch, upstream, ahead/behind, changed-file stats
git_diff	Unified diffs, optionally filtered by path
git_log	Commit history pages
list_todos	Per-project DevHub todo items

How to Use

There are two ways to connect DevHub to your editor:

Option A: Standalone (stdio): build the binary with cargo build --release -p devhub-mcp and add it as a local MCP server in your editor:

{
  "devhub-mcp": {
    "enabled": true,
    "remote": false,
    "command": "/path/to/executable",
    "args": [],
    "timeout": 30
  }
}

Option B: DevHub HTTP (Streamable HTTP): toggle the MCP switch inside the DevHub desktop app, then point your editor to the running server:

{
  "devhub-mcp": {
    "type": "remote",
    "url": "http://127.0.0.1:47821/mcp",
    "headers": {
      "Authorization": "Bearer <token-from-devhub-settings>"
    }
  }
}

DevHub generates a 256-bit HTTP token on first start. Copy or regenerate it from Settings. For tailnet access, run tailscale serve --bg http://127.0.0.1:47821, use the resulting HTTPS URL ending in /mcp, and send the same bearer header. Reverse-proxy Host headers are accepted; direct LAN binding is intentionally disabled.

Todo List

Lightweight per-project todo tracking accessible via devhub-mcp list_todos and the in-editor todo panel.

Artifacts

• Windows x64
• Linux x64
• macOS Apple Silicon

Every archive contains both executable identities, README.md, RELEASE.md, and LICENSE. Platform integration is deliberately native and small:

• Windows embeds the DevHub icon in both .exe files.
• Linux includes XDG desktop metadata and named SVG icons for both executables. The MCP entry is NoDisplay because clients launch it over stdio.
• macOS includes ad hoc signed DevHub.app and DevHub-MCP.app bundles with matching icons. Top-level command symlinks preserve direct terminal and MCP-client execution.

SHA-256 hashes are published in checksums.txt.

Requirements

• Git for repository workflows.
• OpenSSH configuration and key-based authentication for SSH projects.
• A POSIX remote environment with standard command-line tools, or a Windows SSH host with Git for Windows installed.
• Linux requires a glibc-based system and a Vulkan-capable desktop stack.
• The macOS bundles are ad hoc signed for bundle integrity but are not Developer ID signed or notarized.

Before running an archive, compare its SHA-256 hash with checksums.txt.

v2.1.0

DevHub 2.0

This update focuses on removal of the prior ai-harness scaffolding in favor of a focused, practical tool.

Highlights

DevHub MCP Server (devhub-mcp)

A new read-only MCP server exposing your entire DevHub catalog as AI-editor tools. Runs locally at 127.0.0.1:47821 and provides 9 tools:

Tool	Description
list_projects	Catalog of all projects with metadata
project_overview	README, layout, git state, recent commit, todos
list_tree	Gitignore-aware file tree (depth/hidden controls)
read_file	Read line ranges of text files with editor-navigable paths
search_content	Full-text search across project files
git_status	Live branch, upstream, ahead/behind, changed-file stats
git_diff	Unified diffs, optionally filtered by path
git_log	Commit history pages
list_todos	Per-project DevHub todo items

How to Use

There are two ways to connect DevHub to your editor:

Option A: Standalone (stdio): build the binary with cargo build --release -p devhub-mcp and add it as a local MCP server in your editor:

"devhub-mcp": {
      "enabled": true,
      "remote": false,
      "command": "/path/to/executable",
      "args": [],
      "timeout": 30
    },

Option B: DevHub HTTP (Streamable HTTP): toggle the MCP switch inside the DevHub desktop app, then point your editor to the running server:

"devhub-mcp": {
      "type": "remote",
      "url": "http://127.0.0.1:47821/mcp"
    }
  }

Todo List

Lightweight per-project todo tracking accessible via devhub-mcp list_todos and the in-editor todo panel.

Artifacts

• Windows x64
• Linux x64
• macOS Apple Silicon

Each archive contains the executable, README.md, RELEASE.md, and LICENSE. SHA-256 hashes are published in checksums.txt.

Requirements

• Git for repository workflows.
• OpenSSH configuration and key-based authentication for SSH projects.
• A POSIX remote environment with standard command-line tools.
• Linux requires a glibc-based system and a Vulkan-capable desktop stack.
• The macOS build is an unsigned portable binary, not a notarized app bundle.

Before running an archive, compare its SHA-256 hash with checksums.txt.

v2.0.0

DevHub 2.0

DevHub 2 turns the project catalog into a local-first developer workspace while remaining deliberately smaller than an editor.

Highlights

• A compact project-centered shell with Overview, Files, Search, Git, and History workspaces.
• Keyboard-first navigation, command palette, project switcher, and live theme selection.
• Parser-backed README preview and a shared read-only source viewer.
• Complete everyday Git flow: changes, semantic diffs, stage, unstage, discard, commit, branch switching, Fetch, Push, and automatic local status refresh.
• Paginated commit history with topology, refs, commit details, changed files, and per-file diffs.
• One project-rooted local or SSH terminal with persistent collapse state and explicit process ownership.
• Zed-first local and SSH handoff plus a detected-editor launcher with project-aware compatibility filtering.

Network access remains explicit. DevHub does not automatically contact Git remotes or load README media.

Artifacts

• Windows x64
• Linux x64
• macOS Apple Silicon

Each archive contains the executable, README.md, RELEASE.md, and LICENSE. SHA-256 hashes are published in checksums.txt.

Requirements

• Git for repository workflows.
• OpenSSH configuration and key-based authentication for SSH projects.
• A POSIX remote environment with standard command-line tools.
• Linux requires a glibc-based system and a Vulkan-capable desktop stack.
• The macOS build is an unsigned portable binary, not a notarized app bundle.

Before running an archive, compare its SHA-256 hash with checksums.txt.

v1.1.0

DevHub GPUI 1.1.0

DevHub GPUI is a compact, Zed-first project hub for discovering and opening local and SSH-hosted projects. This release contains portable archives for Windows, Linux, and macOS.

Downloads

Choose the archive matching your platform:

• devhub-gpui-1.1.0-x86_64-pc-windows-msvc.zip for Windows x64
• devhub-gpui-1.1.0-x86_64-unknown-linux-gnu.tar.gz for Linux x64
• devhub-gpui-1.1.0-aarch64-apple-darwin.tar.gz for macOS Apple Silicon

Each archive contains the executable, README.md, RELEASE.md, and LICENSE. The release also includes checksums.txt with SHA-256 hashes for every archive.

Install

Windows

1. Extract the ZIP to a stable location.
2. Run devhub-gpui.exe.
3. Windows release builds use the GUI subsystem and do not open a terminal
   window.

Linux

1. Extract the archive.

2. Make the binary executable if required:

   chmod +x devhub-gpui

3. Run ./devhub-gpui.

The Linux build requires a glibc-based x64 environment, a Vulkan-capable graphics stack, and normal X11 or Wayland desktop libraries.

macOS

1. Extract the archive.
2. Run ./devhub-gpui from the extracted directory.

The macOS artifact targets Apple Silicon. It is an unsigned portable binary, not a notarized .app bundle, so macOS may require explicit approval before first launch.

First launch

The first launch opens source settings. Add at least one local folder or SSH source, choose its scan depth, save, and run a scan. DevHub GPUI never scans the current working directory as an implicit fallback. Configuration and cache data use the separate devhub-gpui platform identity. They do not overwrite the original DevHub application's data.

Project parity

v1.1.0 completes the approved DevHub functional-parity project. The selected product workflow is complete: scan cancellation with a "Stop" button, remote .gitignore semantics via git check-ignore, pin/unpin and hide/archive projects with persistent config, right-click context menus, themed input fields, and Windows SSH without console window flash.

Zed and SSH

Local projects open through the zed command. Remote projects use Zed's ssh://user@host/path target format.

SSH access must already work non-interactively through OpenSSH configuration, keys, or an agent. Remote project discovery requires sh and GNU-compatible find, grep, stat, wc, head, and cat. Git is required on the remote for Git metadata and ignore-rule parity. A PowerShell-only Windows SSH session is not compatible with the current remote discovery implementation.

Verify downloads

Compare an archive's SHA-256 hash with checksums.txt before running it.

PowerShell:

Get-FileHash .\devhub-gpui-1.1.0-x86_64-pc-windows-msvc.zip -Algorithm SHA256

Linux or macOS:

sha256sum devhub-gpui-1.1.0-x86_64-unknown-linux-gnu.tar.gz

Upgrade and rollback

Portable releases do not modify themselves. To upgrade, extract the new version to a new directory and launch it against the existing devhub-gpui configuration.

To roll back, keep the previous extracted directory and launch its executable. Before downgrading, back up the devhub-gpui configuration directory. Older builds refuse to overwrite configuration files declaring a newer schema version.

v1.0.0

DevHub GPUI 0.1.0

DevHub GPUI is a compact, Zed-first project hub for discovering and opening
local and SSH-hosted projects. This release contains portable archives for
Windows, Linux, and macOS.

Downloads

Choose the archive matching your platform:

• devhub-gpui-0.1.0-x86_64-pc-windows-msvc.zip for Windows x64
• devhub-gpui-0.1.0-x86_64-unknown-linux-gnu.tar.gz for Linux x64
• devhub-gpui-0.1.0-aarch64-apple-darwin.tar.gz for macOS Apple Silicon

Each archive contains the executable, README.md, RELEASE.md, and LICENSE.
The release also includes checksums.txt with SHA-256 hashes for every archive.

Install

Windows

1. Extract the ZIP to a stable location.
2. Run devhub-gpui.exe.
3. Windows release builds use the GUI subsystem and do not open a terminal
   window.

Linux

1. Extract the archive.

2. Make the binary executable if required:

   chmod +x devhub-gpui

3. Run ./devhub-gpui.

The Linux build requires a glibc-based x64 environment, a Vulkan-capable graphics
stack, and normal X11 or Wayland desktop libraries.

macOS

1. Extract the archive.
2. Run ./devhub-gpui from the extracted directory.

The macOS artifact targets Apple Silicon. It is an unsigned portable binary, not
a notarized .app bundle, so macOS may require explicit approval before first
launch.

First launch

The first launch opens source settings. Add at least one local folder or SSH
source, choose its scan depth, save, and run a scan. DevHub GPUI never scans the
current working directory as an implicit fallback.

Configuration and cache data use the separate devhub-gpui platform identity.
They do not overwrite the original DevHub application's data.

Zed and SSH

Local projects open through the zed command. Remote projects use Zed's
ssh://user@host/path target format.

SSH access must already work non-interactively through OpenSSH configuration,
keys, or an agent. Remote project discovery requires sh and GNU-compatible
find, grep, stat, wc, head, and cat. A PowerShell-only Windows SSH
session is not compatible with the current remote discovery implementation.

Verify downloads

Compare an archive's SHA-256 hash with checksums.txt before running it.

PowerShell:

Get-FileHash .\devhub-gpui-0.1.0-x86_64-pc-windows-msvc.zip -Algorithm SHA256

Linux or macOS:

sha256sum devhub-gpui-0.1.0-x86_64-unknown-linux-gnu.tar.gz

Upgrade and rollback

Portable releases do not modify themselves. To upgrade, extract the new version
to a new directory and launch it against the existing devhub-gpui
configuration.

To roll back, keep the previous extracted directory and launch its executable.
Before downgrading, back up the devhub-gpui configuration directory. Older
builds refuse to overwrite configuration files declaring a newer schema version.