Skip to content

Bloks 2.5.3

Choose a tag to compare

@github-actions github-actions released this 29 Sep 14:39
· 869 commits to main since this release

Setting up an engine takes a button now

Most setup trouble happened before Bloks could help: an install command that failed with a permissions error, a Mac without Node, or an engine that installed fine and then couldn't answer because nobody had signed in.

  • Install from the app. The first-run check and Settings, Engines install Claude Code, Codex, Gemini CLI, Pi, Antigravity and the Grok CLI with one click. They go into your own folder, so there's no password prompt and no permission errors.
  • Signed out says so. An engine that's installed but not signed in no longer shows as connected. Sign in opens Terminal at that engine's sign-in, and the row turns green once you finish. Codex now reports whether it's signed in too.
  • A failed install tells you what to do, such as installing Node or checking the connection, with the installer's own output a click away.

Long conversations load through Bloks Cloud

Once a few conversations got long, your phone and a Mac connected through Bloks Cloud could stop loading your agents. You'd see "not reachable" or a spinner over "No agents yet". Through Cloud, each conversation now arrives as its newest part. Show earlier messages loads the rest a page at a time, and anything too big comes back as a clear "too large" instead of timing out. On the computer running Bloks, conversations still load in full.

Conversations in the sidebar, finished

  • The + for a new conversation no longer covers "working" or "waiting".
  • Starting a conversation after closing the last one no longer leaves an empty General beside it.
  • Conversation titles line up with the agent's name.
  • Right-click a conversation to rename it, mark it unread, copy its ID or close it.
  • With the list in the sidebar, the tabs above the chat step aside, and a conversation's fullness ring moves to its row.
  • Working shows as a spinner again.

Thanks to @rpavlovs (#79) and @LandonSchropp (#78).