v1.11 release line, remote workspace restore, and website automation

This week imux moved to the v1.11 release line, with v1.11.3 shipping on 2026-05-09. The most material product change is that remote workspace configuration now persists and restores across sessions, instead of having to be re-specified every time the workspace reattaches.

Releases: v1.11 line

The v1.11.0 release was merged via PR #1 on 2026-05-08 (d886286), together with website downloads staging (8b8e6b5), release copy updates (536acd1), and Sparkle build-number metadata (252bb5b, 3ee0889). Two patch releases followed quickly: v1.11.2 on the same day (cf344ad, 9a2a6f9) and v1.11.3 on 2026-05-09 (a0c3785, b88c122, 5551d6c, f015a96). The previous v1.10.14 through v1.10.20 tags appear earlier in the window, indicating the team transitioned cleanly out of the v1.10 line during the week.

Feature: remote workspace session restore

The clearest product change landed in dce940b, which adds persistence and restoration of remote workspace configuration across sessions. A preceding commit, ddac083, added support for picking the initial workspace directory when a remote session starts, so the workspace root is now an explicit parameter rather than implicit from the connection. Earlier design and implementation notes for the same area land in 228030d (design spec) and 6225671 (implementation plan).

The user-visible effect: closing the app, rebooting, or reconnecting to a remote host no longer drops your workspace assignment. Reopening restores the directory you were working in, the editor focus, and the remote session metadata that the supervisor uses for notification routing.

Website and release automation

The website surface changed on multiple axes:

• d36a758 — redesigned toward an engineering-oriented aesthetic.
• 4d46bb9 — added the geist font dependency to support the redesign.
• 82b544e — introduced /llms.txt, /compare, /status pages plus the release-blog automation workflow.
• 64f6858 — completed tag- and weekly-cron blog draft automation and added the /activity page.

Together these turn the website into a participant in the release process rather than a separate static surface that has to be hand-edited on every cut.

CI: OpenAI-compatible LLM gateway

4d1a27f extended the scripts and CI to accept an OpenAI-compatible LLM gateway with model fallback. There is no UI surface for this — the practical effect is that automation scripts and CI workflows that call an LLM (release blog drafts, weekly digests, future content jobs) can fall back across models when the primary route is unavailable, instead of failing the whole pipeline.

What to watch next

The new tag/weekly-cron blog draft automation now has enough wiring to be exercised by ordinary release and scheduled activity. The next useful signal is whether the generated drafts hold up across a full release cycle without manual rewriting, and whether the remote workspace restore work picks up follow-up patches as users hit edge cases on reconnection.