SDK and browser packages 0.2.2

Released 2026-11-07. Changes since v0.2.1.

• Added sidebar settings for language preferences. Hosted dashboards also show,
  copy and reset the browser identity there. Opening settings from a public share
  loads the registered profile without replacing the active share or changing its
  permissions; profile-loading failures expose a retry action.
• Simplified the dashboard header into a connection summary with app counts and
  a connection-management popup. Readable names take precedence over identifiers,
  which remain available in details. Board view hides editing and sharing notices.
• Moved owner and gateway invitations into dialogs that preserve the active board
  and unsaved edits. Accepting a connection change asks before discarding edits;
  dismissing an invitation keeps the current session.
• Fixed recovery after failed owner registration, local credential saves and
  profile locks held by another tab. Duplicate invitations no longer replace
  pending save recovery, and connection teardown ignores late results.
• Standardized dialog close controls, keyboard dismissal and focus restoration,
  and improved narrow-screen layouts. Storage failures during dismissal keep the
  invitation and recovery controls visible.
• Localized native-app handoff actions and removed stale invitation banners after
  React takes over. Active sharing links retain their own native-app handoff.
• Reorganized English and Japanese installation, CLI, SDK and mobile documentation,
  with dedicated typed-input, transport and catalog-generation references.

Upgrade: this is a compatible dashboard update. Sharing links, saved boards,
owner access and Gateway trust require no migration from 0.2.1 / native 0.3.1.
The sharing and Gateway protocols are unchanged.

TypeScript, Python and Rust SDK application behavior, core transport helpers and
renderer behavior have no implementation changes. Their versions advance together
with hub-ui under the existing SDK/browser release policy. Native CLI/utils ship
the updated dashboard separately as 0.3.2. npm packages become installable after
maintainer approval of their staged uploads.

See the SDK/browser release procedure and
full comparison.

SDK and browser packages 0.2.1

SDK and browser packages 0.2.1

Released 2026-11-06. Changes since v0.2.0.

• Updated @omochi-ui/hub-ui to create and open reusable v2 sharing links.
  App interaction and layout editing can be enabled independently. Links work
  across browsers and native clients without shared-client identity enrollment.
• Simplified sharing controls and updated Japanese/English permission and
  invalid-link messages. Forwarded links carry the same permissions as the
  original link.
• Updated the browser transport to use omochi/dashboard/2 and the unified
  share mode. Owner enrollment continues to use the existing v1 protocol.
• Updated dashboard, remote access, CLI and media documentation.

Upgrade note: use a matching native Hub 0.3.1 and current hosted/self-hosted
client. Existing v1 sharing links and registered shared-client grants are
retired; owners must issue replacement links. Owner access and Gateway trust
are preserved. See the native upgrade notes.

TypeScript, Python and Rust SDK application behavior, core transport helpers
and renderer behavior have no source changes in this release. Their versions
advance together with hub-ui under the existing SDK/browser release policy.
Native CLI/utils are released separately as 0.3.1. npm packages become
installable after maintainer approval of their staged uploads.

See the SDK/browser release procedure and
full comparison.

Native services 0.3.2

Released 2026-11-07. Changes since native-v0.3.1.

• Bundled the updated dashboard with sidebar language settings, compact connection
  controls, consistent dialogs and cleaner board view. Hosted clients additionally
  expose browser identity settings with copy, reset and profile-loading recovery.
• Updated owner/gateway invitation flows to preserve the current board and unsaved
  edits, and fixed recovery after registration or local-save failures, duplicate
  invitations and browser profile contention.
• Improved keyboard focus, narrow-screen controls and Japanese/English native-app
  handoff labels, and removed stale invitation actions.
• Reorganized the English and Japanese user documentation and references.

The native server implementation and wire protocols have no changes in this
release. The native version advances to distribute the new embedded dashboard in
the CLI, Cargo packages, platform archives and Docker image. See the
SDK/browser 0.2.2 notes for the complete dashboard changes.

Upgrade from 0.3.1: no re-pairing, shared-link replacement or data migration is
required. Install 0.3.2 and restart the Hub to serve the updated dashboard.
Users upgrading from 0.3.0 or earlier must also follow the
0.3.1 migration notes.

npm install -g @omochi-ui/cli@0.3.2 @omochi-ui/utils@0.3.2
# Or install from Rust sources:
cargo install omochi-cli --version 0.3.2 --locked

The Docker image is ghcr.io/omochi-ui/omochi:0.3.2, for linux/amd64 and
linux/arm64. There is no latest image tag. npm packages become installable
after maintainer approval of their staged uploads.

See the native release procedure and
full comparison.

Native services 0.3.1

Native 0.3.1

Released 2026-11-06. Changes since native-v0.3.0.

Changes

• Unified dashboard invitations and public links into reusable sharing links.
  App interaction and layout editing can be enabled independently; both are
  disabled by default. Anyone holding a forwarded link receives the same
  permissions, without registering a recipient identity.
• Updated browser and Flutter clients to use the same v2 sharing links. Native
  clients can open a link once or explicitly save its credential in protected
  storage.
• Fixed native profile loading when old invite or public records are present.
  Valid legacy sharing records are removed while retaining the existing client
  identity, owner connections and v2 shares. Corrupt data and storage failures
  continue to report errors.
• Raised the downstream listener limit from 16 to 128 concurrent connections,
  shared across owner/shared sessions and unauthenticated handshakes. The limit
  of eight in-flight request streams per connection is unchanged.
• Updated Japanese and English guides, architecture documentation and the
  dashboard sharing contract.

Upgrade

Existing v1 sharing links and registered shared-client grants stop working.
The Hub replaces recognized v1 sharing storage with an empty v2 store. Reissue
all dashboard sharing links after upgrading; old identity grants are never
converted into link credentials. Owner links/enrollment and Gateway trust are
preserved.

The sharing protocol is now omochi/dashboard/2; the sharing enrollment protocol
has been removed. POST /api/shares and owner shareCreate accept a board ID and
permissions without the old public field. Update custom integrations and use
matching browser/native clients. Gateway v4 and SDK application protocols have
not changed.

Back up persisted configuration before upgrading. Restart native services with
0.3.1, update clients, then create and distribute replacement sharing links.
For Docker, use the checkout at native-v0.3.1 and run:

export OMOCHI_VERSION=0.3.1
docker compose -f deploy/docker/compose.yaml pull hub
docker compose -f deploy/docker/compose.yaml up --build -d --wait

The versioned image is ghcr.io/omochi-ui/omochi:0.3.1, for linux/amd64 and
linux/arm64. There is no latest image tag. npm CLI/utils and native platform
packages use version 0.3.1; the separate SDK/browser release is 0.2.1. npm
packages become installable after maintainer approval of their staged uploads.

See the sharing guide,
v2 protocol,
native release procedure and
full comparison.

v0.1.2

• Update package source, documentation, and issue links for the move to omochi-ui/omochi.
• Refine dashboard controls and icons.
• Add a shared agent approval example for reviewing tool calls from Codex, Claude Code, Cursor, and OpenCode in Omochi.

All SDKs and npm packages use version 0.1.2.

Full changelog: v0.1.1...v0.1.2

v0.1.1

Publish the Omochi CLI, supporting npm packages, and Python/Rust SDKs at the shared version 0.1.1.

• Submit the seven npm packages through Trusted Publishing with provenance to npm's staging area. A maintainer must review and approve the stages with 2FA before they become publicly installable.
• Publish the Python wheel/source distribution and Rust crate through OIDC Trusted Publishing on GitHub Actions.

The release workflow tests all three languages and verifies packaged distributions before publishing. The CLI requires Bun 1.4.3 or newer.