What's new in 3.5.1
Background workflow results survive session changes
A background run that finished after /new, resume, fork, or /reload could leave its result on disk without injecting it back into the conversation — the tool promised automatic delivery, but a replaced session invalidated the delivery path and the failure was swallowed. Delivery now suspends across teardown and flushes into the replacement session once the runtime is live again; in-flight runs are preserved on same-project replacements or paused onto the journal path when a switch cannot safely continue them. Same-name saved slash commands reload from the live project storage after a project switch, so they no longer re-run a previous project's script.
MiniMax defaults to M3
The minimax and minimax-cn fallback defaults now select MiniMax-M3. Contributed by @octo-patch (#141).
What's Changed
- fix: label esc as back in agent detail pager footer (#130) by @vansh2408 in #136
- feat(model): default MiniMax provider to MiniMax-M3 by @octo-patch in #141
- fix(workflow): preserve background result delivery by @QuintinShaw in #143
New Contributors
- @vansh2408 made their first contribution in #136
- @octo-patch made their first contribution in #141
Full Changelog: v3.5.0...v3.5.1
