ProtoViewer agent: on-device authoring and tool surfaces¶
Not implemented. ProtoViewer has no on-device authoring agent and no tool surfaces: it shows, relaunches, resets, shares and imports prototypes written elsewhere (ProtoViewer). The draft design (a Koog authoring agent inside ProtoViewer, and tools exposed as platform modules whose surfaces are prototype specs) is an idea in the devlog entry under Background; no issues are filed for it.
Current facts that design builds on:
- Patches (
PrototypePatchinandroid/protocol,PrototypePatch.swiftinAutoMobilePrototypeAgentCore) write only under/dataand/state(add,replace,test,remove). ThereplaceNodeoperation is the only way to change the node tree. Theroot,windowandthemefields are not patchable andreplaceNodecannot replace the root; those changes need a whole-specshow. components/useexpansion exists only on the host (expandPrototypeComponentsinsrc/features/prototype/prototypeComponents.ts). Devices receive expanded specs, and the ProtoViewer import path accepts only expanded specs.library.jsonsourceis one ofmcp,file,shareorpaste, always written by the importing code and never read from bundle bytes.- The repository pins
koog-agents1.3.0, used only byandroid/junit-runner.