Release candidate 1.1

01 / What it was

Release candidate 1.1 put everything from September into one installable package: the blocks, the terminals that survive, Hermes at each desk, the web walls and the launcher.

It stayed private. It was never published as a release, but it is the base that Omo Space v1.2.0 was built on.

02 / How it worked

• Blocks: Hermes Computer, Terminal, Omo Monitor, Slim Screen, Omo Linker, Omo Pocket, Name Plate and Status Lamp, with survival recipes and room kits.
• tmux owns every shell. Closing a screen, leaving the area, quitting the game or restarting the bridge never stops a process.
• If the session server did stop, it says INTERRUPTED. Reviving a shell or resuming Hermes is a button you press, never automatic.
• One titled Hermes conversation per tab, in the profile chosen for that desk.
• Remote walls: right-click a wall up to 24 blocks away and type into it. Tests at release: bridge 61/61, launcher 56/56; in-game acceptance tests last run 26-27 Sep.

03 / What we saw

Being honest about interruptions became a rule: nothing is ever silently re-run after a restart.

04 / Where it led

Renamed Omo Space, it was made public as v1.2.0 on 28 Oct.

Sources

1. Public changelog, v1.1.0 section. github.com/omoresearch/omo-space/blob/main/CHANGELOG.md v1.1.0 — release candidate (private; not published)
2. Public changelog, v1.1.0 section. github.com/omoresearch/omo-space/blob/main/CHANGELOG.md A stopped session server is reported honestly as INTERRUPTED; *Revive shell* and *Resume Hermes* are explicit.
3. Public changelog, v1.1.0 section. github.com/omoresearch/omo-space/blob/main/CHANGELOG.md Tests at release: bridge 61/61, launcher 56/56. In-game acceptance 1-8 last run 26-27 Sep 2026