Multica published v0.1.27 on 2026-04-12, with release notes covering self-hosting and operational hardening across storage, auth, CLI install behavior, batch issue handling, cache scoping, runtime usage filtering, and stale task recovery. The release includes a local file storage fallback, graceful email degradation for self-hosted auth, install-script upgrade and repeat-run fixes, and reset handling for stale in-progress issues.
This matters for Open Orchestrators readers because Multica is explicitly positioning itself as a board for managing human and coding-agent work together. In that context, self-hosting reliability, local fallback paths, and issue-state recovery are not background maintenance; they affect whether teams can keep agent work visible and recoverable when running their own deployment.
For operators and builders, the practical signal is that Multica is tightening the operational layer around managed coding agents rather than only adding UI features. The release also improves CLI version output with JSON and build metadata, updates required AI agent CLI documentation, and fixes batch-operation error handling, which are useful surfaces for teams automating or debugging agent workflows.
Source confidence: High for the GitHub release; medium for broader deployment impact because the release notes do not spell out plan, hosting, or migration scope.
Evidence:
Explicit non-claims:
- This update does not claim every fix applies to hosted and self-hosted deployments equally.
- This update does not claim benchmarked reliability or performance gains.
- This update does not use third-party social posts as release evidence.