sliccy 6.230.1 → 6.230.2

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.
+- **Connect MCP servers from the shell.** Use `mcp add <url> <name>` to register a server, `mcp exposure <name> direct` to expose its tools as native agent tools, or keep the default server-local QuickJS codemode tool. Direct tool names use underscores in place of hyphens; `mcp invoke` and codemode scripts still use the server's original wire names.
 - **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.