@volter-ai-dev/supercode-ui 0.1.18 → 0.1.21

package/README.md

@@ -40,6 +40,9 @@ const mounted = mountSupercodeMessenger(document.querySelector('#agent'), {
     onIntent(intent) {
       host.send(intent);
     },
+    async pickContext() {
+      return host.pickFilesAndImages();
+    },
     onClose() {
       panel.close();
     },
@@ -121,6 +124,12 @@ errors, and owned/attached identities without reimplementing transcript or capab
 `SupercodeController` snapshots and persisted inventory into it, then handles `SupercodeUiIntent`.
 The browser cannot supply locators, credentials, policy, environment variables, or arbitrary
 materialization paths. Session keys and target harnesses must be revalidated by the host.
+`pickContext` is optional and host-owned: the default composer shows one attachment control when
+this callback exists and accepts either typed text context (`detail`) or native image inputs
+(`url`). Images can also be pasted directly. The composer bounds images to four supported browser
+formats at 5 MB each, previews them locally, and keeps both attachment kinds associated with queued
+messages, retry, edit, and new-chat recovery. The host still chooses how explicit file selection
+is exposed and must revalidate every returned item.
 
 An embedding product such as Vibewaiting should therefore be small: Lucarne owns its iframe and
 launcher lifecycle, Supercode owns this UI and the controller semantics, and Vibewaiting only