Sasha Studio release notes: v1.0.1442 to v1.0.1443
Executive Summary
Administrators can give each member No access, Read, or Read & write for whole knowledge projects. With shared writes enabled, members can create and edit documents through Claude in the projects assigned to them. Document content stays on disk.
Major Features & Improvements
- Set project access in Settings โ My Account โ User Management โ member menu โ Knowledge Grants.
- Read & write permits document creation and editing. Existing grants remain read-only.
- Downgrading or removing a grant applies to existing connections on their next request.
- Member homes remain private; another memberโs home cannot be assigned as a shared project.
Stability & Reliability
- Managed filesystem writers coordinate across requests and processes, including Git operations, startup maintenance and scheduled Claude runs.
- Shared edits retain version conflict detection, repeat-request handling and crash recovery.
- Project retirement settles unfinished operations together with retirement metadata.
Developer Experience & Docs
- PRD 20 ยง10.0c records the filesystem-first shared-project scope.
- The writer audit, Linux runtime proof and deployment record document the supported boundary and verification.
- The internal acceptance probe supports writable shared projects and read-only refusal checks.
Upgrade Notes
- Shared writes default to disabled and require the independent
MCP_KNOWLEDGE_SHARED_WRITES_ENABLED=trueflag, a dedicated handle key and supported Linux/ext4 storage. - Deploy the guarded image before enabling shared writes. Each member also needs an explicit project write grant and a connection with knowledge write scope.
- Trusted interactive staff shell/CLI remains outside managed-writer coordination. Intentionally detached automation is outside the supported release boundary.
- This release does not enable global unified authorization or change other instance deployment pins.
Changelog Summary
Source range: v1.0.1442..v1.0.1443.
Member project grant levels, shared filesystem create/edit, managed-writer locking, subprocess lifetime handling, retirement recovery, UI concurrency protection and expanded acceptance evidence.
Looking Ahead
Git history/restore, additional document mutations and permissions for individual subfolders remain future work.
