Repository navigation
Releases
v0.19.4
Update path, proven end to end
This release exists so the updater added in 0.19.3 could be walked through a real
version change instead of asserted.
What was broken before: the plugin was registered and signed, but no UI called
it; the endpoint was a releases/latest/download/latest.json path that returns an
HTML page on GitCode; and latest.json did not exist anywhere. No installed copy
could ever have been offered an update.
Now: Settings → About checks, shows the notes, downloads with a progress bar and
installs after verifying the minisign signature. The browser-served build of the
same UI states it cannot self-update rather than showing a dead button.
Verified
| Step | Evidence |
|---|---|
| Endpoint returns JSON | curl https://gitee.com/badhope/creator-studio/raw/main/latest.json → "version": "0.19.4" |
| Installer at the manifest URL is complete | HTTP 200, 40,555,465 bytes, SHA256 c42bfa2a… matches the local build |
| Signature covers that installer | verified with minisign-verify against the public key compiled into the app: SIGNATURE VALID |
Manifest signature == shipped .sig |
byte-identical |
| Gate | pnpm verify exit 0 · 730 passed · 0 skipped |
Still not automated
Clicking "download and install" inside the packaged WebView2 window needs GUI
automation this environment cannot drive. The network half, the manifest, and the
signature are verified against the real hosts; the in-shell click is covered by
unit tests and by construction, not by an observed run.
v0.19.2
What changed
The installed app answered 404 at http://127.0.0.1:7878/. The desktop shell
loads its own assets, so this was invisible in the exe — the broken entry point was
the web plus backend one.
install-daemon-deps.mjscopies the built UI intodaemon-runtime/dist/webfindWebRoot()checks that location firstapps/daemon/test/web-root.test.ts: root servesindex.html, assets are
reachable, unknown paths fall back to the SPA,/v1/*still returns a JSON 404
Verified
pnpm verify # exit 0 · 715 passed · 0 skipped · Postgres 9 realSilent install → launch → curl / returns 200 text/html; the shell renders the
first-run wizard in the light default theme with the daemon connected. CLI, MCP
(POST /mcp, 10 tools) and the desktop window all exercised on the installed copy.
Windows x64 installer is attached below; it bundles its own Node runtime, so no
Node install is needed.
v0.18.1 - security fixes
Security fixes
Seven critical defects closed, each with a regression test that failed before the fix:
- Tool allowlist now enforces execution, not just the prompt. A read-only agent could call
fs.write. - Approvals bind to tool and target. Consent to delete one file can no longer delete another.
- Dangling symlinks can no longer write outside the workspace.
- Grant settings take effect. Setting a tool to
denyreturned 200 while the agent kept running it. - Model profiles can no longer exfiltrate
env:orvault:secrets through a caller-chosen base URL. - IPv4-mapped IPv6 and DNS rebinding both bypassed the SSRF guard.
- Cloud pairing no longer allows account takeover — it requires an already-paired device or the deployment bootstrap token.
Also: grant scopes match the resolved path, and CORS no longer trusts every localhost port.
Install
Windows x64: CreatorStudio_0.18.1_x64-setup.exe (18.0 MB, signed). Node.js 22+ required on PATH.
Verification
674 tests, 0 skipped, including nine Postgres tenant-isolation tests against a real cluster. The installer was built with the daemon runtime included and verified to launch.
v0.18.0 — agent protocols, honest limits
Creator Studio 0.18.0
A local-first production desk for people who ship creative work alone.
What's in this release
- Six scenario packs — video, novels, podcasts, courses, long-form writing, shorts. Each declares its own stages, views, card types and checklist as JSON; the engine reads packs, never executes them.
- Contract-checked output — every artifact validated against a zod schema, with one corrective retry on bad model output. A failure is a readable error, never a silent write.
- Approval gates — delete, write-outside-workspace and shell execution require a human decision, single use, resumable.
- Provenance — reference URLs are really fetched; private hosts, credentials and non-http(s) schemes refused, robots respected.
- Local export — ZIP with the latest of each artifact, a README and a per-file sha256 manifest. Nothing is uploaded anywhere.
- Agent protocols — MCP-style tool annotations, an A2A Agent Card, AG-UI lifecycle event names.
Install
Windows x64: CreatorStudio_0.18.0_x64-setup.exe (17.2 MB). The installer bundles the daemon; Node.js 22+ must be on PATH.
Verification
668 tests pass, 0 skipped, including nine Postgres tenant-isolation tests against a real cluster. 27 pages rendered in a real browser with zero console errors and zero overflow.
Honest limits
Live vendor models, macOS/Linux installers, the auto-update round trip and the desktop→cloud chain are not verified. See docs/STATUS.md. No time-saving figure is published because none has been measured.