trove Install

Autopilot, and the two ways Trove runs.

Two channels

On a subscription

Claude Free, Pro, Max, Team, Enterprise: the Claude Code plugin. Hooks, MCP tools and config fixes. No proxy, no credentials touched, nothing rerouted.

On API keys

An optional local gateway on 127.0.0.1. Your agent points at it with its documented custom-endpoint setting. Keys pass through in memory and are never stored. If Trove hits an error, the original request is forwarded unchanged.

Trove never handles subscription or OAuth logins. Gateway mode is for API-key traffic only and rejects anything else with a plain explanation.

The lifecycle

  1. shadow
  2. eligible
  3. on
  4. measured

If guardrails trip, an optimizer is rolled back to shadow.

Cache safe by construction

Every transformation is a pure, deterministic function of the request. The same history always produces byte-identical output, so cached prefixes stay valid. Optimizers switch only at session boundaries. Each one declares its own token overhead and is charged for it.

Honest numbers

Every figure Trove shows is labeled measured (counted from usage the provider reported) or estimated (list prices or an assumption). Dollar figures are estimates, not invoices. Savings are judged against your actual sessions with and without an optimizer, never against a hypothetical baseline.

Autopilot is a first version. Its promotion thresholds are placeholders not yet validated by a benchmark, and riskier changes need a separate second yes (trove autopilot trials on).

Open source. Runs on your machine. trove uninstall puts everything back.