Choose models per role

Trove runs two kinds of LLM session with their own model + transport setting: the cheap spec audit (the triage) and the autonomous implementation cycle. Each is a global default you can override per project.

There used to be a third, "spec writing", for the per-lane spec assistant. That assistant is retired — authoring is an OPAL conversation now, and that conversation picks its own model.

The model settings are rows of the Models category of the trove settings window. Each role has two rows:

• Model: the name of the model, for example claude-haiku-4-5. An empty name lets the transport select its default model. The list of the row shows the models that the installed claude CLI offers, and then the models of the REST API, marked (REST API). Trove asks the CLI when you first open the list, so the CLI models can arrive a few seconds later. You can also type a name that is not in the list.
• Transport: how the role reaches its model.
  • Claude terminal: the claude CLI on your subscription. This is the default for each role. It costs no metered API money.
  • REST API: the REST API of a configured provider. Use it only when the LLM registry has an API provider with credentials. If no API provider exists, a row set to REST API is dimmed, and its tooltip tells you to add a provider or to select the Claude terminal.

The defaults give each role a suitable tier: the latest Haiku for the audit, because it is fast and cheap, and the workhorse model for the implementation.

Set the default for all projects

1. Open Trove from the apps menu, and select the Settings tab of the projects wall.
2. Push Settings. The trove settings window opens.
3. Make sure that Write to shows All projects.
4. Select Models in the category list, and change the rows.

Each change is saved immediately.

Override for one project

1. Open the board of the project, and select its Settings tab.
2. Push Settings. The trove settings window opens, with Write to set to Project: .
3. Change the rows that you want to set for this project.

A row that the project does not set shows the value of all projects. The Source column tells which level gives the value. To use the value of all projects again, push the revert button of the row.

Overrides are sparse: a project keeps only the rows that you set for it. A later change to the value of all projects applies to each project that does not set the row.