Repository navigation
HolyCrab Agent Tools v0.6.0
HolyCrab Agent Tools v0.6.0
v0.6.0 adds four Berry models, aligns material references and validation with the backend, and improves upload, generation, update and Windows reliability. Python 3.10 or later is required.
Models and materials
- Add
berry-1.0,berry-1.0-turbo,berry-1.0-proandberry-1.0-pro-turbo, bringing the bundled CLI/MCP catalog to 16 models. - Preserve structured material errors, request IDs and metadata across CLI, JSON and MCP. Model suitability is decided by the backend; missing or pending metadata is not a new local generation blocker.
- Support
imageAssetIdsfor image generation, with backend ID priority when URLs are also supplied. Audio references accept asset IDs or URLs, and audio estimates send the complete normalized request. - Add
holycrab assets metadata retry ASSET_IDand its MCP tool. Retrying is explicit; the CLI does not loop automatically. Old Base64 orspeakeraudio references receive migration guidance.
Reliability and Windows
- Validate estimates and recheck approved prices before generation. Preserve known task and asset IDs when saving local state fails; never automatically repeat an uncertain paid submission or upload.
- Freeze confirmed upload bytes, prevent concurrent reuse of a plan, and retain recovery records. Inspect a batch with
holycrab assets uploads get PLAN_IDorasset_upload_plan_get. - Reject truncated and partial downloads before replacing existing files. Report failed or uncertain MCP mutations with
isErrorwhile retaining recovery details. - Improve installation integrity, update rollback, credential handling, cancellation and delayed Windows cleanup. Preserve user files, customized Skills and unrelated MCP registrations.
- Accept UTF-8, UTF-8 BOM and BOM-marked UTF-16 request files. Verify PowerShell 5.1, PowerShell 7 and CMD launchers. Windows installation directories containing
%or!are rejected with guidance to choose another directory.
Updates
From an installed version that supports the update command:
holycrab update --check
holycrab update
holycrab --versionThe update command asks before installing. In v0.6.0, ordinary CLI use and long-running MCP sessions check for stable updates at most once per day, retry a failed check after one hour, and avoid repeated reminders. Update notifications never install automatically. Older installations must use their existing update command to discover this release; the new notification behavior starts after upgrading.
Known Windows v0.5.0 upgrade issue
A post-release native Windows check found that holycrab update --yes from v0.5.0 can complete the v0.6.0 installation but return exit code 123 and a filename-syntax error from the old CMD launcher. The subsequent holycrab --version and holycrab doctor --json checks reported 0.6.0 and healthy runtime. This command path is recorded as failed, not a clean successful update.
For Windows upgrades, rerun the official Windows installer and then check the version and doctor result. Fresh v0.6.0 installation is unaffected. Published v0.6.0 files and its tag remain unchanged; this note records the observed post-release limitation.
Validation scope
Automated coverage includes all 16 model routes, 22 MCP tools, installed HTTP fault scenarios, ten behavioral mutation checks, and native Windows/macOS/Linux verification. A real upload/query check reused an existing authorized person, preserved the original asset and verified downloaded bytes. New liveness verification and paid generation were not performed. Windows 10/11 x64 desktop validation was explicitly excluded; tested Windows Server and ARM environments do not imply coverage of every desktop configuration.