HelixML

Settings reference

Every settings panel in Helix (account, organisation, and admin), with what each control does and where to find it.

This page lists every settings panel in Helix and what each control does. For how to configure specific features, see the relevant guide instead: LLM providers, organisations, source control.


Account settings

Access from the user menu (top right) → Account.

General

SettingWhat it does
Full nameDisplay name shown in comments, activity, and the org member list
PasswordChange your login password (available when using email/password auth)
Claude subscriptionLink a Claude Pro or Team subscription for Claude Code agent access via subscription (see choose a code agent)
UsageToken count, total cost, and request count for your account this billing period
QuotaPer-resource limits set by your instance admin

API keys

Each account has one API key used to authenticate requests to the Helix API and SDK.

ControlWhat it does
Show / CopyReveal and copy the key value
RegenerateIssue a new key; the old key stops working immediately

The key is also accepted in the Authorization: Bearer <key> header and as ?api_key=<key> in query strings.

Chat settings

SettingWhat it does
ThemeLight or dark UI mode

Organisation settings

Access from the org selector → Settings (or Organisation → Settings in the sidebar). You must be an org owner to change most of these.

General

SettingWhat it does
NameHuman-readable org name shown in the UI
SlugURL-safe identifier used in org URLs (/orgs/<slug>/...). Cannot be changed after creation.
Auto-join domainEmail domain (e.g. acme.com) whose users are automatically added to this org on first sign-in
Delete organisationPermanently deletes the org and all its projects. Irreversible.

Members

Invite, manage, and remove org members. Roles:

RoleCapabilities
OwnerFull admin — change settings, delete org, manage members
MemberCreate and run projects; cannot change org settings

API keys

Org-level API keys authenticate service accounts and CI integrations. They carry org-member permissions.

Providers

Configure AI providers shared across the whole org. Members who haven't added their own providers fall back to these. See Configure LLM providers — Organisation level.

Billing

Subscription and credit balance for Helix Cloud orgs. On self-hosted deployments this section is not shown.

Secrets

Secrets are key-value pairs injected as environment variables into agent sandboxes and coding sessions for all projects in the org. Use them for API keys, tokens, and other credentials that projects need at runtime.

ControlWhat it does
Add secretCreate a new key-value secret
DeleteRemove a secret; existing running sessions are not affected until they restart

Admin panel

Access from Admin in the left sidebar. Visible to instance administrators only.

Analytics & Monitoring

LLM Calls

A live log of every LLM API call made through the instance — model, provider, token counts, latency, and the requesting user. Useful for auditing cost and debugging slow responses.

Infrastructure

Inference Providers

Configure instance-level LLM providers available to all users. Equivalent to the per-user and per-org provider settings but applied globally. See Configure LLM providers — Self-hosted for Helm configuration; this panel lets you configure them at runtime without a redeploy.

OAuth Providers

Configure identity providers for user authentication:

ProviderNotes
GitHubOAuth App or GitHub App
GoogleGoogle Cloud OAuth 2.0 client
OIDCAny OIDC-compatible IdP (Okta, Keycloak, Azure AD, etc.)

Service Connections

Register external service integrations (webhooks, outbound channels) used by the instance.

Runners

Manage compute runners from a single master-detail page. The top of the page shows instance-wide stats: online runner count, active sandbox count, and user count. Below that, a GPU statistics panel gives a global view of fleet utilisation. A runner picker dropdown (defaulting to the first online runner) lets you select any registered runner; the detail panel below shows:

  • Profile — which inference profile is assigned to this runner
  • Logs — live-tail log stream from the selected runner
  • Sandboxes — sandbox containers currently running on this runner, with resource usage and session context

Models & Configuration

Helix Models

Configure custom model endpoints served by Helix's own inference layer (as opposed to external API providers). Applies to self-hosted GPU deployments running Helix-served models.

Runner Profiles

Inference profiles map runner hardware to model configurations. A profile specifies which model to serve on which runner type, with memory and concurrency constraints.

Pricing

Set credit costs for sandbox usage:

SettingWhat it controls
Headless sandbox priceCredits per second for headless (no-desktop) sandboxes
Desktop sandbox priceCredits per second for full Ubuntu desktop sandboxes
Max concurrent headless sandboxesPer-org limit on simultaneous headless sessions
Max concurrent desktop sandboxesPer-org limit on simultaneous desktop sessions

System Settings

Instance-wide configuration:

SettingWhat it does
Hugging Face tokenAPI token for downloading gated models from HuggingFace Hub. Can also be set via the HUGGING_FACE_HUB_TOKEN environment variable — the UI shows which source is active.
Kodit enrichment modelLLM used by Kodit to generate semantic descriptions of code symbols during indexing
Kodit text embedding modelEmbedding model used to vectorise code for semantic search

Code Intelligence

Kodit Repositories

View and manage the repositories Kodit has indexed. Trigger re-indexing or remove a repository from the index.

Kodit Queue

Monitor the Kodit indexing job queue — pending, running, and completed indexing tasks with timing and error information.

User Management

Users

Browse all users on the instance. View last active date, org membership, and admin status. Grant or revoke admin privileges.

Organizations

Browse all orgs on the instance. View member count and creation date. Useful for support and billing audits.


Environment variables

For self-hosted deployments, many of these settings can also be applied via environment variables passed through the Helm chart rather than the UI. See Configuration reference — Control plane environment variables for the full list.