A failed connect from the add/edit form reopens it with the typed
values and the error, instead of dropping back to the list.
Far more useful when the address is wrong.
Bump version to 0.1.4 (build 5).
A connection saved without a name (including the one migrated from the
single-server record) showed its URL as both title and subtitle. Fall
back to the host, and migrate old records that stored the URL as the
name.
Match the first-party mobile client's connection screen:
- the first screen lists saved servers, the one last used leading with
its connect button or connected state, the others below, and adding
is one tap
- servers can be added, edited (name, address, proxy, self-signed) and
deleted; deleting the live or last one returns to the list
- a password sheet prompts only when the server asks for one, keeps the
error and the typed password for a retry
- while connected, the instances sheet switches servers
- proxy and self-signed options stay per server (the native app's own)
- the single-server record and its token migrate automatically
- permission cards read a plain signal, fixing a flaky update
- bump version to 0.1.2 (build 3)
The stored connection remembers that no password was set, but the
reconnect path still required a device token and asked for the password.
Reconnect without one when the server issued none.
Add a Go client for OpenChamber built with Asuka's native widgets.
- internal/ocapi: health, password-to-device-token auth, session and
message paging, prompt/interrupt/model/agent, permissions, SSE events,
HTTP/SOCKS5 proxies and certificate pinning
- internal/storage: connection settings plus a device token in the
platform keystore, with a per-install id for server-side dedupe
- internal/appui: connect, session list and chat screens with streaming
Markdown, reasoning/tool folding, permission cards and session actions
- netcfg: native module that enables cleartext HTTP in release builds
- cmd/ocprobe: terminal probe for the API
- headless UI tests (uitest) and the research/plan document