FirstCall v0.2.1 adds a verifiable desktop GUI launch path and refreshes the public demos from the released Windows archive.
Highlights:
- Desktop GUI now supports
--data-dir,--config-dir,--screen, and--samplefor repeatable validation and demos. - README now includes both CLI/MCP and desktop GUI demos.
- The former non-goal framing was replaced with positive support-boundary documentation.
- Package/runtime hardening from v0.2.0 remains: body-kind preservation, request fingerprint recomputation, stricter package validation, generated MCP stdio roundtrip in CI, and release archive checks.
Verification performed for this release:
- GitHub Actions CI passed on Windows, Linux, and macOS.
- CLI lifecycle, Loopback verify, Security audit, and Release binaries workflows passed.
- The Windows v0.2.1 release zip was downloaded locally and checked against SHA256SUMS.txt.
- The downloaded
firstcall.exereportedfirstcall 0.2.1and accepted the GUI validation flags. - The downloaded
firstcall-cli.exereportedfirstcall-cli 0.2.1. - The downloaded CLI verified GitHub GET /user with HTTP 200, exported a package, inspected it as ready, installed generated MCP dependencies, built the TypeScript server, and called the generated MCP tool successfully over stdio.
- The downloaded GUI was launched against an isolated SQLite store created by the downloaded CLI, captured showing sample request parsing and recipe storage rendering, and used to refresh the README GUI GIF.
Download the archive for your OS, extract it, and run:
firstcall --screen new --sample curlfor the desktop GUI workbench.firstcall-cli versionfor the automation CLI.
CLI verification remains environment-first. Do not put real secrets in command history, scripts, or exported artifacts.