[P0][Workbench] Android adaptive port of the shared Workbench UI #29

New issue

Open

opened 2026-09-19 04:27:35 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-19 04:27:35 +00:00

Owner

Parent: #undefined

Ship the shared Workbench UI as an Android app using the same Tauri 2 frontend/state client.

Scope

Android app target;
phone-first navigation;
tablet/foldable multi-pane layouts;
chat, projects, modes/context, approvals, diffs, Spec/Plan/Verify, agents, history;
remote AgentProlog endpoint profiles;
background-safe connection state;
notifications for approval/question/run completion;
Android back/deep-link/share behavior where appropriate.

Constraints

No separate Android agent runtime/state machine. Android remains a frontend unless connected to the local Termux backend.

Acceptance

Same canonical session can be opened on desktop and Android.
Reconnect/resume is protocol-driven.
Android instrumentation tests cover core flows.
APK/AAB CI artifact is produced.

Parent: #undefined Ship the shared Workbench UI as an Android app using the same Tauri 2 frontend/state client. ### Scope - Android app target; - phone-first navigation; - tablet/foldable multi-pane layouts; - chat, projects, modes/context, approvals, diffs, Spec/Plan/Verify, agents, history; - remote AgentProlog endpoint profiles; - background-safe connection state; - notifications for approval/question/run completion; - Android back/deep-link/share behavior where appropriate. ### Constraints No separate Android agent runtime/state machine. Android remains a frontend unless connected to the local Termux backend. ### Acceptance - [ ] Same canonical session can be opened on desktop and Android. - [ ] Reconnect/resume is protocol-driven. - [ ] Android instrumentation tests cover core flows. - [ ] APK/AAB CI artifact is produced.