Skip to main content
Agent skill

Windows Release

Build and verify the Windows desktop build (NSIS installer + latest.yml) for the canonical OpenMausBot release and its legacy updater mirror. Use when cutting a release, shipping a new version to Windows users, or when a Windows user reports they are stuck on an old version. Windows only — does not cover the macOS dmg/notarization flow.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Windows Release when an AI agent needs a reusable SKILL.md workflow for this job: Build and verify the Windows desktop build (NSIS installer + latest.yml) for the canonical OpenMausBot release and its legacy updater mirror. Use when cutting a release, shipping a new version to Windows users, or when a Windows user reports they are stuck on an old version. Windows only — does not cover the macOS dmg/notarization flow.

When not to use it

Skip Windows Release when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/windows-release
# Save SKILL.md to ~/.claude/skills/windows-release/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/windows-release/SKILL.md. For a shared project, commit the folder at .claude/skills/windows-release/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Windows Release skill for this task: Use Windows Release when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Windows release

Ships `OpenMausBot-<version>-setup.exe` and its update feed to [milind-soni/OpenMausBot](https://github.com/milind-soni/OpenMausBot/releases). The unified release workflow mirrors the same bytes to the legacy releases repository for apps installed before the updater migration.

**Scope: Windows only.** The macOS build is a separate flow (dmg + notarytool + staple) that must run on a Mac. This skill never touches mac artifacts — but see [Every release ships both](#every-release-ships-both) before you finish.

## Preconditions

- **Run on Windows.** NSIS packaging from macOS needs Wine; don't. - **Node 24+** (`package.json` `engines`). Node 23 builds fine but pnpm warns on every step and CI runs 24 — don't debug a runtime oddity on the wrong major. - **pnpm** via `corepack pnpm`. If `corepack enable` fails with EPERM (no admin), drop a `pnpm.cmd` shim containing `@echo off` / `corepack pnpm %*` somewhere on PATH — `package:win` chains `pnpm build && …` and needs bare `pnpm` to resolve.

## 1. Version

Bump `version` in `package.json`. It must match the tag on the GitHub release you upload to, and it becomes the version electron-updater compares against.

## 2. Build

```powershell pnpm install pnpm typecheck pnpm package:win ```

`package:win` deliberately omits `build:speech` — the dictation helper is a signed macOS Swift binary and has no Windows counterpart.

Output in `release/`:

| File | Purpose | |---|---| | `OpenMausBot-<version>-setup.exe` | the installer | | `latest.yml` | **the update feed** — see step 4 | | `OpenMausBot-<version>-setup.exe.blockmap` | differential updates | | `OpenMausBot-<version>-x64.zip` | portable, not used by the updater |

## 3. Verify before uploading

Three things silently produce a broken app if wrong. Check all three:

```powershell Test-Path release\win-unpacked\resources\server\index.js # harness server Test-Path release\win-unpacked\resources\ui\index.html # built UI Get-Content release\win-unpacked\resources\app-update.yml # feed config ```

- Missing `server/index.js` → `utilityProcess.fork` fails → the 🐭 "Couldn't start the bot server" page. - Missing `ui/index.html` → server has nothing to serve → black window. - `app-update.yml` must point at `milind-soni/OpenMausBot` and, while the build is unsigned, **must not contain `publisherName`** — electron-updater would reject every update as untrusted.

Then smoke-test the installer itself. Run it, and confirm:

1. It installs per-user with no UAC prompt and launches. 2. The chat window renders (not the error page). Server logs land in `%APPDATA%\OpenMausBot\logs\server.log`. 3. The model picker lists at least one provider — this exercises the `.cmd`-shim resolution in `server/procs.ts`, which only ever runs for real on Windows. 4. No update popup appears on launch. Background check failures are silent by design; a popup here means that regressed.

## 4. Publish

Upload to the **same tag** as the macOS release for that version, so one release carries both platforms.

```powershell Copy-Item release/OpenMausBot-<version>-setup.exe release/OpenMausBot-setup.exe gh release upload v<version> --repo milind-soni/OpenMausBot ` release/OpenMausBot-<version>-setup.exe ` release/OpenMausBot-setup.exe ` release/OpenMausBot-<version>-setup.exe.blockmap ` release/latest.yml ```

Prefer the repository's **Release** workflow, which builds all platforms from one pinned commit and mirrors the complete, byte-identical asset set safely. If this emergency manual path is used, the same four files must also be attached to the matching draft in `milind-soni/openmausbot-releases`; never replace the bytes of an already-published asset.

Both names are required, for different consumers:

- **`OpenMausBot-<version>-setup.exe`** is what `latest.yml` references by name and sha512. The auto-updater downloads exactly this. - **`OpenMausBot-setup.exe`** is a byte-identical copy that gives the README's `/releases/latest/download/OpenMausBot-setup.exe` button a stable URL. This mirrors `OpenMausBot.dmg` sitting beside `OpenMausBot-<version>.dmg`.

### latest.yml is not optional

Without it every installed Windows app 404s on check and stays on its version forever. It is generated by `package:win` even under `--publish never`.

**Never hand-edit it or carry one forward from a previous build.** It pins the installer's sha512; a mismatch makes the updater download and then reject the update, which looks like "updates silently do nothing".

## Every release ships both

A version that exists on macOS but not on this release is a Windows user stuck on old code with no signal that anything is wrong — the updater reports "up to date" because `latest.yml` still describes the older build.

So: **whenever a new version goes out, this flow runs too.** If Windows can't ship for some reason, don't publish the mac-only release under a new version tag either — or accept that Windows is knowingly frozen and say so in the release notes.

Because the two builds must run on two machines, the tag is the join point: cut the release, attach mac artifacts from the Mac, attach Windows artifacts from here.

## Known: the build is unsigned

No certificate is configured, so SmartScreen shows "unknown publisher" and users click **More info → Run anyway**. The README documents this. Auto-update still works *because* it's unsigned (no `publisherName` to verify against).

If signing is added later, it goes under `win.signtoolOptions` or `win.azureSignOptions` in `electron-builder.yml` — electron-builder 26 nests these; there is no top-level `win.certificateFile`. Once signed, keep the certificate subject stable forever, or list both old and new in `publisherName`; changing it strands every already-installed user.

Intended uses

  • Use Windows Release when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.