Aegis Orchestrator
Zaru

The Vault

Store and manage credentials that your agents use at runtime. Agents never see credential values directly — the platform injects them securely at execution time.

The Vault

The Vault is where you store credentials that your agents use at runtime. Agents never see credential values directly — the platform retrieves the credential and injects it securely when the agent needs it during execution.

A key you store can be read back only by you, from your own signed-in session, and only for a named purpose, and each read is recorded. No agent, operator, API key or other person is given the value. The routes and their refusals are in the Vault API reference.

Providers (/vault/providers), second in The Vault's navigation, is where you add the model providers Zaru chats through on your own key (The Conversation Panel); a link to /settings/providers opens it.


Supported Providers and Credential Types

ProviderCredential TypesExample Value
OpenAISecretsk-...
AnthropicSecretsk-ant-...
Google (Gemini)Secret, Service AccountAPI key or service account JSON
GitHubSecretghp_...
Carbon ForgeSecretA Carbon Forge (formerly Nuclear Notes) MCP token, nn_mcp_...
CustomSecret, VariableAny value
Google (mailbox)OAuth2None: Connect Google on the Connections page signs you in to Google
Google CalendarOAuth2None: Connect Google Calendar on the Connections page signs you in to Google
IMAP and SMTP (mailbox)MailboxYour mail server settings, user name and password, from Connect by IMAP and SMTP
CalDAV (calendar)CalendarYour calendar server's https:// address, account address and password, from Connect by CalDAV

The last four are connections, made from the Connections page rather than New Credential: a mailbox for the mail.* tools, and a calendar account for the calendar.* tools (Calendar). Google's mailbox and Google Calendar are two separate sign-ins, each granting only its own service.


Secrets vs Variables

The Vault has two credential types:

Secret — a sensitive value. Masked after creation and never shown again. Use Secret for API keys, passwords, access tokens, and any value you would not want displayed in logs or the UI.

Variable — a non-sensitive configuration value. Readable after creation. Use Variable for base URLs, feature flags, region names, or any non-sensitive identifier your agents need at runtime.

When in doubt, use Secret.

The Vault is for credentials. For Zaru's evolving notes about your preferences and work style, see Memory — a sibling user-scoped settings page.


Adding a Credential

  1. Navigate to The Vault in the sidebar.
  2. Click New Credential.
  3. Select a provider from the list (or choose Custom for any other service).
  4. Enter a name for the credential — this is how it will appear in grant lists and agent configuration.
  5. Enter the credential value.
  6. Click Save.

Secret values are masked immediately after saving and cannot be retrieved again. If you lose a secret value, you will need to rotate it from the source service and save the new value.


Credential Grants

Saving a credential does not automatically make it available to your agents. You must explicitly grant access.

After saving a credential, open it and click Add Grant. You can grant access to:

  • A specific agent by name
  • A workflow by name
  • Your entire current session (useful for interactive use)

Without an active grant, no agent can read or use the credential, even if they request it.

A grant does not widen which of your connections a run reaches: a run, a schedule or an API key reaches only the connections its profile names, or those chosen for it one by one. The Connections page shows no Grants link on a mailbox or a calendar account.


OAuth Connections

OAuth Connections, in the Vault's navigation, opens the Connections page. Two providers connect by OAuth on the reference deployment: Google, a Google mailbox for the mail.* tools, and Google Calendar, a Google calendar for the calendar.* tools. Click Connect Google or Connect Google Calendar and sign in to Google in your browser; each is its own sign-in, and each grants only its own service. The page also connects a mailbox by its IMAP and SMTP settings and a calendar account by its CalDAV server, each with its account and password rather than a sign-in. Once connected, a run, a schedule or an API key whose profile names that connection can make authenticated requests on your behalf.

The providers offered are the ones the server's oauth_providers registers; a server that registers none shows "No OAuth provider is set up on this server yet." GitHub is not one of them: a GitHub token is stored as a credential.

An OAuth connection's access token is refreshed when it is within 60 seconds of expiry. A connection whose token can no longer be refreshed is marked expired. Disconnect on the provider's card removes the connection.


Profiles

Profiles, after OAuth Connections in the Vault's navigation, groups your connections into named sets, each with the tools they may use, a default repository, a default Carbon Forge workspace and instructions. A conversation or a schedule chooses one profile in place of choosing connections one by one. See Profiles.


Edge Hosts

The Vault houses your Edge Hosts — AEGIS daemons running on your own hardware (laptops, home servers, work VMs) bound to your tenant. The section is organized into three sub-views.

Hosts

A card per enrolled daemon. Each card shows:

  • Display name (editable inline).
  • Status badge: Connected / Disconnected / Unhealthy / Revoked.
  • OS / arch (auto-detected at enrollment).
  • Last seen timestamp.
  • Labels (read-only — these are advertised by the daemon).
  • Tags (editable inline — operator-managed classifiers like prod, db-host).
  • Action menu: Rename, Edit Tags, Revoke, Inspect.

The Host Detail view adds capabilities, advertised labels, operator tags, and a recent command history streamed from the platform's event log.

Add Edge Host

Click Add Edge Host. The dialog issues an enrollment token bound to your effective_tenant, displays a copyable aegis edge enroll <token> command, a QR code for mobile-to-laptop transfer, and a countdown to expiry (default 15 minutes). On enrollment the new edge appears in the list within ~1 heartbeat.

For team tenants, the picker shows accessible tenants (personal + teams you're a member of). The token's tid is set accordingly and the resulting daemon is visible to all team members per the team-membership claim.

Groups

Saved selectors with named, reusable scopes. The group editor exposes a selector form (tags, labels, tools, OS, arch) with a live Selector Preview Panel ("matches 7 of your 12 connected edges") and a pinned-members section for explicit overrides.

Group membership is dynamic — re-evaluated at every dispatch. New hosts that match the selector automatically join.

Fleet Runs

Paginated history of fleet operations. Each row shows the tool, target, policy summary, outcome, and a per-node breakdown. The live run view for an in-flight operation shows a per-node grid with streaming output and a Cancel button.

For the underlying model, see edge mode overview; for the operations playbook, see edge fleet operations.

On this page