Bloks 2.5.9

Bloks starts on Windows again

Bloks 2.5.8 didn't open on Windows from a shortcut. The port handling in 2.5.8 started the server in a way that crashes on Windows when the app has no console window. This release also fixes an older problem where the server wouldn't start if a folder above the install folder had a package.json saying "type": "commonjs", which is common in home folders. Thanks to @grantterra for tracking both down (#82).

The MCP connector follows every conversation

If you hand work to your agents from Claude Code through the Bloks connector:

• Replies come from the right place. ask_agent now says which conversation your message went to and reads the reply from there. Before, it only read the conversation open in the app, and could report "still working" while the answer sat in another one. You can also pick a conversation with lane.
• read_conversation takes a conversation too, and defaults to the one you just used.
• list_agents lists each agent's conversations and whether each is working or waiting on you.
• waiting_on_me says which conversation each item is in.
• read_message opens one whole message. Search results now include an id for it.

Approvals you can always find

• Opening an agent goes to a waiting conversation first. If one of its conversations is stopped on a question or an approval, opening the agent goes there before any unread one.
• Pointers from the chat. A chat also tells you when another of that agent's conversations is waiting on you.
• Credit and limit problems get your attention. When an agent can't answer because its engine is out of credit, over a limit or signed out, its conversation gets an unread dot and you get a notification.

Plugin hooks per agent

A new switch in an agent's settings runs Claude Code without your plugin and settings hooks for that agent. Some plugins add their own text at the start of every session, and the agent can mistake it for instructions.

Thanks to @carlmumford for the detailed report in #81.