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).
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