sliccy 6.199.0 → 6.200.0

package/README.md

@@ -74,6 +74,7 @@ SLICC is for you if:
 - **Automate repetitive workflows in authenticated web apps.** Use browser automation, page inspection, screenshots, storage access, and scripted tab control where your logged-in browser session already has the context.
 - **Hand work off from another coding agent into your live browser session.** Open any URL whose response carries an RFC 8288 `Link` header with a SLICC handoff or upskill rel (the tray-hub `/handoff?handoff=...` / `?upskill=...` endpoint is a convenience) and SLICC prompts you to approve the action inside the Chat tab.
 - **Solve technical tasks with practical tools.** Reach for `bash`, `git`, `grep`, `node`, `python`, previews, and browser automation when the job is bigger than text generation.
+- **Answer agent questions from the composer.** Finished messages highlight questions in the transcript; the latest answerable question shows its choices or input above the composer text field, including the model's recommendation.
 - **Make targeted file changes with Pi's `edit` tool.** One call can apply multiple unique, non-overlapping replacements while preserving BOMs and line endings; replacement text is always literal, so `$` sequences cannot rewrite themselves through JavaScript replacement expansion.
 - **See image-producing tool results directly in chat.** Supported `<img:data:image/...;base64,...>` markers from commands such as `open --view` and `screencapture` render as bounded, lazy-loaded inline images in chat tool rows. Each tool body displays at most four images and shows an explicit overflow indication when more are present.
 - **Use a Ghostty-backed terminal.** wterm renders shell text and handles input; `imgcat photo.png` sends image bytes to its Kitty graphics preview. Other supported image and video types keep their existing media preview.
@@ -92,6 +93,7 @@ SLICC is for you if:
 - **Inspect experimental features from the avatar menu.** When centrally managed flags enable the surface for the current runtime, click your avatar and choose **Experimental features…** to open its standalone dialog. The dialog may honestly be empty: `experimental-settings` controls its availability but is not itself user-toggleable. Experimental features take effect when SLICC boots, so flipping one only matters on the next load. Changes are held until you confirm: the dialog says what is waiting and offers **Reload now** to save and apply them, or **Revert** to drop them. Nothing is written until you reload, and dismissing the dialog discards — so a flag can never end up reading `on` with nothing to show for it.
 - **Steer a running turn instead of waiting for it.** In the chat composer, `Enter` sends — including from a hardware keyboard in the native iOS follower — and queues behind whatever the cone is already doing; `Shift+Enter` inserts a newline. `Ctrl+Enter` (`Cmd+Enter` on macOS) steers: the message is injected as soon as the current step finishes, so you can redirect the agent mid-turn.
 - **Boot full x86 virtual machines in the browser.** `v86 start` runs real operating systems (Alpine, FreeDOS, KolibriOS, ...) on the wasm-based [v86](https://github.com/copy/v86) emulator, entirely client-side. The agent drives the guest from the shell — type, click, screenshot, stream the screen live, save/restore state — and `-net <model>,relay=fetch` gives the guest HTTP access through SLICC's fetch proxy. Install with `ipk add -g v86`.
+- **Run native command-line programs compiled to wasm.** A package that ships Emscripten programs (for example `ipk add -g @ai-ecoverse/wasm-pkgconf`) makes each one a shell command. Each process runs in a worker of its own, with real pipes and child processes; `wasm --list` shows what is installed. No local mount or server is needed.
 - **Delegate parallel work to scoops.** Split tasks into isolated sub-agents with their own sandboxes and context, then let the main agent coordinate the results. If a scoop hits a terminal model or provider failure, its owner gets a durable error card without spending another model call to acknowledge the outage; fatal state still bypasses mute and releases `scoop_wait`.
 - **Turn one-off wins into reusable workflows.** Package behavior as skills, build interactive sprinkles, and react to external events with webhooks and cron-driven licks.
 - **Mount your local file system.** By default, SLICC is confined to your browser. But you can ask it to mount folders from your local file system, so it can read and write from there. Mount into an empty path such as `/mnt/myproject` so you do not hide existing skills or scripts. Tear one down with `umount /mnt/myproject` (or the longer `mount unmount /mnt/myproject`). Picker mounts ask again after a page reload; for folders you always want available, map them in the launcher's mount table (`npx slicc --mount=~/Projects/foo:/mnt/foo`, or Settings → Mounts in Sliccstart.app) and they are mounted automatically on every launch, with no picker or permission prompt — see [Auto-mounted host folders](docs/mounts.md#auto-mounted-host-folders-the-mount-table).

package/dist/node-server/cloud-status.d.ts

@@ -1,4 +1,11 @@
 import { type Express, type NextFunction, type Request, type Response } from 'express';
+/** e2b sandboxes poll this path. A host with several leaders sets `SLICC_JOIN_FILE`. */
+export declare const DEFAULT_JOIN_FILE_PATH = "/tmp/slicc-join.json";
+/**
+ * Join file for `POST /api/cloud-status`. `SLICC_JOIN_FILE` wins so each
+ * leader on one host writes its own file; unset keeps the sandbox default.
+ */
+export declare function resolveJoinFilePath(env?: NodeJS.ProcessEnv): string;
 export interface CloudStatusEndpointOptions {
     joinFilePath: string;
 }

package/dist/node-server/cloud-status.js

@@ -1,6 +1,16 @@
 import { promises as fs } from 'node:fs';
 import { isLoopbackHostname } from './_shared/index.js';
 import express from 'express';
+/** e2b sandboxes poll this path. A host with several leaders sets `SLICC_JOIN_FILE`. */
+export const DEFAULT_JOIN_FILE_PATH = '/tmp/slicc-join.json';
+/**
+ * Join file for `POST /api/cloud-status`. `SLICC_JOIN_FILE` wins so each
+ * leader on one host writes its own file; unset keeps the sandbox default.
+ */
+export function resolveJoinFilePath(env = process.env) {
+    const configured = env.SLICC_JOIN_FILE?.trim();
+    return configured || DEFAULT_JOIN_FILE_PATH;
+}
 /** The optional string fields validated when present but never required. */
 const OPTIONAL_STRING_FIELDS = [
     'trayId',

package/dist/node-server/index.js

@@ -26,7 +26,7 @@ import { runPause } from './cloud/pause.js';
 import { FileRegistry } from './cloud/registry-file.js';
 import { runResume } from './cloud/resume.js';
 import { runStart } from './cloud/start.js';
-import { registerCloudStatusEndpoint } from './cloud-status.js';
+import { registerCloudStatusEndpoint, resolveJoinFilePath } from './cloud-status.js';
 import { ComputerDemoState, createComputerDemoFrameServer, handleComputerDemoUpgrade, registerComputerDemoRoutes, } from './computer-demo.js';
 import { ElectronAppAlreadyRunningError, ElectronOverlayInjector, launchElectronApp, resolveOverlayThinBridge, } from './electron-controller.js';
 import { getElectronAppPorts } from './electron-runtime.js';
@@ -1254,12 +1254,12 @@ async function main() {
     // Secret management API — direct .env file access (no browser needed),
     // plus the S3 / DA sign-and-forward and masked-secret endpoints.
     registerSecretRoutes(app, { secretStore, secretProxy, oauthStore, devMode: false });
-    // Cloud status endpoint (hosted-only) — writes join info to /tmp/slicc-join.json
+    // Cloud status (hosted-only). Writes SLICC_JOIN_FILE, else /tmp/slicc-join.json.
     // Register BEFORE Chromium launches. The webapp's first action after
     // ?runtime=hosted-leader boot is to mint a tray and POST /api/cloud-status.
     // If the route doesn't exist yet, the post 404s and the CLI poll times out.
     if (RUNTIME_FLAGS.hosted) {
-        registerCloudStatusEndpoint(app, { joinFilePath: '/tmp/slicc-join.json' });
+        registerCloudStatusEndpoint(app, { joinFilePath: resolveJoinFilePath() });
         registerHostedBootstrapEndpoint(app, { secretStore });
         registerSecretsReloadEndpoint(app, { secretProxy, secretStore, oauthStore });
     }