Skip to content

Choose a model ​

Tara keeps a catalog of approved models, and Phillip lets you choose only from that catalog. This page shows how to view the catalog, choose a model for a project or for yourself, and decide which kind to use when. You need to sign in to Tara with Phillip first.

View the model catalog ​

Each catalog entry has an identifier (id or alias), a purpose, a status, and a recommended marker. The Tara Portal shows the same catalog in Explore, on the Model tab. On the command line, run:

bash
ph model list

The command prints the catalog and marks the model in use. In general, you choose by type of work.

WorkUse
Reasoning: architecture design, review, complex problemsAn Opus model
Code generation, writing docs, everyday workA Sonnet model
Fast, simple tasks such as summarizing and classifyingA lightweight model (Haiku), if the catalog has one

PhillipCLI platform staff manage the catalog in the Portal. They add new models, edit entries, and deprecate old models without a new Tara release. The catalog can therefore change between two visits.

This split keeps costs reasonable: the strongest model handles the work that needs thinking, and a cheaper model writes the code.

The Model tab groups the catalog by kind of work. The default marker shows you where to start.

Choose a model for a project or for yourself ​

bash
ph model use sonnet-std                   # for the current project (default)
ph model use opus-review --scope user     # for every project you haven't set separately
ScopeWhere it's writtenEffect
project (default)The model key in the project's .claude/settings.jsonEveryone who shares the project, if you commit this file
userYour configurationEvery project that doesn't set its own model

The aliases and ids in the examples might differ from your organization's catalog, so run ph model list to get the right values. Phillip rejects a model that isn't in the catalog. If you choose the project scope and commit .claude/settings.json, the whole team shares the choice, so agree on it with your team lead first.

Which model is in effect? ​

When several places set a model, Phillip uses this order of precedence: the ANTHROPIC_MODEL environment variable first, then the project's model, then the user's model. If none sets a model, Claude Code uses its own default. If you're not sure which model you're using, ask directly:

bash
ph model show

The command prints the model in effect and its source: the environment variable, the project, or the user.

Clear a choice ​

bash
ph model clear                    # clear the project's choice
ph model clear --scope user       # clear the user's choice

When models move to a new generation, the catalog changes through the same review process as every resource: aliases stay stable, and the real model behind an alias can change. The AI cost shown in ph ryoma usage is the converted API price. It's a unit for quotas, not an amount you pay.

Read more ​