Configuration Reference

Stallari configuration describes local paths, providers, plugins, routing, privacy, helper behavior, and optional peer behavior. Most controls should be changed in Settings unless your installation is managed by an external configuration system.

Configuration Areas

Area	What It Controls
Vault	The local knowledge base Stallari reads and writes.
Providers	Model routes and provider-specific options.
Plugins	Installed connectors, service contracts, and credentials.
Routing	Which provider or plugin handles a request under a given scope.
Privacy	Exclusions and review expectations.
Helper	Background lifecycle and local service behavior.
Permissions	User consent and macOS permission readiness surfaces.
Packs	Installed workflow bundles and their requirements.

Editing Configuration

Use Settings for normal changes. Use a text editor only when you understand the field and can validate the result.

After manual edits, run:

stallari-cli config validate

If validation fails, Stallari should keep the old healthy behavior where possible and surface the problem in Status or Settings.

Managed Configuration

Some installations generate configuration from another system. In that case, direct edits may be overwritten. Change the source of truth and then regenerate.

The app should indicate when configuration is externally managed and which controls are read-only.

Credentials

Secrets do not belong in configuration files. Provider keys, plugin tokens, and service credentials should live in the local credential store and be referenced by configuration or Settings state.

Do not share raw configuration publicly unless it has been reviewed for paths, hostnames, account identifiers, and plugin endpoints.

Routing And Scope

Routing determines which model or plugin handles a request. Good routing is explicit:

local or cloud model route,
service contract,
domain or scope,
required permissions,
and review policy.

If no route is available, Stallari should report the missing provider or plugin rather than silently choosing an unrelated service.

Privacy

Privacy configuration can exclude paths, tags, or terms from indexing and model context. Exclusions are part of the work contract. If content is excluded, Stallari should not surface it simply because a workflow asks broadly.

Validation Checklist

At least one model route is configured.
Required plugins have credentials and consent.
Vault path is reachable.
Helper status is healthy.
Sensitive local data classes have explicit consent before use.
Privacy exclusions match the intended boundaries.

Legibility And Continuity — configuration is readable, validatable, and pointed at by Status
Local Vs Cloud — provider and routing configuration is the policy edge between local and cloud execution