The Settings tab
The Settings tab holds Trove’s app-level configuration: how it keeps itself up to date, and the optional identity overlay that stamps who generated each signal onto the telemetry stream.
Auto-update
Section titled “Auto-update”Trove can keep itself current. The Settings tab exposes the auto-update toggle and a manual Check for updates control, so you can either let new versions arrive on their own or pull them on demand. Updates are delivered from Trove’s public GitHub Releases — there’s no SaaS account and no separate updater daemon to babysit.
Identity tagging
Section titled “Identity tagging”Identity tagging is an opt-in overlay that adds two resource attributes to every signal Trove forwards:
user.nameuser.email
Because these are resource attributes — set once per harness session, not
per-data-point — they scope a metric series to a person without inflating
cardinality. Combined with the harness.id attribute every signal already
carries, identity tagging is what powers the per-person, per-tool views your team
cares about: which engineer is using which tool, and the dead-seat detection
that surfaces paid licenses with zero activity.
How it lands in your backend
Section titled “How it lands in your backend”Once enabled, your queries can group and filter on user.name / user.email
exactly as they do on harness.id. A finance dashboard can roll cost up by person;
an engineering dashboard can show per-engineer turn counts across a mixed-harness
team — all from the same normalized Tier A metrics.