Bloks 2.5.32

Archiving really stops an agent, long conversations stop eating your limits, and Telegram answers survive a restart

• Archive stops the work. An archived agent no longer starts tools from a turn that was already on its way, every way of archiving interrupts what is running, and nothing it asks for afterwards is allowed. Its routines and watchers pause without losing their settings, and Restore brings them back with a note saying which ones (#220).
• Long conversations compact before the next turn. A conversation close to its engine's window is compacted first (Claude Code, Codex and Pi each in their own way), so a tool-heavy turn stops resending a huge context on every step. The threshold is in Settings, next to Compact while idle (#222, #223).
• A bounded handoff for a new session. Switching engines, a backup taking over, or a session that could not be resumed now gets a summary and the recent messages instead of the whole conversation.
• Context sizes read right. Codex conversations no longer all read 100% full, and every engine's own window is used where it reports one (#224).
• Telegram answers come back after a restart. A message sent to the bot while Bloks was restarting now gets its answer in the same chat (#225, thanks @rpavlovs).
• Better voice transcription. OpenAI voice messages use gpt-transcribe, which is cheaper and more accurate (#221, thanks @rpavlovs).
• Room archive errors are shown. If archiving a room fails, Bloks says so and puts the room back (#226).
• Updates. Electron 44.7, motion 14, lucide-react and posthog-js.

Thanks to @pycckuu, @mixo44 and @rpavlovs for the reports.