FAQ

What is AlphaBase?

AlphaBase is an AI engineering workspace with a shared local runtime and several clients: Desktop, VS Code, CLI/TUI, local Web, and SDK/API integrations.

Is AlphaBase only desktop?

No. The supported local surfaces are Desktop, VS Code, CLI/TUI, and the browser UI started by alphabase web.

How do providers and models work?

Connect a provider with an API key, OAuth, local runtime, or compatible endpoint, then select an available model. AlphaBase Zen is optional. Model availability and behavior depend on credentials, provider configuration, model catalog data, client version, and runtime state.

Does AlphaBase support LSP?

AlphaBase integrates with supported LSP servers. Automatic setup is conditional on the language, project, installed tools, and configuration; LSP can also be configured or disabled.

Can I control AlphaBase from a mobile app?

The current product documents local CLI/TUI, Desktop, VS Code, Web, and SDK clients. It does not promise a mobile client. alphabase web binds locally by default; non-loopback access requires explicit authentication and network configuration.

Are provider and model claims fixed?

No. Provider and model availability changes with credentials, upstream service availability, catalog data, and release configuration. Use the connected-provider inventory and current model selector as the source of truth.

Why do I get unauthorized errors?

Usually runtime auth mismatch or wrong runtime target. Verify host/port/auth, then refresh diagnostics.

Why do capabilities show PARTIAL?

That indicates degraded mode or fallback data source use. Check runtime connectivity and provider health.

What is the current agent behavior?

• alpha-v3 (Alpha): the visible default primary agent for direct work and specialist coordination
• plan: a hidden restricted profile used for analysis/planning transitions; edit tools are denied by default
• general and explore: built-in subagents with permission-controlled tool access

Why does task output sometimes look malformed?

Typical causes are stream interruption, parser mismatch, or task ending before terminal completion event. Use diagnostics + logs.

What is the fastest release verification path?

Run launch gates plus a clean-profile VS Code smoke before promotion.