Repository navigation
Releases
SpecDriven v0.1.265
What's changed
- The settings file is YAML: settings.json is converted to settings.yaml (#437)
Install and verify
Source snapshot of SpecDriven/specdriven-app at v0.1.265 (87d61a1).
Install: curl -fsSL https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.sh | sh downloads specdriven-0.1.265-src.zip, checks the signature on SHASUMS256.txt and the zip's checksum against it, unpacks it under ~/.specdriven/app, builds it and starts it. It offers to install Bun first if the machine has none.
Install on Windows (PowerShell): irm https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.ps1 | iex does the same under %USERPROFILE%\.specdriven\app, adds SpecDriven to the Start menu and starts it.
Windows installer: prebuilt installers that need neither Bun nor a build are published on request as a release of their own, windows-v0.1.265, when there is one; see Releases.
To review the source before it runs: download specdriven-0.1.265-src.zip, SHASUMS256.txt and SHASUMS256.txt.sig, verify them as below, and unzip it yourself.
To verify this release by hand: gh attestation verify specdriven-0.1.265-src.zip --repo SpecDriven/specdriven-app checks GitHub's build provenance (this workflow, this commit). Offline, SHASUMS256.txt.sig is an SSH signature by the SpecDriven release key, release@specdriven.app; with the key the installers embed in a one-line allowed_signers file, ssh-keygen -Y verify -f allowed_signers -I release@specdriven.app -n specdriven-release -s SHASUMS256.txt.sig < SHASUMS256.txt, then sha256sum -c SHASUMS256.txt. The steps are spelled out in docs/installation.md.
SpecDriven is built with Bun: bun install --frozen-lockfile, then bun run start for the web app or bun run build:desktop for the desktop installer.
GitHub also attaches its own Source code (zip) and Source code (tar.gz) to every release; specdriven-0.1.265-src.zip is the one SHASUMS256.txt vouches for and the installers download.
SpecDriven v0.1.264
What's changed
- A worktree session starts from main, level with origin (#436)
Install and verify
Source snapshot of SpecDriven/specdriven-app at v0.1.264 (a602f07).
Install: curl -fsSL https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.sh | sh downloads specdriven-0.1.264-src.zip, checks the signature on SHASUMS256.txt and the zip's checksum against it, unpacks it under ~/.specdriven/app, builds it and starts it. It offers to install Bun first if the machine has none.
Install on Windows (PowerShell): irm https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.ps1 | iex does the same under %USERPROFILE%\.specdriven\app, adds SpecDriven to the Start menu and starts it.
Windows installer: prebuilt installers that need neither Bun nor a build are published on request as a release of their own, windows-v0.1.264, when there is one; see Releases.
To review the source before it runs: download specdriven-0.1.264-src.zip, SHASUMS256.txt and SHASUMS256.txt.sig, verify them as below, and unzip it yourself.
To verify this release by hand: gh attestation verify specdriven-0.1.264-src.zip --repo SpecDriven/specdriven-app checks GitHub's build provenance (this workflow, this commit). Offline, SHASUMS256.txt.sig is an SSH signature by the SpecDriven release key, release@specdriven.app; with the key the installers embed in a one-line allowed_signers file, ssh-keygen -Y verify -f allowed_signers -I release@specdriven.app -n specdriven-release -s SHASUMS256.txt.sig < SHASUMS256.txt, then sha256sum -c SHASUMS256.txt. The steps are spelled out in docs/installation.md.
SpecDriven is built with Bun: bun install --frozen-lockfile, then bun run start for the web app or bun run build:desktop for the desktop installer.
GitHub also attaches its own Source code (zip) and Source code (tar.gz) to every release; specdriven-0.1.264-src.zip is the one SHASUMS256.txt vouches for and the installers download.
SpecDriven v0.1.263
What's changed
- Switching folders closes the other folder's coding agent sessions (#435)
- The Files tab's editor highlights source code by language (#434)
- The start screen opens spec folders and code repositories from one field (#433)
Install and verify
Source snapshot of SpecDriven/specdriven-app at v0.1.263 (c068846).
Install: curl -fsSL https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.sh | sh downloads specdriven-0.1.263-src.zip, checks the signature on SHASUMS256.txt and the zip's checksum against it, unpacks it under ~/.specdriven/app, builds it and starts it. It offers to install Bun first if the machine has none.
Install on Windows (PowerShell): irm https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.ps1 | iex does the same under %USERPROFILE%\.specdriven\app, adds SpecDriven to the Start menu and starts it.
Windows installer: prebuilt installers that need neither Bun nor a build are published on request as a release of their own, windows-v0.1.263, when there is one; see Releases.
To review the source before it runs: download specdriven-0.1.263-src.zip, SHASUMS256.txt and SHASUMS256.txt.sig, verify them as below, and unzip it yourself.
To verify this release by hand: gh attestation verify specdriven-0.1.263-src.zip --repo SpecDriven/specdriven-app checks GitHub's build provenance (this workflow, this commit). Offline, SHASUMS256.txt.sig is an SSH signature by the SpecDriven release key, release@specdriven.app; with the key the installers embed in a one-line allowed_signers file, ssh-keygen -Y verify -f allowed_signers -I release@specdriven.app -n specdriven-release -s SHASUMS256.txt.sig < SHASUMS256.txt, then sha256sum -c SHASUMS256.txt. The steps are spelled out in docs/installation.md.
SpecDriven is built with Bun: bun install --frozen-lockfile, then bun run start for the web app or bun run build:desktop for the desktop installer.
GitHub also attaches its own Source code (zip) and Source code (tar.gz) to every release; specdriven-0.1.263-src.zip is the one SHASUMS256.txt vouches for and the installers download.
SpecDriven v0.1.262
What's changed
- The user menu offers Log out instead of Sign in with token (#432)
- The agent header's account chip shows an icon instead of ACNT or API (#431)
Install and verify
Source snapshot of SpecDriven/specdriven-app at v0.1.262 (7cd98b8).
Install: curl -fsSL https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.sh | sh downloads specdriven-0.1.262-src.zip, checks the signature on SHASUMS256.txt and the zip's checksum against it, unpacks it under ~/.specdriven/app, builds it and starts it. It offers to install Bun first if the machine has none.
Install on Windows (PowerShell): irm https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.ps1 | iex does the same under %USERPROFILE%\.specdriven\app, adds SpecDriven to the Start menu and starts it.
Windows installer: prebuilt installers that need neither Bun nor a build are published on request as a release of their own, windows-v0.1.262, when there is one; see Releases.
To review the source before it runs: download specdriven-0.1.262-src.zip, SHASUMS256.txt and SHASUMS256.txt.sig, verify them as below, and unzip it yourself.
To verify this release by hand: gh attestation verify specdriven-0.1.262-src.zip --repo SpecDriven/specdriven-app checks GitHub's build provenance (this workflow, this commit). Offline, SHASUMS256.txt.sig is an SSH signature by the SpecDriven release key, release@specdriven.app; with the key the installers embed in a one-line allowed_signers file, ssh-keygen -Y verify -f allowed_signers -I release@specdriven.app -n specdriven-release -s SHASUMS256.txt.sig < SHASUMS256.txt, then sha256sum -c SHASUMS256.txt. The steps are spelled out in docs/installation.md.
SpecDriven is built with Bun: bun install --frozen-lockfile, then bun run start for the web app or bun run build:desktop for the desktop installer.
GitHub also attaches its own Source code (zip) and Source code (tar.gz) to every release; specdriven-0.1.262-src.zip is the one SHASUMS256.txt vouches for and the installers download.
SpecDriven v0.1.261
What's changed
- The User info dialog no longer shows the email (#430)
Install and verify
Source snapshot of SpecDriven/specdriven-app at v0.1.261 (41b6b09).
Install: curl -fsSL https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.sh | sh downloads specdriven-0.1.261-src.zip, checks the signature on SHASUMS256.txt and the zip's checksum against it, unpacks it under ~/.specdriven/app, builds it and starts it. It offers to install Bun first if the machine has none.
Install on Windows (PowerShell): irm https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.ps1 | iex does the same under %USERPROFILE%\.specdriven\app, adds SpecDriven to the Start menu and starts it.
Windows installer: prebuilt installers that need neither Bun nor a build are published on request as a release of their own, windows-v0.1.261, when there is one; see Releases.
To review the source before it runs: download specdriven-0.1.261-src.zip, SHASUMS256.txt and SHASUMS256.txt.sig, verify them as below, and unzip it yourself.
To verify this release by hand: gh attestation verify specdriven-0.1.261-src.zip --repo SpecDriven/specdriven-app checks GitHub's build provenance (this workflow, this commit). Offline, SHASUMS256.txt.sig is an SSH signature by the SpecDriven release key, release@specdriven.app; with the key the installers embed in a one-line allowed_signers file, ssh-keygen -Y verify -f allowed_signers -I release@specdriven.app -n specdriven-release -s SHASUMS256.txt.sig < SHASUMS256.txt, then sha256sum -c SHASUMS256.txt. The steps are spelled out in docs/installation.md.
SpecDriven is built with Bun: bun install --frozen-lockfile, then bun run start for the web app or bun run build:desktop for the desktop installer.
GitHub also attaches its own Source code (zip) and Source code (tar.gz) to every release; specdriven-0.1.261-src.zip is the one SHASUMS256.txt vouches for and the installers download.
SpecDriven v0.1.260
What's changed
- A session ends with the specs caught up with the code (#429)
Install and verify
Source snapshot of SpecDriven/specdriven-app at v0.1.260 (ba47a46).
Install: curl -fsSL https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.sh | sh downloads specdriven-0.1.260-src.zip, checks the signature on SHASUMS256.txt and the zip's checksum against it, unpacks it under ~/.specdriven/app, builds it and starts it. It offers to install Bun first if the machine has none.
Install on Windows (PowerShell): irm https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.ps1 | iex does the same under %USERPROFILE%\.specdriven\app, adds SpecDriven to the Start menu and starts it.
Windows installer: prebuilt installers that need neither Bun nor a build are published on request as a release of their own, windows-v0.1.260, when there is one; see Releases.
To review the source before it runs: download specdriven-0.1.260-src.zip, SHASUMS256.txt and SHASUMS256.txt.sig, verify them as below, and unzip it yourself.
To verify this release by hand: gh attestation verify specdriven-0.1.260-src.zip --repo SpecDriven/specdriven-app checks GitHub's build provenance (this workflow, this commit). Offline, SHASUMS256.txt.sig is an SSH signature by the SpecDriven release key, release@specdriven.app; with the key the installers embed in a one-line allowed_signers file, ssh-keygen -Y verify -f allowed_signers -I release@specdriven.app -n specdriven-release -s SHASUMS256.txt.sig < SHASUMS256.txt, then sha256sum -c SHASUMS256.txt. The steps are spelled out in docs/installation.md.
SpecDriven is built with Bun: bun install --frozen-lockfile, then bun run start for the web app or bun run build:desktop for the desktop installer.
GitHub also attaches its own Source code (zip) and Source code (tar.gz) to every release; specdriven-0.1.260-src.zip is the one SHASUMS256.txt vouches for and the installers download.
SpecDriven v0.1.259
What's changed
- The coding agent's message box recalls sent messages, answers /help and names the open file (#428)
Install and verify
Source snapshot of SpecDriven/specdriven-app at v0.1.259 (43723b9).
Install: curl -fsSL https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.sh | sh downloads specdriven-0.1.259-src.zip, checks the signature on SHASUMS256.txt and the zip's checksum against it, unpacks it under ~/.specdriven/app, builds it and starts it. It offers to install Bun first if the machine has none.
Install on Windows (PowerShell): irm https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.ps1 | iex does the same under %USERPROFILE%\.specdriven\app, adds SpecDriven to the Start menu and starts it.
Windows installer: prebuilt installers that need neither Bun nor a build are published on request as a release of their own, windows-v0.1.259, when there is one; see Releases.
To review the source before it runs: download specdriven-0.1.259-src.zip, SHASUMS256.txt and SHASUMS256.txt.sig, verify them as below, and unzip it yourself.
To verify this release by hand: gh attestation verify specdriven-0.1.259-src.zip --repo SpecDriven/specdriven-app checks GitHub's build provenance (this workflow, this commit). Offline, SHASUMS256.txt.sig is an SSH signature by the SpecDriven release key, release@specdriven.app; with the key the installers embed in a one-line allowed_signers file, ssh-keygen -Y verify -f allowed_signers -I release@specdriven.app -n specdriven-release -s SHASUMS256.txt.sig < SHASUMS256.txt, then sha256sum -c SHASUMS256.txt. The steps are spelled out in docs/installation.md.
SpecDriven is built with Bun: bun install --frozen-lockfile, then bun run start for the web app or bun run build:desktop for the desktop installer.
GitHub also attaches its own Source code (zip) and Source code (tar.gz) to every release; specdriven-0.1.259-src.zip is the one SHASUMS256.txt vouches for and the installers download.
SpecDriven v0.1.258
What's changed
- Plugin repos are cloned by system git, then built-in git, then gh (#427)
Install and verify
Source snapshot of SpecDriven/specdriven-app at v0.1.258 (36783c7).
Install: curl -fsSL https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.sh | sh downloads specdriven-0.1.258-src.zip, checks the signature on SHASUMS256.txt and the zip's checksum against it, unpacks it under ~/.specdriven/app, builds it and starts it. It offers to install Bun first if the machine has none.
Install on Windows (PowerShell): irm https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.ps1 | iex does the same under %USERPROFILE%\.specdriven\app, adds SpecDriven to the Start menu and starts it.
Windows installer: prebuilt installers that need neither Bun nor a build are published on request as a release of their own, windows-v0.1.258, when there is one; see Releases.
To review the source before it runs: download specdriven-0.1.258-src.zip, SHASUMS256.txt and SHASUMS256.txt.sig, verify them as below, and unzip it yourself.
To verify this release by hand: gh attestation verify specdriven-0.1.258-src.zip --repo SpecDriven/specdriven-app checks GitHub's build provenance (this workflow, this commit). Offline, SHASUMS256.txt.sig is an SSH signature by the SpecDriven release key, release@specdriven.app; with the key the installers embed in a one-line allowed_signers file, ssh-keygen -Y verify -f allowed_signers -I release@specdriven.app -n specdriven-release -s SHASUMS256.txt.sig < SHASUMS256.txt, then sha256sum -c SHASUMS256.txt. The steps are spelled out in docs/installation.md.
SpecDriven is built with Bun: bun install --frozen-lockfile, then bun run start for the web app or bun run build:desktop for the desktop installer.
GitHub also attaches its own Source code (zip) and Source code (tar.gz) to every release; specdriven-0.1.258-src.zip is the one SHASUMS256.txt vouches for and the installers download.
SpecDriven v0.1.257
What's changed
- Links sync the folder before they open; a miss says why (#426)
Install and verify
Source snapshot of SpecDriven/specdriven-app at v0.1.257 (ce99fa4).
Install: curl -fsSL https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.sh | sh downloads specdriven-0.1.257-src.zip, checks the signature on SHASUMS256.txt and the zip's checksum against it, unpacks it under ~/.specdriven/app, builds it and starts it. It offers to install Bun first if the machine has none.
Install on Windows (PowerShell): irm https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.ps1 | iex does the same under %USERPROFILE%\.specdriven\app, adds SpecDriven to the Start menu and starts it.
Windows installer: prebuilt installers that need neither Bun nor a build are published on request as a release of their own, windows-v0.1.257, when there is one; see Releases.
To review the source before it runs: download specdriven-0.1.257-src.zip, SHASUMS256.txt and SHASUMS256.txt.sig, verify them as below, and unzip it yourself.
To verify this release by hand: gh attestation verify specdriven-0.1.257-src.zip --repo SpecDriven/specdriven-app checks GitHub's build provenance (this workflow, this commit). Offline, SHASUMS256.txt.sig is an SSH signature by the SpecDriven release key, release@specdriven.app; with the key the installers embed in a one-line allowed_signers file, ssh-keygen -Y verify -f allowed_signers -I release@specdriven.app -n specdriven-release -s SHASUMS256.txt.sig < SHASUMS256.txt, then sha256sum -c SHASUMS256.txt. The steps are spelled out in docs/installation.md.
SpecDriven is built with Bun: bun install --frozen-lockfile, then bun run start for the web app or bun run build:desktop for the desktop installer.
GitHub also attaches its own Source code (zip) and Source code (tar.gz) to every release; specdriven-0.1.257-src.zip is the one SHASUMS256.txt vouches for and the installers download.
SpecDriven v0.1.256
What's changed
- gh engine: clone github.com repos by host-qualified name (#425)
Install and verify
Source snapshot of SpecDriven/specdriven-app at v0.1.256 (d7f0fc4).
Install: curl -fsSL https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.sh | sh downloads specdriven-0.1.256-src.zip, checks the signature on SHASUMS256.txt and the zip's checksum against it, unpacks it under ~/.specdriven/app, builds it and starts it. It offers to install Bun first if the machine has none.
Install on Windows (PowerShell): irm https://raw.githubusercontent.com/SpecDriven/specdriven-app/main/install.ps1 | iex does the same under %USERPROFILE%\.specdriven\app, adds SpecDriven to the Start menu and starts it.
Windows installer: prebuilt installers that need neither Bun nor a build are published on request as a release of their own, windows-v0.1.256, when there is one; see Releases.
To review the source before it runs: download specdriven-0.1.256-src.zip, SHASUMS256.txt and SHASUMS256.txt.sig, verify them as below, and unzip it yourself.
To verify this release by hand: gh attestation verify specdriven-0.1.256-src.zip --repo SpecDriven/specdriven-app checks GitHub's build provenance (this workflow, this commit). Offline, SHASUMS256.txt.sig is an SSH signature by the SpecDriven release key, release@specdriven.app; with the key the installers embed in a one-line allowed_signers file, ssh-keygen -Y verify -f allowed_signers -I release@specdriven.app -n specdriven-release -s SHASUMS256.txt.sig < SHASUMS256.txt, then sha256sum -c SHASUMS256.txt. The steps are spelled out in docs/installation.md.
SpecDriven is built with Bun: bun install --frozen-lockfile, then bun run start for the web app or bun run build:desktop for the desktop installer.
GitHub also attaches its own Source code (zip) and Source code (tar.gz) to every release; specdriven-0.1.256-src.zip is the one SHASUMS256.txt vouches for and the installers download.