Measured capability checklist · October 2026

What Vibastic actually does

Every agent capability Vibastic tracks, with its real status — live when it works in the shipped product, adapted when it had to be reimplemented for the browser and Android, blocked when an upstream service refuses it, missing when it does not exist yet.

This checklist comes from the same data file the app itself uses, so the public page and the in-app screen cannot drift apart. Statuses were checked in October 2026 and change only when a measurement changes.

Grouped by area, each with its status and its source.

Agents

  • Agent office (6 specialised roles)live

    planner, file_finder, builder, reviewer_fixer, researcher, browser_tester — bounded dispatch, sub-agents one level deep.

  • Plan mode (read-only)live

    Composer [PLAN] chip: the request runs read-only, the loop refuses to write files.

Permissions

  • Confirmation mode (ask)adapted

    OpenCode permission port: risky tools ask for confirmation instead of running.

  • Permission rules (deny > ask > allow)live

    {action, resource, effect} rules, prefix wildcard (mcp_*), last match wins — faithful reimplementation.

  • Permission dialog on every calladapted

    In confirmation mode every risky call opens the Allow / Deny dialog; with no answer the call is denied — never run silently.

Sessions & context

  • Checkpoints & undolive

    checkpoint() / undoTo() over the history + virtual file-system snapshot restore.

  • Persisted sessionsadapted

    Host-side JSON serialisation of the session (IndexedDB) — adapted to the browser, no internal opencode files.

  • Diff context / file changesadapted

    The VFS snapshots on every write and the job card rebuilds the phases; a rich diff viewer is still to be built.

  • Project memorylive

    Decision log persisted across conversations, re-injected into the prompt builder.

Tools

  • File tools (write, patch, read, list, glob, grep)live

    11 tools over a sandboxed virtual file system — same tool surface, safe execution outside the process.

  • Remote MCP serverslive

    Remote HTTP/SSE servers configured in Settings; tool chips in the composer. stdio needs a desktop.

  • Local stdio MCP serversmissing

    A stdio server has to launch a local process — impossible inside a WebView, reachable only through Vibastic Bridge on desktop.

  • Built-in terminal (TUI)missing

    A TUI cannot run inside a WebView; adapted as a browser_tester agent (preview + console) instead.

Providers & models

  • Provider / model switchinglive

    Unified local + cloud picker (sticky auto-router, provider-order fallback, BYOK keys encrypted on device).

  • OpenCode Zen free tierblocked

    Removed from the offer: the live probe returned HTTP 403 FreeTierError ("free tier can only be used from within OpenCode"), and OpenCode documents no self-service eligibility step for third-party clients. The fix must come from OpenCode; no bypass is used.

  • DeepSeek Harness agentlive

    Dedicated transport + /api/harness intensifier — sandboxed agent runs, selectable from the router.

  • Local AI (GGUF on device)live

    wllama multi-thread (cross-origin isolation enabled), ~18 catalogued models, full cycles tested.

By status

Proof paths kept for developers (registrant): the evidence field of lib/opencode-capabilities.ts shows what backs each status.

Compare Vibastic with other tools

OpenCode is an independent project. Vibastic is not affiliated with, endorsed by or integrated with it; product names and trademarks belong to their respective owners and appear here only to describe compatibility.

Report a translation error