Skip to content

Settings

Settings (/settings) manages account preferences and developer tools. Open the gear in the desktop sidebar identity area, or More → ACCOUNT on mobile. Tabs: Appearance · Notifications · Developer. Integrations have separate guides.

Section Content
Account and profile Wallet identity and username, no separate profile tab
Appearance Dark/Light/System, Reduce motion
Notifications Five notification types
Developer API Keys, MCP Bridge, Orchestration, Connectors, My AI Provider, admin AI Configuration
Toolsets OpenAPI/MCP/Lore → /mcp/:slug
Connectors External-service registry and one-time agct_ token
Embassy Local binary and /settings/projects

Account and profile

There is no separate account/profile tab; ACCOUNT at the top is a section label.

Topic Where
Identity Wallet address; another wallet means another account
Username Chosen during initial connection: 3–32 lowercase letters, digits, _, -, starting with a letter
Credits and history Wallet and top-bar chip; /credits/history. See Credits.
Public view Public profile

Wallet identity stays fixed

Changing a username does not change your wallet address.

Appearance

Choose Dark, Light or System (OS preference). The browser stores this in localStorage, not the server. The top-bar toggle changes the same setting.

Reduce motion

This switch is currently visual only; it does not yet reduce app-wide animation.

Notifications

Each web-channel preference is persisted with PATCH /api/v1/user/notifications/prefs.

Type Trigger Default
Approval requests Run awaits approval On
Social Follows, forks, comments On
Run status Workflow completion/errors On
Security Connector and key events On
Product updates Features and announcements Off

Read notifications in the top-bar bell; see UI tour.

Deduplication

The same wallet/type/link notification is not repeated within one hour. Only enabled types generate notifications.

Developer

Subsection buttons appear at the top. AI Configuration is admin-only.

Subsection Purpose
API Keys Scoped agst_ programmatic keys
MCP Bridge Toolset list/import; Toolsets
Orchestration Design preview
Connectors Service registrations; Connectors
My AI Provider BYOK for agent chat
AI Configuration Admin platform model/provider setup

API Keys

  • New key requires a name and at least one scope: read:agents, write:agents, execute:legend.
  • Keys contain agst_ and 32 hexadecimal characters. The raw value appears once; the server stores a bcrypt hash and short prefix. Lists show prefix, scopes and last use.
  • Revoke invalidates a key.
  • The server also accepts Embassy scopes read:assignments and submit:report, not listed in the web dialog; see Embassy.

See Export and API.

Do not share your key

It cannot be shown again. If lost, revoke it and create another.

MCP Bridge and Connectors

MCP Bridge lists registered toolsets and the OpenAPI/MCP/Lore import bar. Cards open /settings/toolsets/:slug. Go to MCP Bases → opens Embassy registrations (/settings/projects). Connectors adds registrations and rotates tokens.

Sample cards

An empty toolset registry shows demo cards. Orchestration is also a design preview: engine status, counters, runs and “Simulate failure” use fixed samples. For live runs see Legend → Observability.

My AI Provider (BYOK)

Any signed-in user can save an AI provider. When enabled, agent chats (/agent/:id/chat) use it first.

Field Description
Provider Anthropic, Gemini, OpenAI-compatible; Platform default returns to the platform model
Base URL Fixed for Anthropic/Gemini; required for OpenAI-compatible /chat/completions endpoint
API key Encrypted, shown masked; leaving blank for the same provider preserves the stored key
Model Select a suggestion or enter a model ID
Use for my agent chats Toggle without deleting

Test checks connectivity (ten per minute per wallet); Remove deletes it. API: GET/PUT/DELETE /api/v1/user/ai-provider, POST /api/v1/user/ai-provider/test.

No silent fallback; SSRF protected

Provider failure produces a chat error, without falling back to platform keys. Base URLs are checked on save, test and call; private ranges require operator ALLOWED_TOOL_CIDRS. BYOK does not affect Zephyr, Legend or other platform AI.

AI Configuration (admin)

Wallets in ADMIN_WALLETS configure provider, base URL, key and model for each AI “slot”. Non-admins receive 403 and do not see the subsection. Save and Test connection per slot. Changes take effect within seconds without restarting.

Group Slots
Lore lore.distill, lore.embed
Assistant assistant.chat
Agents agent.chat
Legend legend.agent
AI Pipeline aipipeline.text, aipipeline.embed
MCP Bridge mcpbridge.infer
MCP Base mcpbase.case

Chat slots support Anthropic, Gemini, OpenAI-compatible or disabled. Embedding slots support Gemini, OpenAI-compatible or local. Keys are encrypted. Image generation is outside this configuration.

Integrations

Toolsets · Connectors · Embassy.