Maestrly v0.32.0: Model fallback, undo a turn's file changes and bot skills

by•

A big one: a turn can now keep going when its model gives out, you can roll back what a turn did to your files, and bots can build up skills of their own.

  • Fallback models. When a model hits its usage limit, loses its login, is unavailable or runs out of context, the turn can continue on the next model in your list, API-key providers included. Set it up in Settings → Models and agents → Fallback models. It's off until you add a model, and you can pin a conversation to its own model.

  • Undo a turn's file changes. When a turn changes files, its answer shows the diffs, and "Undo changes of this turn" puts them back, whether the agent used its file tools or ran commands. You review each file first, can undo just one, and can redo. It works with or without Git.

  • Bots keep their own skills. A bot can save a procedure it learned as a skill and improve it over time. In the bot's Settings → Skills you see each skill's history, restore a version, edit or lock it, or require your approval before a change takes effect.

  • One account rotation per provider. Claude and Codex accounts now share a single ordered rotation in Settings → Accounts. An account you pick directly stays fixed and stops when it runs out instead of switching. The failover routes you already had become the new rotation.

  • Long conversations hold up better. Agents search past messages by what they're about, not only by exact words, and compaction keeps decisions, pending requests and exact identifiers in fixed sections, with the latest part of the conversation kept word for word.

  • Sturdier with local models. Ollama, LM Studio, llama.cpp and vLLM report the context window they actually run with, and malformed tool calls from any model are repaired before they fail.

Release notes:

1 view

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.