A chat page carried every finished tool result, and the app fetched it
twice when opening a chat, with a 20 second deadline. On a slow link a
long session (this one was ~530 KB per page) timed out.
- ask for shelled pages (x-openchamber-part-shells: v1), which drops
finished tool results: ~180 KB for the same page
- fetch one message by id when its tool row is opened
- keep tool and step updates local from events instead of re-reading
the page on every step, and only resync after a real disconnect
- 60 second deadline with a retry button
Bump version to 0.1.11 (build 12).
Every prompt now carries a row with its time, a copy button and a menu
(copy message, fork before this prompt), matching the first-party
client. The turn footer's sparkles became an inline SVG: the platform
symbol table left an empty square on some devices.
Bump version to 0.1.10 (build 11).
The footer's "more" button now opens a sheet with the completion time
above the actions, matching the first-party client; the platform action
sheet dropped the time. Copy answer and fork from here are listed, and
a back gesture dismisses it.
Bump version to 0.1.9 (build 10).
A long turn's prompt can fall before the loaded message page. Measure
from the first record of the run then, so historical turns still show a
duration in the footer.
Bump version to 0.1.8 (build 9).
Match the first-party chat footer on touch screens: after a turn ends,
its last assistant message gets a row with the model name (resolved
from /api/model with the id as fallback), the agent and how long the
turn took, plus a "more" menu. The menu shows the completion timestamp
and offers copy answer and fork from here; forking copies history
before the next prompt (or the whole history at the end) and opens the
new session.
Bump version to 0.1.7 (build 8).
While disconnected the screen is the bare list with its own heading;
the navigation stack (and its new-session and refresh actions) exists
only once connected. That removes the duplicate title and the buttons
that could do nothing without a session.
Bump version to 0.1.6 (build 7).
The session screen now has a single server icon that opens the instance
list; picking an instance drops the live connection and connects to it,
and disconnecting moved into that list. A custom SVG rack stands in for
the missing server symbol on Android.
The agent sheet lists primary agents only: a session cannot run a
subagent (General, Explore) as its own agent.
Bump version to 0.1.5 (build 6).
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.
- chat: a searchable sheet picks the model or agent for the session; the
choice is applied through the server and mirrored in the session list
- sessions: a new-session sheet with a title and a working directory
(the server's default plus the directories already listed); creating
one opens its chat
- ocapi: list models with their display names and read the server's
default location
- bump version to 0.1.1 (build 2)
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