Switchboard 0.4.8

• Added icon-only Copy under each user question and AI answer, plus Salin percakapan in the side-panel header. Accessible labels and tooltips differentiate copying a question, answer, or entire chat. Clipboard output is original plain text (not rendered HTML); conversation copy contains visible user and AI messages only, omitting browser tool details, internal errors, and API keys. New Chat clears the copy source. Both Cloud and optional local agent paths use the same copy controls.

Release candidate — unpublished; Chrome Web Store 0.4.7 submission is a different, earlier build.

• Standalone side-panel tab manager: + Tab attaches one of the currently open HTTP(S) tabs, list enables selecting/switching among up to 12 attached tabs, Hapus detaches a tab without closing it. No implicit fallback to an unrelated active Chrome tab after detaching. Cloud model tools cannot select/unbound or override a user-selected tab.
• BotConnector Cloud now runs directly in the Chrome side panel, with an extension-local BYOK configuration, fixed HTTPS inference gateway, and an agent tool loop using the existing browser tool executor and native Chrome per-site permissions. The AI picker reuses the authenticated BotConnector /v1/models catalog and BCCLI capability labels: searchable Free/Paket verified-tool model dropdown, refresh action, and quick model switching in the chat composer without API-key re-entry. No Switchboard CLI, Web Console, or pairing required. Browser actions request explicit operator confirmation; failed/uncertain mutations are not retried. API keys stay in trusted extension-local storage and may be removed in-panel. New privacy disclosures and standalone Chrome regression coverage.

Switchboard 0.4.7

• The Chrome side panel now has a Provider / Model ID / API key form for BotConnector Cloud, OpenRouter and Groq. BotConnector uses the fixed first-party HTTPS gateway https://api.botconnector.id/v1 with agnes-3.0-flash as its initial model ID. Saving uses independent, one-use approval in the authenticated Web Console; the key is never written to extension storage and the companion bearer never gains access to general settings.

• Advanced provider settings still open the existing local Settings → Models form. Secrets typed into the side-panel BYOK field are only handled transiently in memory, never persisted in the extension.

• Add a read-only extract-data prompt shortcut. Preserve the current chat-first panel, native Chrome site permissions, and Manual/Auto/Skip semantics.

• Make workflow recording opt-in for successful agent click, scroll, and navigation actions, without recording typed values or sensitive URL query strings. Safely import/export bounded JSON, cancel replay after the in-flight action, and never retry uncertain clicks. High-risk selectors and actual click labels are screened (after Chrome site permission); replay clicks require an explicit operator review. Replay refuses to take over an unbound personal tab.

• Add a compact task result footer distinguishing tool-reported success, failed steps, cancellation, step limit, and answers without tool evidence; it does not claim independent verification.

• Reuse the existing real Chrome agent E2E for an opt-in Cloud provider run with strictly scoped approvals and credential-safe env configuration. A bounded Qwen 3.8 Flash / OpenRouter run passed live Chrome DOM verification and reconnect without a duplicate click.

• Add repeatable task UX tests and opt-in visible-Chrome acceptance. None of these changes are included in the published 0.4.6.

Switchboard 0.4.6

• Stop losing data or the host: a cancelled tool batch now answers every tool_call id, an unreadable automations.json is never overwritten and one bad schedule cannot exit the process, CI run records are written atomically and privately, and a session larger than the reader limit keeps its newest turns plus a searchable archive instead of vanishing.
• Browser safety: "allow for this session" now applies to the granted tool in that session (screenshots, downloads and page quarantine still ask every time), pre-auth pairing bodies are capped at 64 KB, a quarantined page withholds its title and selectors, and a download is attributed only to the approved tab and origin.
• Report failures instead of faking success: provider timeouts say request timed out after Ns, a stream cut before its terminal marker is rejected, an empty model answer fails the run instead of storing a canned sentence, and a workflow with an older running run no longer starts a second copy.
• Chat accepts the four ~5 MB images it documents (body cap raised, oversize mapped to 413).
• Console: status chips and counts meet 4.5:1 in light and dark, the delete button meets the 24×24 target, and the Run trace pane has empty and error states.

Switchboard 0.4.5

• Harden local trust boundaries: project-local CI is disabled by default behind an explicit per-project trust decision, runs only a base environment plus ci.envAllowlist, and executes steps in the configured sandbox.
• Make the paired browser companion token browser-scoped: it cannot start shell-capable chats, settle non-browser approvals, or change the action mode through extension status updates.
• Require browser selectors to exist in the current snapshot; screenshots and downloads always require explicit approval; pairing uses mutual HMAC challenge-response with AES-GCM token delivery; trace session keys reject path traversal.
• Let the side panel discover the console origin advertised by the paired server (webOrigin), so sbx web --port <n> keeps Ask, approvals and Stop working without a hardcoded 7777; loopback http: origins only, with a visible fallback for older servers.
• Enable CDP focus emulation (Emulation.setFocusEmulationEnabled) inside withDebugger so browser_click and browser_key reliably deliver trusted mouse and key events in Chrome and Microsoft Edge even when the bound agent tab is in the background or the browser window is unfocused/occluded on Windows.
• Refuse shell/credential-capable presets in unattended automations unless allowUnattended: true; verify documentation and extension manifest versions against package.json in tests.

Switchboard 0.4.4

• Fix Windows portable startup by resolving the same pinned BotConnector Local Core from either the npm vendor path or the portable sibling local-core folder, without duplicating model managers.
• Add portable smoke checks for Core CLI and model recommendations.

Switchboard 0.4.3

• Improve browser Auto safety checks with compact local-model verdicts and fail-closed prompt-injection quarantine; preserve Chrome site permissions.
• Add hardware-informed AI Lokal model recommendations using the original BotConnector Local Core catalog and hardware probes.
• Separate installed GGUF from running GGUF; add explicit Plug/Unplug and launch of original Local Core download/runtime manager without automatic downloads.
• Fix Settings panel navigation clipping on desktop and mobile; suppress inappropriate Browser Companion onboarding banner.
• Add npmjs stable release checks, one-click manual update and opt-in automatic update every six hours, with no forced restart and no silent updates of Windows portable installations.

Switchboard 0.4.2

• Bundle the original, pinned BotConnector Local Core in the same @botconnector/switchboard npm installation and Windows portable bundle, with no second model manager and no automatic GGUF downloads.
• Add sbx local and sbx local status to access the upstream model manager and runtime checks; retain the established sbx web entry point.
• Integrate explicitly selected local models into the existing Settings > Models panel, with loopback-only inference and fail-closed safeguards against Cloud fallback.
• Verify Windows native GGUF text inference and initial vision OCR, npm global installation, portable fresh-profile smoke, and Node 20/22 GitHub CI. Model-specific vision accuracy and full browser-agent GGUF parity remain experimental.
• Improve local Core CLI process shutdown and provide npm tarball acceptance tests.

Switchboard Browser Companion v0.4.4

Switchboard Browser Companion 0.4.4 — public release candidate

Date: 15 October 2026. Owner explicitly requested immediate launch after reviewing QA gaps.

Identity

• Chrome Web Store existing item ID: miehnbiiokkciokmepnhgmlhjpabbkna; installed in owner's primary Chrome with from_webstore=True, location=1, update_url=https://clients2.google.com/service/update2/crx, prior version 0.4.3.
• Update same item, not a duplicate. Manifest update version 0.4.4.
• Artifact: switchboard-chrome.zip (51,817 bytes), SHA-256 b230f3f36bce5c775a139e67e4a3b3cce31f272c57813c4caa920a1015be7994 (candidate built from branch before final merge; re-check exact published ZIP).
• scripts/verify-browser-store-zip.py PASS: eight expected files, matching audited source, images and root manifest valid. Chrome and Edge ZIP built from identical source.
• No change to NPM package version 0.4.1; Browser Companion update is not a CLI/NPM release.

Changes included

• Chrome's native single-use per-site grant is requested from an explicit panel user gesture. Grant is removed after one tool; second action requests grant again. No second permission gate.
• Browser screenshot JPEG is sent only on explicit visual user intent, as an ephemeral untrusted attachment to the configured model; never as base64 in chat or persisted session. Malformed/overlong/non-HTTP screenshot results fail closed.
• Screened DOM snapshot retains heading levels and non-sensitive control labels, enabling correct H1/button answers without bypassing page safety.
• Side-panel chat error and Stop outcomes, Auto multi-step recovery and tab-bound interactions from prior acceptance work.

Acceptance

• Windows npm test, npm run build, npm run typecheck PASS at prior head; combined Node 20/22 GitHub CI PASS on 7b5c206.
• True headed Chrome service worker, authenticated pairing, native user-granted Allow once → single DOM tool → automatic native revoke → second-action Deny: PASS. A native Chrome popup unattended without user approval must wait/time out by design.
• Real side-panel Send → screenshot → gemma4:cloud → canvas code SATURN 42 and blue rectangle recognized: PASS, opt-in Cloud synthetic test only.
• Direct original Claude in Chrome native side panel read-only local QA response validated. Same HTML and prompt in Switchboard initially failed, but corrected semantic snapshot returned Judul: QA-BICO-731; Tombol: Ready, matching DOM; PASS with local AI.
• Direct original Claude click, vision and Stop UX comparison remains unverified due Claude nearing weekly quota. Owner accepted remaining comparison limitations for launch, not represented as complete pixel-level parity.

Submission

Upload only audited Chrome ZIP version 0.4.4 to existing Chrome Web Store item, review required website-content/privacy disclosures and publisher record, select Submit for review. Publication is not confirmed until Web Store reports Published with the same item ID and current version. Edge Add-ons has its own unverified process. Do not leak API keys, signing keys, personal screenshots or credentials.

Switchboard 0.4.1

• Add an official pinned MCP plugin catalog for Semgrep and OpenSandbox to the existing Switchboard Plugins & MCP panel. Installing, reconnecting, and removal reuse the standard MCP bridge and approval policy.
• Keep manually configured MCP servers authoritative. Explicit local install is required; remote websites cannot silently install tools.
• Prepare a Windows portable bundle including Node and uv/uvx, with checksums and upstream licensing; first-run access uses the existing Switchboard local console.
• Provide local-console handoff through ?plugin=semgrep or ?plugin=opensandbox; hosted OpenSandbox per-user provisioning remains subject to security and capacity gates.

Switchboard 0.4.0

• New Chrome/Edge Manifest V3 Browser Companion for Switchboard CLI and Web UI. The agent prompt stays in Switchboard; the extension only executes approved browser actions and returns results.
• Browser tool bridge stays connected in the background after its panel is closed, with authenticated loopback WebSocket, heartbeat, automatic reconnect, and short-lived one-use pairing codes.
• Add 13 browser tools, approved-origin controls, audit logs, password/payment field protection, and browser-specific approval details showing the intended action, last-reported site, and target selector before consent.
• Browser Companion starts automatically from both sbx chat --preset browser and sbx web. Real-model end-to-end verification with Chrome and Edge on Windows, including Web UI and CLI, is documented under docs/browser-companion.
• Package separate Chrome/Edge extension ZIPs with SHA-256 checksums in the GitHub Release. These are development-style unpacked extensions; Chrome Web Store and Edge Add-ons publication are not included.