Alvoki Docs

Support matrix

What’s supported

Supported configurations, verified behavior and known limitations during the closed alpha.

Closed alpha

Alvoki is currently a closed alpha. Access is reviewed, and approved use is suitable for evaluation and non-critical workflows.

The product is still evolving. Connectors, permissions, APIs, interfaces and workflows may change, and some changes may require action from existing users.

Alvoki is operated on a best-effort basis during this alpha, without contractual uptime or support-response commitments.

The sections below describe what is currently supported, along with known limitations.

Support matrix

Availability varies by path; these rows describe the setup and run behavior currently documented for each surface.

SurfaceStateVerified behaviorCurrent limitation
Codex CLI via MCPBetaCLI 0.145.0 setup/connectivity smoke: registration, bearer-token environment setup, config/list output, and OAuth command flags.This covers MCP setup and command surfaces, not a model session or hosted Codex access.
Claude Code via MCPBetaClaude Code 2.1.217 setup/connectivity smoke: bearer-header registration, connected-server output, and OAuth client-id setup.Interactive browser OAuth and model sessions are not covered by this smoke.
OpenCode via MCPBetaOpenCode 1.18.4 setup/connectivity smoke: remote config, bearer authentication, server-list output, and MCP auth command surface.Interactive OAuth, installed-client screenshots, and model sessions are not covered by this smoke.
Hosted sessionsBetaLightweight gateway-backed agent runs plus environment-backed interactive hosted-model sessions, with transcripts and governed capabilities.The interactive hosted-model path currently requires a running sandbox volume. Ask-mode continuation depends on the calling surface.
Hosted GitHub run with connected computeVerified beta exampleJuly 24, 2026: seeded bug -> patch -> two passing tests -> PR, with one selected repo and agent/* branch boundary.No merge; the example used scoped Allow grants for unattended completion.
ApprovalsBetaExact approval-payload queueing and replay for gateway-governed calls.Approval is a gate, not rollback; continuation after approval depends on the calling surface.
Workflows / packagesEarly betaWorkflow runs, package actions, human input, and run history.Workflow UI, remote OAuth package auth, and third-party package trust are still maturing.

Known limitations and gaps

Workflow UIRicher trigger editing, event delivery diagnostics, schedule controls, and clearer run evidence for the golden workflow loop.
Prompt-assisted workflowsThe Workflows-page authoring panel can start an admin-scoped agent that validates and saves workflows or drafts missing setup. A separate review-before-save gate for manual run shape and policy is follow-up work.
OAuth package authProvider OAuth connection flows, token refresh, and package binding beyond API-key secrets.
Package UI bridgeHost-mediated package UI calls for setup, action invocation, live context, and resizing.
Third-party package trustA public package marketplace, package review, signing, provenance verification, version distribution, and stronger secret handling for third-party packages do not exist today.