36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
# First Launch
|
|
|
|
The first launch flow is designed to get you into a real vault quickly without hiding the local-first model.
|
|
|
|
## What You Choose
|
|
|
|
Tolaria asks whether you want to:
|
|
|
|
- Create or clone the Getting Started vault.
|
|
- Open an existing local vault.
|
|
- Create a new empty vault.
|
|
|
|
The Getting Started vault is cloned locally and then disconnected from its remote. That keeps the sample safe to edit without accidentally pushing tutorial changes.
|
|
|
|
## What Tolaria Creates
|
|
|
|
Tolaria stores app-level settings on the local machine. Your notes stay in the vault folder you choose.
|
|
|
|
| Data | Stored in |
|
|
| --- | --- |
|
|
| Notes and attachments | Your vault folder |
|
|
| Type definitions and saved views | Your vault folder |
|
|
| Window size, zoom, recent vaults | Local app settings |
|
|
| Cache data | Rebuildable local cache |
|
|
|
|
## First Commands To Try
|
|
|
|
- `Cmd+K` / `Ctrl+K`: open the command palette.
|
|
- `New Note`: create a note in the current vault.
|
|
- `Open Getting Started Vault`: clone the public sample vault.
|
|
- `Reload Vault`: rescan files after external edits.
|
|
|
|
## AI Setup Prompt
|
|
|
|
Tolaria can show an optional AI agents prompt after a vault is open. It checks common local install locations for supported coding agents and gives you setup paths, but you can dismiss it and use Tolaria without AI.
|