Skip to content

Settings

The Settings tab holds Trove’s app-level preferences. There aren’t many — Trove is opinionated about defaults — but each one matters.

Trove can keep itself current using Tauri’s built-in updater.

  • Auto-update (toggle). When enabled, Trove periodically checks the GitHub Releases feed and applies signed updates in the background. Updates are cryptographically verified before they are applied.
  • Check for updates (button). Triggers an immediate check, regardless of the auto-update toggle. Use this when you want the latest build right now.

Identity tagging stamps two resource attributes onto every signal Trove forwards, so your backend can attribute activity to a person:

  • user.name — a display name (for example, Jane Doe).
  • user.email — an email address (for example, jane@example.com).

These attributes power the per-user views that engineering leads and finance care about — comparing harness usage across a team, and detecting dead seats (paid licenses with zero turns over a window). They are entirely optional and travel only to the backend you configured, alongside the rest of your telemetry.

Trove keeps all of its persistent state in a single versioned JSON file, state.json. It captures which harnesses and backends are enabled and what each patch wrote — never secrets, which live in the OS keychain. The schema is versioned and migrated in place across app versions, and the file never reaches outside your config directory.

state.json lives in the same per-platform config directory as the generated collector.yaml:

PlatformConfig directory
macOS~/Library/Application Support/com.intevity.trove/
Linux (XDG)~/.config/com.intevity.trove/
Windows%APPDATA%\com.intevity.trove\

The bundled collector also writes a rotating log there (or under the platform’s log directory) that feeds the Logs tab:

PlatformCollector log
macOS~/Library/Logs/com.intevity.trove/collector.log
Linux~/.local/state/com.intevity.trove/collector.log
Windows%LOCALAPPDATA%\com.intevity.trove\Logs\collector.log

collector.log is size-capped at 10 MiB with a single rotation to collector.log.1.