Settings¶

Access settings via the gear icon in the toolbar.

Display Settings¶

Settings > General > Display.

Theme¶

Display Options¶

Graph Settings¶

Settings that affect the Graph view visualization (Settings > General > Graph).

Max depth is stored per workspace and in the database, so each workspace keeps its own depth and the value survives a reinstall.

Physics Settings (Radial Layout)¶

The radial layout uses a physics simulation. Adjust these parameters via the Graph view settings panel:

Tuning tips:

• Increase Node Repulsion for sparse layouts with more space between nodes
• Decrease Edge Length for tighter clustering of connected nodes
• Higher Gravity pulls nodes toward center; lower values allow spreading
• More Iterations produces smoother results but takes longer to compute

Settings are saved per-workspace with keys like graph-radial-repulsion-{workspace}.

Where settings are kept¶

In the desktop app settings live in the database, which is encrypted when database encryption is on. A copy is also written to browser localStorage so the window can paint before the database has opened.

A setting marked secret is exempt from that copy. The OpenAI API key is the only one today. localStorage is plain files in the user-data directory, outside the encrypted database, so mirroring a live credential there would hand it to anyone who can read the directory while the database protects everything else. A secret is therefore written only to the database, and a copy left in localStorage by an earlier version is deleted the first time the setting loads.

In the browser there is no database and localStorage is the only store, so a secret entered there is kept by the browser as any other web app would.

Node Position Storage¶

Node positions in Graph view are automatically persisted:

• Storage: Browser localStorage
• Key format: graph-positions-{workspace}-{parentId}
• Scope: Per-workspace and per-parent context
• Validation: Positions outside bounds (50000) are filtered

Positions are saved after: - Dragging nodes - Layout operations (relax, reset) - Graph updates

AI Settings¶

Configure AI providers for note enhancement.

Ollama (Local)¶

OpenAI-Compatible¶

Skip SSL Verification¶

The bypass applies only to local endpoints: localhost, 127.0.0.1, ::1 (including the bracketed [::1] form) and any *.local host. Certificates for every other host are verified even while the setting is enabled — a remote endpoint with a bad certificate fails with:

SSL/TLS error: <reason>. "Skip SSL verification" only applies to local endpoints
(localhost, 127.0.0.1, ::1, *.local); certificates for remote hosts are always verified.

The setting applies to note improvement as well as Wikipedia lookups when the OpenAI-compatible provider is selected.

Custom Prompts¶

Create custom AI prompts:

1. Navigate to Settings > AI
2. Scroll to Custom Prompts
3. Click "Add Prompt"
4. Enter name and template
5. Use {{selection}} as placeholder for selected text

The preset actions, including the Wikipedia lookup, are edited in the same list; Reset restores a preset's default text.

For detailed AI usage, see AI Notes.

Database Management¶

Available in the desktop (Electron) application.

Snapshots¶

Create point-in-time backups of your database.

Snapshot Location:

Snapshots are written next to the main database (graph.db) as graph-backup-{timestamp}.db:

• macOS: ~/Library/Application Support/graph-core/
• Windows: %APPDATA%/graph-core/
• Linux: ~/.config/graph-core/

A snapshot is also taken automatically before a destructive migration (-pre-workspace-migration, -pre-tag-migration) and before restoring another snapshot (-pre-restore).

Restoring a snapshot upgrades it to the current schema, running the same table creation, migrations and indexes as startup, so a snapshot taken before a migration is usable without a restart. The snapshot is opened and read before it replaces the working database; if it cannot be read, the working database stays in place. The previous connection is closed after the switch, and the upgrade runs on the restored database.

Database Operations¶

Emptying the trash is done from the Trash view ("Empty Trash"), not from Settings.

Lost and Found¶

A node is orphaned when its parent is missing or sitting in the trash. Deleting a node re-attaches its children to their grandparent, so this is rare in day-to-day use — it mostly shows up in databases from older versions. Use Lost and Found to:

• View orphaned nodes
• Reparent them to root (their path and depth are rebuilt, descendants included)
• Delete permanently

About¶

Settings > About shows the app version and provides:

See Demo Workspace.

Keyboard Shortcuts¶

For the complete keyboard shortcut reference, see Keyboard Shortcuts.

See Also¶

• AI Notes
• Workspaces
• Installation

Security¶

Available in the desktop app only; in web mode the data lives behind the HTTP API and this section is hidden.

• Encrypt database: encrypts the database file, backups, and snapshots at rest (design). Enabling requires setting a recovery password; the warning shown there is literal - losing both the recovery password and this machine's keychain loses the data. On a system with no secure keychain (Linux without a keyring service), the settings panel says so before you enable, and the app asks for the recovery password at every start instead of unlocking through the keychain.
• Require Touch ID at startup (macOS): puts a fingerprint prompt between the keychain and the key, so an open macOS session is not enough to open the app. With sensitive-note encryption enabled, the same setting lets a fingerprint reveal sensitive notes: the prompt appears at the moment of reveal, and the recovery password remains the fallback.
• Disable encryption: requires the recovery password and rewrites the database as plaintext.