Settings

The Settings page is where you configure AI provider accounts, define model profiles, build fallback chains, and connect external integrations. All per-user and per-organization AI configuration lives here.

Accessing settings

Settings navigates to /settings.

Settings tabs

The Settings page has tabs across the top. The default tab when first opening Settings is Usage.

In order, the tabs are: Usage, Accounts, Model Profiles, Fallback Chains, Provider Types, Integrations, Automations, Variables, Devices, Updates, Seed Library, and Backup. Provider Types and Seed Library appear only in Advanced UI mode, and Backup is shown only to superusers; the rest are always available.

Usage tab

The Usage tab gives a high-level view of AI consumption across the current organization for a selected time period.

Period selector

Four buttons let you select the time window for the stats:

Stat cards

Three stat cards display aggregate totals for the selected period:

Usage chart

Below the stat cards, a “Token usage over time” chart renders a time-series graph of token consumption for the selected period. The chart uses bars or a line plot depending on the granularity of the selected window.

Empty states:

• No data at all: “No data for this period”
• Chart area with no data points: “No usage data for the selected period.”

Accounts tab

The Accounts tab is where you connect AI providers. Nexora supports both OAuth-based providers and API-key providers.

Header

The tab header reads:

AI Accounts Claude, Gemini and Codex connect via OAuth — no API key needed. OpenAI, DeepSeek, Groq and more use API keys.

An Add Account button sits in the top-right corner of the tab.

Empty state

When no accounts are configured, the tab shows:

• Colorful provider logo dots (visual indicator of supported providers)
• “No accounts yet” heading
• “Connect Claude or Gemini via OAuth, or add any provider with an API key” subtitle
• “Add first account” button (equivalent to the Add Account button in the header)

Auto Rate-Limit Fallback info card

Regardless of whether accounts exist, an informational card is shown:

Auto Rate-Limit Fallback When an account hits its rate limit, Nexora switches to the next in your chain automatically. The limited account cools down for 60 s, then is retried. Build chains in the Fallback Chains tab.

Add Account modal

Clicking Add Account or Add first account opens the Add Account modal.

The modal contains a Provider dropdown that defaults to Claude (shown with an orange dot).

Model Profiles tab

Model Profiles let you define named LLM configurations that can be assigned to agents. A profile captures:

• A name and optional description and tags
• A route mode — either a specific provider type + model, or a fallback chain
• A priority and an active toggle

Profiles are referenced by agents in their configuration. Changing a profile’s settings immediately affects all agents using that profile.

Fallback Chains tab

Fallback Chains define the order in which Nexora tries provider accounts when a request fails due to rate limiting or provider errors.

How fallback works

1. Nexora sends the request to the first account in the chain.
2. If that account returns a rate-limit error, Nexora immediately retries with the next account.
3. The rate-limited account is placed in a 60-second cooldown. After cooldown it is re-added to the rotation.
4. If all accounts are exhausted, the request fails with an error.

Building a chain

• Create a chain with New Chain, then click Add step to add a provider/model step.
• Use the move-up arrow to reorder steps — the topmost step is tried first.
• Click the trash button next to a step to remove it from the chain.

Integrations tab

The Integrations tab (headed External Accounts) connects Nexora to external services that agents can interact with.

A separate Git credentials section on this tab stores GitHub/GitLab tokens used by the git read/write skills.

Each integration card shows the service name, its current status, and a button to connect or configure it.

Automations tab

The Automations tab lets you configure rule-based automated behaviors that trigger agents on a schedule or in response to events.

Automation rules define:

• A trigger — what causes the automation to fire (e.g. a schedule, an incoming webhook, a Telegram message matching a pattern)
• An agent — which agent handles the trigger
• Parameters — any additional context or instructions passed to the agent when it fires

Variables tab

The Variables tab stores API keys and secrets that tools need (e.g. STRIPE_SECRET_KEY) without editing a server .env file. Values are encrypted at rest and write-only — they are never displayed again after saving; you can only replace or delete them.

Scopes

At run time a variable is resolved org-first, then personal — an org value with a given key shadows a personal value with the same key unless you remove the org one.

Adding a variable

Devices tab

The Devices tab links the Nexora mobile app (iOS / Android) to your account by scanning a QR code. Each device gets its own independently revocable access — unlinking one device never signs out your web, CLI, or other mobile sessions.

Linking a device

Linked devices

Each linked device shows its name, platform (iOS / Android), and last-active time. Click the trash icon to unlink a device — it loses access immediately and can be re-linked later by scanning a new QR code.

Updates tab

The Updates tab lists the skills, tools, personas, and agents you installed from a marketplace and lets you upgrade them to newer versions.

Checking and applying updates

• Check for updates — re-queries the marketplace for newer versions of every installed package. The button reports how many updates are available.
• A package with a newer version shows v<installed> → v<available> and an Update button.
• Update all appears when more than one package has an update pending.
• Up-to-date packages show a “Up to date” check.

Each row shows the package type (Skill / Tool / Persona / Agent), its name, and the installed version. Paid packages are marked with a lock icon.