@abot-ai/runtime 1.3.1 → 1.5.0

package/dist/src/web-ui/app/ARCHITECTURE.md

@@ -19,6 +19,17 @@ Controllers and components communicate through injected callbacks or values. The
 
 `workspace-shell.js` is the single owner of workspace navigation. It owns the active Home, Chat, Schedules or Config workspace, responsive Conversations visibility, focus restoration, Escape handling, backdrop state, and related ARIA attributes. `conversation-sidebar-layout.js` resolves the sidebar presentation policy; `operations-section.js` owns the internal Runtime, Logs, and Health tabs within Configuration. These components must not own session data, request state, or Runtime transport.
 
+`workspace-route-controller.js` owns the browser address projection and history
+restoration; `lib/workspace-route.js` owns address parsing and serialization.
+The four workspace paths reuse the existing server fallback. Environment is
+explicit, with a Chat session, Configuration category and Operations tab, or
+saved schedule Job when relevant. Bootstrap validates the URL environment before
+loading its data, then restores the addressed view. Route application uses the
+existing shell, environment, conversation and schedule controllers and respects
+their guards. Environment transitions suppress intermediate history entries;
+rejected Back or Forward navigation restores the accepted history entry. The URL
+never contains drafts, credentials, approval choices, or mutation payloads.
+
 `conversation-activity.js` owns only request-scoped activity presentation. `realtime-event-controller.js` preserves sequence authority, associates events and progress with their exact `requestId`, and injects those values into the conversation view. `realtime-transport.js` only parses and transports frames; it does not reduce application state.
 
 `composer-context-window.js` presents the existing context estimate as one compact composer indicator. It selects the active assistant request, or the newest conversation message only when it is a request-linked assistant message while idle. A pending user turn, an assistant message without a request ID, or missing metrics hides the indicator instead of falling back to an earlier request. Context metric updates refresh it independently of message tokens; session-view resets clear it. Estimated usage, provider-reported usage, and compaction remain distinct, and provider usage stays bound to the matching model invocation.
@@ -48,6 +59,17 @@ the completion-event boundary: tool output, canonical evidence and model context
 are unchanged. The Web UI does not fetch a file or memory record again to recreate
 historical evidence. Passive Runtime memory remains outside tool activity.
 
+`tool-process-activity-fields.js` projects declared process display fields without
+branching on tool identities. Opted-in commands retain up to 4,096 characters and
+whitespace; shared `conversation-tool-evidence.js` renders them as inert
+preformatted text in both activity and approval disclosures. Working
+directory, target, exit code and recorded process evidence remain distinct from
+model-authored intent. Result output stays a bounded excerpt, and completion or
+exit zero does not establish an application window or independent outcome check.
+Terminal failures preserve recorded result fields and clipping flags. Old events
+without declared input/output evidence remain unavailable; the UI never guesses
+commands from rationale or opaque parameter summaries.
+
 Web sources appear in a separate Activity section alongside role cards and the event timeline. `web-source-event.js` projects only successful `web_search` and `web_fetch` completions; `web-sources.js` validates bounded plugin receipts and groups them by recorded call. `conversation-sources.js` renders links and retrieval/presentation states without interpreting answer text. Source-bearing events retain their own identity before display grouping, and stored session events use the same projection as live events. Session switching clears them with the existing Activity state.
 
 The optional `meta.webSources` version 1 receipt describes the final bounded **tool output**, not whether a later model invocation consumed or cited it. Older events can show found/fetched URLs with unknown output visibility; absent or unsupported receipts never imply full content. Favicons are best-effort browser requests to the source origin's `/favicon.ico`, loaded lazily with no referrer and a local fallback. No third-party icon service or server proxy is used. Source URL policy rejects unsafe schemes and credentials, and prevents automatic image loads for local/private IP literals; origin DNS, redirects, cookies, and browser image policy remain browser concerns. Icons carry no evidence and never block tool execution.
@@ -72,7 +94,7 @@ Panel resizing and persisted panel widths are intentionally not part of this arc
 
 `composer-workspace-controller.js` moves the existing composer DOM between Home and Chat and isolates their draft text and attachments. `composer-surface-controller.js` routes input, rendering and attachment actions to the active surface. Both surfaces use the same attachment and submission controllers; background Chat queue work writes to its own input surface. Home submission adopts its draft into a new conversation before invoking the ordinary Chat request controller. Home navigation alone never resets or reads the active conversation. `conversation-read-state-controller.js` rechecks visible Chat, environment, session and view revision before marking persisted assistant messages read.
 
-Dashboard Job suggestions are inert data in `dashboard-job-templates.js`. They open the ordinary schedule form with editable defaults, a selected model, device time zone and a new dedicated conversation target. Only explicit Save creates state. `schedule-job-creation.ts` adapts this Web-only target into an owner-created conversation and the existing scheduler contract; it never invokes the model. Existing-conversation creation remains supported. `configuration-feature.js` owns the composition of Configuration and its memory controls. `app-bootstrap.js` owns startup ordering, environment restoration, initial loading and Home activation.
+Dashboard Job suggestions are inert data in `dashboard-job-templates.js`. They open the ordinary schedule form with editable defaults, a selected model, device time zone and a new dedicated conversation target. Only explicit Save creates state. `schedule-job-creation.ts` adapts this Web-only target into an owner-created conversation and the existing scheduler contract; it never invokes the model. Existing-conversation creation remains supported. `configuration-feature.js` owns the composition of Configuration and its memory controls. `app-bootstrap.js` owns startup ordering, environment restoration, initial loading and route-controller composition; an unaddressed start activates Home.
 
 Read tracking belongs only to the native Web UI backend. `session-read-state/service.ts` reads canonical session snapshots and projects unread assistant replies; `store.ts` persists the UI cursors in an environment-specific sidecar under `runtimeDir/web-ui/read-state/`. Runtime session files, model context and Runtime contracts remain unchanged. A persisted initialization timestamp treats existing history as read and tracks later replies, including newly created Job conversations. Read acknowledgements resolve only the displayed persisted assistant message or its exact completed request ID. Cursors advance monotonically and survive server restarts; invalid boundaries never acknowledge unseen replies. Browser consumers retain newer read revisions when older responses arrive late.
 
@@ -80,6 +102,36 @@ The native conversation list uses the existing `SessionService` disk reader and
 
 Read-state persistence is an optional Web UI projection. `session-read-state/availability.ts` isolates sidecar failures from listing, loading, clearing and deleting conversations. A failure returns `readStateStatus: "unavailable"` and unknown counts, preserves the sidecar for diagnosis, and leaves read acknowledgements unsuccessful. The browser keeps the last known receipt, labels unavailable tracking explicitly and resumes normal counts after a healthy list refresh. Canonical session and attachment failures remain errors. Workspace visibility is committed before change callbacks attempt to acknowledge visible messages, including drawer closure and responsive layout changes.
 
+## Conversation file preview
+
+`conversation-file-reference.js` projects only explicit successful file-output
+receipts from tool events. Activity keeps this reference separate from the
+historical sent/received fields and excerpt. `conversation-file-action.js` makes
+the existing filename an inline preview control inside the tool summary. Its click suppresses disclosure activation;
+other summary interactions retain the recorded evidence disclosure.
+
+`conversation-file-preview-controller.js` owns scoped loading and stale-response
+rejection. The feature adapter mounts the viewer outside the message subtree and
+preserves conversation scroll while the layout changes. Session resets and
+workspace departure close it; responsive focus and Escape behavior belong to
+`conversation-file-focus.js`. Transport stays in the conversation-files service.
+
+The local backend's `conversation-file-access.ts` admits only a saved or scoped
+active completion belonging to the requested environment, session and request.
+`conversation-file-target.ts` owns the held file and root/containment identity
+checks shared by content reads and native opening. The route revalidates request
+generation and completion before returning bytes or handing off to a Mac app.
+`conversation-file-native-request.ts` limits native opening to same-origin JSON
+POSTs from a local browser on macOS. `conversation-file-native-open.ts` restricts
+file types and invokes the fixed OS opener without a shell. The viewer exposes
+this action only when its preview response includes `nativeOpenAvailable: true`;
+its controller scopes busy/failure feedback to the selected file. The OS app
+resolves the original pathname after handoff; that asynchronous read is outside
+the preview reader's held-descriptor guarantee. The receipt
+is presentation-only: the optional filesystem report callback feeds event
+metadata, never the canonical tool result or model context. No file registry or
+historical content snapshot is created.
+
 ## Styles
 
 `styles.css` is the ordered manifest. The modules under `styles/` own:
@@ -97,15 +149,19 @@ Keep responsive overrides last and avoid moving declarations between modules wit
 
 Visual components may format or group events, but they never accept transport frames or construct Runtime API payloads. Realtime frame parsing belongs to `realtime-transport.js`; request sequence and terminal-state reduction belong to `realtime-event-controller.js`; endpoint construction and HTTP payload serialization belong to `runtime-web-client.js` and its feature request modules; and feature controllers own when those operations occur. Config remains explicit-save; presentation changes must never introduce autosave.
 
-
 ## Core schedules
 
 `schedules-feature.js` composes the scheduler browser feature from its controller,
 transport requests and presentation. `schedules-controller.js` owns loading and
 management actions scoped to the selected environment, guards stale reads, and
-refreshes only while the workspace is active and no editor or mutation is pending.
+refreshes from committed server changes while the workspace is active and visible.
+The event refresh queue coalesces bursts and preserves changes received during
+reads or mutations; reconnection and visibility return reconcile missed changes.
+Background updates retain the open editor and the selected run-history page.
 The full Schedules workspace shares the shell navigation and discard guards;
-its editor uses an explicit save and a saved model/mode with Full tool access.
+its editor uses an explicit save and a saved model/mode with selectable Full or
+FULL+ tool access. Full remains the default; FULL+ must be selected explicitly.
+The run history shows the permission captured for each invocation.
 Unchanged timing fields are omitted from edits, preserving the original timer or
 interval anchor when only a title, prompt or model changes.
 
@@ -125,3 +181,104 @@ run identity before activating the ordinary realtime request lifecycle. Duplicat
 trigger delivery cannot add another user message or reactivate a completed run.
 The scheduler page and chat card are presentation-only consumers; the runtime
 scheduler remains the sole owner of Job state and dispatch decisions.
+
+## Interactive setup and configuration activation
+
+The setup guide composes focused rendering/validation modules and receives
+configuration transport callbacks. Runtime onboarding retains catalog authority
+over chat readiness. Home suppresses its dashboard data and shortcuts while
+setup is required; the guide has one scroll owner in either Home or Chat.
+OpenAI credentials live only in the current password input and one save payload.
+They never enter browser state, HTML attributes, preferences or control logs.
+
+The setup sequence is Provider, Connection, Embedding, Plugins and Ready.
+The onboarding feature assembles transport dependencies outside app.js; focused
+step modules own embedding and plugin card selection. Chat connection writes
+defer activation in the wizard, while ordinary setup API callers retain their
+existing immediate-activation behavior. The pending-activation gate keeps the
+catalog unavailable until the explicit final apply, including browser reload in
+the same Web process. Optional choices are read back from canonical saved files.
+
+Embedding setup prepares only the requested provider and its private credential,
+then delegates to the existing memory probe-before-save service. Probe dimensions
+and fingerprints come from the provider response; the UI never invents them.
+Provider preparation may survive a later probe failure, which is reported without
+exposing credentials. The memory Web router resolves the current configuration
+path per request so first-time setup uses local/runtime.config.json correctly.
+Plugin cards reuse the existing manifest selection API, preserving sibling tools
+and saved policies. Fresh installations start with all plugins and tools selected.
+The onboarding plugin cards display every tool checkbox directly. Their dedicated
+stylesheet widens only this step and keeps the outer workspace as the scroll owner.
+
+Configuration composes a plugin manager using the canonical manifest selection
+projection. The separate activation control explicitly applies saved files.
+The server checks synchronous owner admission, refuses busy or externally owned
+environments, and refreshes its gateway through the owning lifecycle callback.
+Browser reload and saved selection are not evidence of live activation.
+
+### Additive model setup
+
+Configuration composes a separate Provider / Model / Ready dialog in
+components/model-setup/. It shares the wizard shell and connection form with
+first setup, while retaining its own additive save/apply lifecycle. The dialog
+is outside the dashboard so refresh and mutation locking cannot detach it.
+An entered API key remains only in the mounted password field until final save;
+review and back navigation do not copy it into state or markup.
+
+configuration-feature.js guards opening against existing configuration drafts,
+blocks workspace/environment navigation while the dialog is open, and holds the
+external mutation lock during save, Apply and refresh. Saved model identity
+survives Apply failure; successful Apply survives refresh failure. Completion
+refreshes Memory provider choices and chat models, selects the new profile, and
+focuses it only after closing the modal and releasing the lock.
+Deferred activation refreshes the saved declaration without marking it active or
+refreshing the active chat catalog. The dialog distinguishes saved/pending status
+from save failures, and closing it does not undo the saved declaration.
+
+local-runtime/model-setup-\* owns catalog/input/credential/addition behavior.
+It uses the canonical configuration repository and shared CLI merge helper,
+preserving existing profiles, references, defaults and connection settings.
+Only new OpenAI/Ollama connections are created here; existing provider IDs are
+resolved by adapter type. The transport exposes no secret values and requires
+the same-origin JSON mutation guard. This flow does not invoke a model.
+
+New Web additions use a model file and `configRef`; existing inline profiles
+remain supported. Declaration removal uses the canonical Runtime lock and loaded
+root revision, validates the remaining configuration for every environment, and
+keeps referenced files, providers and credentials. Discovered files without a
+declaration remain editable and are explicitly marked as not registered.
+
+## Projects and permission modes
+
+`projects-feature.js` composes project UI; `projects-controller.js` owns project
+and folder loading, creation and stale-response rejection. Presentation modules
+render the creation form and sidebar groups, while `runtime-web-client/projects.js`
+owns transport. The folder form occupies the chat canvas without resetting the
+active conversation or draft. It closes the file viewer through its existing
+presentation lifecycle. Creation calls the owner API; a saved project session is
+opened through the canonical conversation controller without a model request.
+
+The session controller remains the owner of session row actions and read state.
+Its injected group renderer places project groups above ordinary conversations,
+including projects with no sessions. The session's saved project snapshot also
+provides the visible working-folder label. Neither project presentation nor client
+request payloads overwrite global runtime paths.
+
+`tool-permission-mode-controller.js` owns the permission selector and explicit
+per-session preference changes; `lib/tool-permission-mode.js` owns known browser
+values and server compatibility. FULL+ requires advertised server support, and
+transport rejects unsupported requests without a silent downgrade. The existing
+composer queue keeps its captured mode. Project membership never selects FULL+.
+`app-state.js` constructs the same one shared browser state identity for `app.js`.
+
+Home approvals reuse the local Web transport's live approval promises through
+`GET /chat/approvals`. An explicit decision POST binds the environment, session,
+request and approval identities and rechecks live ownership before resolving it.
+The dashboard controller discards old-environment responses; discovery and
+approval never load or mark a conversation as read. External bridge connections
+show that Home discovery is unavailable. The shared approval card keeps recorded
+execution evidence visible and places the complete rationale in a native disclosure.
+
+Startup keeps the app inert and hidden from the initial HTML until workspace
+restoration finishes. The branded startup screen reveals the app once ready;
+failed bootstrap reads remain on an error with an explicit Reload action.

package/dist/src/web-ui/app/app-bootstrap.js

@@ -1,3 +1,5 @@
+import { createStartupScreen } from "./components/startup-screen.js";
+import { createWorkspaceRouteController } from "./controllers/workspace-route-controller.js";
 import { textOf } from "./lib/text-format.js";
 
 export async function bootstrapWebApp({
@@ -7,7 +9,10 @@ export async function bootstrapWebApp({
   shell,
   homeComposer,
   dashboard,
+  learning,
+  notifications,
   schedules,
+  projects,
   selection,
   client,
   bindables,
@@ -18,7 +23,26 @@ export async function bootstrapWebApp({
   configuration,
   realtime,
   restoreLastSession,
+  navigation,
+  onNavigationReady = () => {},
 }) {
+  const routes = navigation
+    ? createWorkspaceRouteController({
+        shell,
+        configuration,
+        selection,
+        schedules,
+        getEnvironmentId: () => dom.environmentSelect.value,
+        getSessionId: () => state.currentSessionId,
+        changeEnvironment: navigation.bindings.changeEnvironment,
+        isEnvironmentChanging: navigation.bindings.isEnvironmentChanging,
+        loadSessions: navigation.conversation.loadSessions,
+        openSession: navigation.conversation.openSession,
+        restoreLastSession,
+      })
+    : null;
+  onNavigationReady(routes);
+  routes?.bind();
   selection.loadPreferences();
   shell.load();
   homeComposer.setWorkspace(shell.activeWorkspace());
@@ -29,25 +53,47 @@ export async function bootstrapWebApp({
   selection.renderPermissionMode();
   renderMessages();
   state.config = await client.loadWebConfig();
+  void configuration.refreshComputerAccess?.();
   schedules.refreshAvailability();
+  notifications?.refreshAvailability();
+  projects?.refreshAvailability();
   selection.renderEnvironmentOptions();
   const options = selection.environmentOptions();
   const saved = preferences.environmentId();
   const fallback =
     textOf(state.config.defaultEnvironmentId).trim() || options[0]?.value || "";
   const hasSavedEnvironment = options.some((option) => option.value === saved);
-  dom.environmentSelect.value = hasSavedEnvironment ? saved : fallback;
+  dom.environmentSelect.value = routes
+    ? routes.bootstrapEnvironment(options, saved, fallback)
+    : hasSavedEnvironment
+      ? saved
+      : fallback;
   preferences.saveEnvironmentId(dom.environmentSelect.value);
+  learning?.environmentChanged();
+  learning?.setWorkspace(shell.activeWorkspace());
   homeComposer.environmentChanged();
   selection.renderAgentPicker();
   realtime.connect();
   await Promise.allSettled([
+    projects?.load(),
     selection.loadModels(),
     selection.loadAgentMode(),
     operations.loadRuntimeStatus(),
     operations.loadSystemHealth(),
     configuration.load(),
   ]);
-  await restoreLastSession();
+  if (routes) await routes.restoreInitial();
+  else await restoreLastSession();
   dashboard.setReady();
+  notifications?.setReady();
+}
+
+export async function startWebApp(options) {
+  const startup = createStartupScreen();
+  try {
+    await bootstrapWebApp(options);
+    startup.ready();
+  } catch (error) {
+    startup.fail(error);
+  }
 }

package/dist/src/web-ui/app/app-dom.js

@@ -15,7 +15,29 @@ export function findAppDom(documentRoot = document) {
       "closeSchedulesWorkspaceButton",
     ),
     schedulesRoot: documentRoot.getElementById("schedulesRoot"),
+    learningWorkspaceButton: documentRoot.getElementById(
+      "learningWorkspaceButton",
+    ),
+    learningWorkspacePanel: documentRoot.getElementById(
+      "learningWorkspacePanel",
+    ),
+    closeLearningWorkspaceButton: documentRoot.getElementById(
+      "closeLearningWorkspaceButton",
+    ),
+    learningRoot: documentRoot.getElementById("learningRoot"),
+    memoryWorkspaceButton: documentRoot.getElementById("memoryWorkspaceButton"),
+    memoryWorkspacePanel: documentRoot.getElementById("memoryWorkspacePanel"),
+    openMemoryRestartControlsButton: documentRoot.getElementById(
+      "openMemoryRestartControlsButton",
+    ),
+    closeMemoryWorkspaceButton: documentRoot.getElementById(
+      "closeMemoryWorkspaceButton",
+    ),
+    memorySetupRoot: documentRoot.getElementById("memorySetupRoot"),
+    memoryManagementRoot: documentRoot.getElementById("memoryManagementRoot"),
     configWorkspaceButton: documentRoot.getElementById("configWorkspaceButton"),
+    modelsWorkspaceButton: documentRoot.getElementById("modelsWorkspaceButton"),
+    pluginsWorkspaceButton: documentRoot.getElementById("pluginsWorkspaceButton"),
     chatPanel: documentRoot.querySelector(".chat-panel"),
     sessionsPanel: documentRoot.querySelector(".sessions-panel"),
     configWorkspacePanel: documentRoot.getElementById("configWorkspacePanel"),
@@ -26,6 +48,8 @@ export function findAppDom(documentRoot = document) {
     environmentSelect: documentRoot.getElementById("environmentSelect"),
     agentPickerButton: documentRoot.getElementById("agentPickerButton"),
     agentPickerMenu: documentRoot.getElementById("agentPickerMenu"),
+    newProjectButton: documentRoot.getElementById("newProjectButton"),
+    projectCreationRoot: documentRoot.getElementById("projectCreationRoot"),
     newSessionButton: documentRoot.getElementById("newSessionButton"),
     refreshSessionsButton: documentRoot.getElementById("refreshSessionsButton"),
     closeSessionsButton: documentRoot.getElementById("closeSessionsButton"),
@@ -33,6 +57,7 @@ export function findAppDom(documentRoot = document) {
     sessionSearchInput: documentRoot.getElementById("sessionSearchInput"),
     sessionsCount: documentRoot.getElementById("sessionsCount"),
     sessionsList: documentRoot.getElementById("sessionsList"),
+    currentProjectContext: documentRoot.getElementById("currentProjectContext"),
     sessionTitle: documentRoot.getElementById("sessionTitle"),
     agentModeButton: documentRoot.getElementById("agentModeButton"),
     agentModeMenu: documentRoot.getElementById("agentModeMenu"),
@@ -55,6 +80,7 @@ export function findAppDom(documentRoot = document) {
     composerPlan: documentRoot.getElementById("composerPlan"),
     composerSubmitControl: documentRoot.getElementById("composerSubmitControl"),
     sendButton: documentRoot.getElementById("sendButton"),
+    stopButton: documentRoot.getElementById("stopButton"),
     sendButtonLabel: documentRoot.getElementById("sendButtonLabel"),
     sendNextMenuButton: documentRoot.getElementById("sendNextMenuButton"),
     sendNextMenu: documentRoot.getElementById("sendNextMenu"),

package/dist/src/web-ui/app/app-page-bindings.js

@@ -0,0 +1,46 @@
+import { bindRuntimeSetupPageLifecycle } from "./runtime-setup-page-lifecycle.js";
+
+export function bindWebAppPageLifecycle({
+  appEventBindings,
+  page,
+  documentRoot,
+  environmentSelect,
+  disposeRuntimeSetup,
+  reloadModels,
+  markSessionRead,
+  environmentChanged,
+  visibilityChanged,
+}) {
+  appEventBindings.bind();
+  bindRuntimeSetupPageLifecycle({
+    page,
+    dispose: disposeRuntimeSetup,
+    reloadModels,
+  });
+  documentRoot.addEventListener("visibilitychange", markSessionRead);
+  documentRoot.addEventListener("visibilitychange", visibilityChanged);
+  environmentSelect.addEventListener("change", environmentChanged);
+}
+
+export function bindWebAppWorkspaceLifecycle({
+  appEventBindings, dom, runtimeSetupGuide, reloadModels, conversationSession,
+  homeComposer, dashboardFeature, passiveLearning, notifications, operations,
+}) {
+  bindWebAppPageLifecycle({
+    appEventBindings,
+    page: window,
+    documentRoot: document,
+    environmentSelect: dom.environmentSelect,
+    disposeRuntimeSetup: runtimeSetupGuide.dispose,
+    reloadModels,
+    markSessionRead: conversationSession.markCurrentSessionReadSoon,
+    environmentChanged: () => {
+      homeComposer.environmentChanged();
+      dashboardFeature.environmentChanged();
+      passiveLearning.environmentChanged();
+      notifications.environmentChanged();
+      operations.environmentChanged();
+    },
+    visibilityChanged: passiveLearning.visibilityChanged,
+  });
+}

package/dist/src/web-ui/app/app-realtime-transport.js

@@ -0,0 +1,42 @@
+import { createRealtimeTransport } from "./services/realtime-transport.js";
+
+export function createAppRealtimeTransport({
+  state,
+  getConfig,
+  onMessage,
+  setConnectionLabel,
+  rejectPendingSteers,
+  recordControlEvent,
+  onConnected,
+}) {
+  return createRealtimeTransport({
+    getConfig,
+    onMessage,
+    onOpen: () => {
+      state.connected = true;
+      setConnectionLabel("Connected");
+      onConnected();
+    },
+    onClose: () => {
+      state.connected = false;
+      rejectPendingSteers(
+        "Realtime connection closed before steer was accepted.",
+      );
+      setConnectionLabel("Reconnecting", true);
+    },
+    onError: () => {
+      state.connected = false;
+      setConnectionLabel("Connection issue", true);
+    },
+    onParseError: (error, preview) => {
+      recordControlEvent({
+        type: "control",
+        name: "Realtime parse error",
+        tone: "failed",
+        summary: `${error instanceof Error ? error.message : String(error)}${
+          preview ? `: ${preview}` : ""
+        }`,
+      });
+    },
+  });
+}

package/dist/src/web-ui/app/app-state.js

@@ -0,0 +1,39 @@
+export function createAppState() {
+  return {
+    config: null,
+    connected: false,
+    sessions: [],
+    pinnedSessionIds: [],
+    sessionModes: {},
+    sessionModels: {},
+    lastModelByEnvironment: {},
+    agentMode: "reasoning",
+    supportedAgentModes: ["fast", "reasoning", "deep", "auto"],
+    agentModeMenuOpen: false,
+    permissionModeMenuOpen: false,
+    agentPickerOpen: false,
+    busySessionIds: new Set(),
+    messages: [],
+    events: [],
+    taskProgressByRequest: new Map(),
+    contextWindowByRequest: new Map(),
+    submittedToolApprovalIds: new Set(),
+    requestMessages: new Map(),
+    requestLifecycles: new Map(),
+    currentSessionId: "",
+    activeRequestId: "",
+    sessionViewVersion: 0,
+    lastSeqByRequest: new Map(),
+    modelProfiles: [],
+    defaultModelProfileId: "",
+    runtimeAvailability: { status: "loading" },
+    pendingAttachments: [],
+    pendingAttachmentUploadCounts: new Map(),
+    composerAttachmentGeneration: 0,
+    composerSending: false,
+    composerQueueDrainingScopes: new Set(),
+    composerQueueRecoveredReleaseTokens: new Set(),
+    activeComposerQueueRecovery: null,
+    sessionQuery: "",
+  };
+}