Fractal 0.1.406 makes the existing workspace more reliable to operate: conversations have one consistent delivery path, agent execution is safer under retries and failures, and core workspace operations expose clearer contracts.
New
- Chat now supports one target-aware send flow for internal conversations, agent and user DMs, workspace channels, and external providers.
- Message delivery state and idempotency make external sends observable and safer to retry.
- Collections expose record-level workflows for creating, listing, reading, updating, and deleting custom data.
- Artifact visibility and workspace operations now have clearer contracts for controlled sharing and automation.
Improvements and fixes
- Agent tool execution is safer under retries: repeated calls are deduplicated, framework errors are model-safe, and identity is restored at the execution boundary.
- Tool lifecycle hook failures no longer hide or replace the underlying execution result.
- Shared chat processing is more reliable when agent turns overlap or recover from uncertain outcomes.
- Desktop startup now reports actionable gateway failures and keeps the local server available while auxiliary jobs initialize.
- Task, goal, memory, routine, toolset, and view command contracts were tightened with focused regression coverage.
Under the hood
- Generated API contracts and the Fractal plugin SDK were refreshed for the current collections release.
- Internal agent skills, task state, memories, and operational reports were synchronized separately from the customer-facing product changes.