Desktop & dashboard settings reference

Every Axelera setting in the desktop app, key by key, plus the dashboard Settings page. Defaults are safe: most people only ever touch one or two of these.

The desktop app has two settings surfaces. The Axelera settings live in the standard settings editor and are stored as wingman.* keys — they control how the app connects, signs in, and launches chat. The dashboard Settings page lives inside Agent Dev and shows your account, service health, and support tools.

Backend and startup

How the app reaches Axelera services.

SettingDefaultWhat it does
wingman.backend.modehostedhosted talks to the remote Axelera API. local targets a same-machine development stack instead.
wingman.backend.hostedUrlhttps://api.wingman.axelera.aiHosted API base URL used when backend mode is hosted.
wingman.backend.apiUrlhttps://api.wingman.axelera.aiAPI base URL used by the app.
wingman.showWelcomeOnStartuptrueOpen the Axelera dashboard automatically when entering Agent mode.
wingman.repoRootemptyAbsolute path to the Axelera repository root, used only when auto-detection fails for local service scripts.

Chat launch

How the Open Chat action launches Axelera Chat.

SettingDefaultWhat it does
wingman.chat.modeintegratedintegrated opens Axelera Chat as an authenticated tab inside the app, falling back to the system browser if needed. browser opens your system browser through the exchange-code sign-in flow.
wingman.chat.uiUrlhttps://chat.wingman.axelera.aiHosted Chat UI used by Chat mode.
wingman.chat.fallbackUrlhttps://chat.wingman.axelera.aiFallback hosted Chat URL.
wingman.chat.desktopBrowserUrlhttps://chat.wingman.axelera.aiBase URL for browser-mode sign-in. Local developers can point this at a local chat instance.
wingman.chat.allowedOriginschat and app originsAdditional origins allowed in the chat tab for sign-in redirects.
wingman.chat.backendaxeleraThe chat backend. Axelera Chat is the only supported value.
wingman.chat.defaultModelzai-org/GLM-4.7:fastestDefault chat model for Axelera Chat.

MCP server URL

One key controls where AI CLIs find Wingman tools.

SettingDefaultWhat it does
wingman.mcp.hostedUrlhttps://mcp.wingman.axelera.ai/mcpHosted MCP server URL used when launching Claude Code, Codex, or Gemini with Wingman tools. Deployments can override it centrally, or you can set it directly.

Sign-in and authentication

These are for administrators and local development — everyday use never needs them changed.

SettingDefaultWhat it does
wingman.auth.modesupabaseLeave at supabase, the standard sign-in. Other values exist for Axelera-managed setups only.
wingman.auth.requireLogintrueRequire sign-in before Axelera features unlock.
wingman.sso.providerIdemptySSO provider id for SAML enterprise SSO. When set, Microsoft sign-in uses SAML SSO instead of OAuth.
wingman.backend.supabaseUrlemptyAuth project API URL for custom deployments.
wingman.backend.projectRefemptyAuth project reference for custom deployments.

Integrations and policy

Integrations, feedback, and policy.

SettingDefaultWhat it does
wingman.zendesk.enabledfalseEnable the Zendesk MCP integration for customer-support knowledge. This is what powers Zendesk support triage mode.
wingman.feedback.includeDiagnosticstrueAttach redacted diagnostics to feedback and bug reports: app versions, workspace info, and recent Wingman log lines. Turn it off to send your words only.
wingman.agentDev.allowDangerousBypasstrueApplication-wide policy for Agent Dev Full access and Claude Vibe permission bypass. Set to false in managed or restricted deployments to remove those options. Applies per machine — workspace values are ignored.
wingman.acf.devServerUrlemptyDeveloper override: load the in-app feedback UI from a local dev server.

Dashboard Settings page

Open Agent Dev and pick Settings in the dashboard sidebar. It is read-mostly: a health and identity view rather than a wall of switches.

SectionWhat you find there
AppearanceLight or dark theme for dashboard pages. Theme is a local preference — it does not change hosted service behavior.
Wingman MCPYour MCP connection: service status, the endpoint address, and the copy-ready setup for each editor and CLI. This is where the Home tile and the setup guide both send you.
Managed AI service healthHealth of the managed AI services behind chat and agents.
ProfileYour account identity: email, user id, organization and role, admin access, MFA and email verification, and session provider.
Sign-in configurationThe identity runtime this dashboard started with: auth strategy, the internal and customer SSO providers, the chat OAuth client, and the sign-in methods on your account.
SupportReport Bug opens the bug-report flow, with an optional screenshot and the same redacted diagnostics as feedback. The support contact shown across the product is the Axelera support mailbox, support@axelera.ai, and sales questions go to sales@axelera.ai.