First 30 Minutes

Use this page to get Stallari running, understand the main screens, and make the first permission choices deliberately.

1. Open Setup

The setup window walks through vault selection, model routing, plugins, tools, helper approval, Mac permissions, and a final kickoff screen.

You can skip optional steps and return later. Stallari records setup progress so reopening the app resumes from the next useful step.

2. Choose A Vault

Pick an existing vault or create a new one. Stallari treats the vault as the durable record: generated notes, review items, digests, and configuration-linked context are written as human-readable Markdown where possible.

If you sync the vault between Macs, Stallari still coordinates work locally. Sync makes the knowledge base available across machines; it does not make cloud execution mandatory.

3. Configure A Model Route

Stallari needs at least one model path before it can run work. Common starting points:

Route	Best For
OpenAI	ChatGPT Plus/Pro and OpenAI-compatible provider setup.
Anthropic	Direct API billing and Claude-family routing.
Google	Gemini routing.
xAI	Grok routing.
Local models	On-device or LAN-hosted inference where supported.

Provider keys are stored in the local credential store, not in config.yaml.

4. Approve The Helper

The helper hosts local dispatch, indexing, status probes, and plugin routing. macOS may ask you to approve Stallari in Login Items. This grant allows background operation; it is not the same as access to Mail, files, or app management.

If the helper is not running, open Status. Status names the failed part and links to the relevant control or recovery action.

5. Review Mac Permissions

The Mac Permissions step explains each grant before you take action:

Grant	What It Unlocks
Login Items	Keeps the helper available in the background.
Full Disk Access	Enables user-approved local corpus sources such as Mail indexing.
App Management	Lets Stallari recover from macOS blocks during update or replacement flows.
Plugin / MCP Consent	Lets a named plugin use specific data classes and action classes.

Mail indexing is the recommended first Full Disk Access path because it explains exactly what Stallari can and cannot do before macOS shows its own prompt.

6. Connect Plugins

Plugins connect Stallari to services such as mail, tasks, calendars, files, and provider runtimes. Each plugin declares the contracts it supports and the credentials it needs.

Install only what you plan to use. Sensitive plugins require explicit consent before first use or capability expansion.

7. Learn The Main Screens

Screen	Use It For
Chat	Ask your Chief of Staff questions and request work.
Today	See the current personal slice when available.
Operations	Watch live work as it runs.
Activity	Inspect completed runs, costs, tools, and outcomes.
Status	Check helper health, runtime readiness, permissions, encryption, indexing, and recovery actions.
Settings	Change controls: providers, plugins, permissions, account, and lifecycle settings.
Marketplace	Install approved packs and plugins.

8. Run One Small Task

Start with a low-risk request in Chat, such as asking Stallari to summarize its own setup state or explain what still needs configuration. When actions touch external services, Stallari shows what will be used and where review is required.

Where To Go Next

Goal	Page
Understand the system model	How It Works
Configure providers and controls	Settings
Inspect completed work	Activity
Set up integrations	Integrations

Scope And ACL — why permission decomposes into scope tags rather than blanket grants
Local Vs Cloud — what context crosses which boundary at provider selection
Packs And Trust — the trust chain that gates plugin installation