Evals separate provider rejections from refusals

voitta-bookmarklet (v0.2.4 to v0.2.5)

Evaluation runs now differentiate between upstream provider errors and model refusals. Release v0.2.5 tags provider-side rejections separately, keeping inference failures from polluting refusal metrics. In v0.2.4, test harnesses also gained system prompt overrides specifically for ablation controls without touching production configuration.

skillz (v1.214.0)

v1.214.0 runs a non-credential history scrub and priced rewrite pass across the bundle as part of prep for open-sourcing the repository.

voitta-desktop (v0.1.17)

v0.1.17 was a maintenance bump with no user-facing changes.

Pin voitta-yolt to v2.8.0 before upgrading shmobster

shmobster (v0.36.2 to v0.39.0)

Check out v2.8.0 in your voitta-yolt clone before restarting shmobster. Starting in v0.37.1, the agent pins that tag at boot so updates in a sibling directory cannot silently alter live classifier verdicts. Approval requirements have relaxed for harmless commands: npm ls and read-only awk invocations now run without an approval card, while vercel execution requires an explicit per-project grant in the channel policy. Channels can also enable an opt-in post-answer skill check via "skill_check": true to flag missed techniques once a turn completes.

voitta-bookmarklet (v0.1.252 to v0.2.3)

The repo formerly known as voitta-compute was renamed to voitta-bookmarklet in v0.2.1. The v0.2.0 release shipped an eval API (/api/eval/v1) backed by durable traces and action receipts. Turn processing now routes through a TurnSink and RunContext, paired with an unattended eval worker and Claude subscription routing.

skillz (v1.180.0 to v1.213.0)

Pre-push sensitive-term gates now match whole words and fail closed when the wordlist is missing. In v1.192.0, multi-agent orchestration was corrected so allow rules no longer bypass PreToolUse hooks, alongside new roles for underspecified issues and background squad monitoring. The remaining bundles add targeted debugging and infrastructure skills, including Python deadlock attribution and Kubernetes topology spread edge cases.

shmobster’s liveness watchdog had a blind spot for three releases

shmobster (v0.29.1 to v0.35.0)

The watchdog story is the one to read carefully. v0.31.0 added a second liveness check — catching a dead message_processor thread, not just a dead socket — but the refactor also rewrote the trigger from OR to AND: it was supposed to fire when either the session was unstable or a stable session went deaf, and instead fired only when both were true at once. The real failure mode is a half-open socket: stable session, no pong, recv blocked forever. Under the AND, that never tripped. From v0.31.0 through v0.34.0, an agent could sit deaf and alive for hours with the watchdog polling and doing nothing. v0.34.1 fixes the OR and adds diagnostics; if you’re running anything in that range, upgrade. v0.34.0 separately handles the case where the whole interpreter freezes and takes the watchdog thread down with it — a different failure, a different check. Less dramatically: v0.30.0 gives channels an optional mcp policy key so any MCP server’s tools can be allow-listed per channel (voitta-rag’s search is the first consumer), and v0.32.0/v0.33.0 stop papering over read-only and file-edit turns with needless approval cards. v0.35.0 adds always_skills, so a channel can force a skill into every turn instead of leaving it as a menu entry the model sometimes skips. Releases.

voitta-compute (v0.1.250 to v0.1.251)

Two new providers: Requesty router and Codex (the ChatGPT-subscription path), alongside a small hygiene fix that stopped tracking a local mkcert TLS pair in backend/certs. Latest release.

voitta-rag (v0.1.4 to v0.1.5)

Both releases are security fixes. v0.1.4 binds voitta-rag and Qdrant to loopback only — nothing listens on an external interface by default anymore. v0.1.5 closes three redaction gaps in session memory: sk-proj- keys, PREFIX_TOKEN= style secrets, and Bearer/JWT tokens were passing through unredacted before this. Latest release.

voitta-yolt (v2.4.1 to v2.6.0)

Hardening against credential leakage from agent writes: v2.5.0 treats key-material filenames as protected write targets, v2.6.0 redacts a credential wherever its own key name already identifies it. v2.4.1 was prep for the Claude directory submission. Latest release.

skillz (v1.152.0 to v1.176.0)

Twenty-five releases, almost all new skills or plugin point-fixes in the agent-skills knowledge base. Worth noting: the claude-code-cross-session-messaging plugin got patched three times in this window (1.2.0, 1.2.1, 1.2.2) — a reply arriving after /clear, then grepping the wrong name, then merging two conditions that needed to stay independent. v1.168.0 adds a pipeline that publishes a materialized bundle to a directory branch for the Claude plugin directory, which is the more durable change here. Everything else is one-off operational knowledge (macOS menubar behind the notch, Grafana alert-rule arming races, an MCP streamable-HTTP client with no SDK, terraform plan-JSON secrecy) — useful if you hit the specific gotcha, invisible otherwise. Releases.

voitta-mcp (crm-highlevel-v0.1.0)

First release of an MCP server for HighLevel CRM: runs under docker compose, crm_find_contact now returns a link to the CRM record, and a write tool (crm_update_opportunity_status) exists but is flag-gated off by default. Release.

mods (cw-chart-v0.1.0, image-mirror-v0.1.0)

New repo. Two mods shipped at v0.1.0 — cw-chart and image-mirror — under a release-on-merge setup that gates PRs on version bumps. No user-visible behavior to summarize yet beyond "it exists." Releases.

Shmobster refuses to boot without voitta-yolt 2.0.1 or newer

If your shmobster deployment runs an old voitta-yolt classifier, upgrade voitta-yolt first. As of v0.27.0, shmobster exits at startup if its configured classifier is below the floor, instead of logging a warning and serving anyway.

shmobster (v0.7.0 to v0.30.0)

The floor itself moved twice. v0.8.0 declared voitta-yolt 2.0.0 unsupported outright; v0.9.0 reversed that a release later, setting the real range at >= 2.0.1 (a deployment stuck on 1.6.0 now refuses to run too). There’s a separate security fix worth flagging on its own: v0.19.0 closes a hole where a curl carrying a POST body could run with no approval card at all, if the box’s classifier predated voitta-yolt 2.0.0 — if that’s your box, grab that release first.

Past the gate, the window adds real capability: the agent can flag its own hard-won debugging sessions as skill candidates (v0.7.0), answer Slack DMs (v0.13.0), carry per-channel memory (v0.14.0), skip approval for in-scope git/gh work in channels marked unattended (v0.24.0), and call MCP tools per channel (v0.30.0). Most of what’s left is the approval gate getting sanded down — fewer cards for reads that only looked like writes, a typed approval and a button click no longer racing to opposite outcomes, and as of v0.29.0 a sandbox that refuses to let a channel write the deployment’s own checkout.

Full list: https://github.com/voitta-ai/shmobster/releases

voitta-yolt (v1.2.0 to v2.4.0)

v2.0.0 is the breaking release here — "the auto-mode realignment," cutting YOLT down to carry only what it refuses to delegate — and it’s the reason shmobster’s version-floor logic exists at all. The two releases right behind it are corrections to v2.0.0 itself: v2.0.1 restores a CLI path to deny, v2.0.2 fixes a doc claim about auto mode. v2.1.1 similarly walks back v2.1.0’s classifyAllShell to opt-in, default false. Separately, v2.3.1 strips employer and client names that had leaked into this public repo — check any fork or vendored copy predating that tag.

Releases: https://github.com/voitta-ai/voitta-yolt/releases

skillz (v1.79.0 to v1.159.0)

About eighty releases, nearly all single-skill additions to the catalog — Terraform forensics, Android ADB checks, Grafana alert preflights, and more in that vein. The few with teeth: codex-adversarial-pr-review grew into a real sweep tool across this window (cross-host queues, wildcard authors, multi-hour runs), parallel-agent-session-collisions got a state-dir fix for an orphaned predecessor process, and the secrets hook had three separate false-positive fixes (base64url’s underscore, key filenames read as keys, env-var references read as credentials). Nothing breaking; if you consume skillz for the catalog, diff bundle versions and move on.

Releases: https://github.com/voitta-ai/skillz/releases

voitta-compute (v0.1.237 to v0.1.251)

Two new providers: a Requesty router, and in v0.1.251, Codex via a ChatGPT subscription instead of API billing. v0.1.250 also stopped tracking the mkcert TLS pair in backend/certs — a local clone now needs to generate its own.

Releases: https://github.com/voitta-ai/voitta-compute/releases

voitta-rag (v0.1.1 to v0.1.4)

v0.1.4 changes a default worth knowing about: voitta-rag and its Qdrant backend now publish on loopback only. v0.1.2 and v0.1.3 are benchmark work — a ten-mode code-context harness, then a re-run after an index-prefix fix — useful if you’re judging retrieval quality, no action required.

Releases: https://github.com/voitta-ai/voitta-rag/releases

voitta-rag-enterprise (v0.1.1)

One release, one feature: linked folders. Point it at a host directory and it indexes in place, nothing copied into the container.

Release: https://github.com/voitta-ai/voitta-rag-enterprise/releases/tag/v0.1.1

Forward deployed ingenuity: what Voitta is, and why it now publishes release notes

Most AI tools don’t know anything about your business. They can write an email, but they can’t find last month’s invoice or tell you which order is stuck. Voitta builds the parts that connect AI to the records a business already runs on, and then we come in and assemble them for you: forward deployed ingenuity.

The parts are open (github.com/voitta-ai), so you’re never locked in. We also run them for you under contract, or help you assemble them yourself.

From next week we’ll post weekly notes on what’s new and what it lets you do. An agent drafts each one from our releases; a person reads it before it goes out.