adding-models
Guide for adding new LLM models to Letta Code. Use when the user wants to add support for a new model, needs to know valid model handles, or wants to update model-specific compatibility behavior. Covers runtime catalog sources, CI test matrices, and handle validation.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 3396
- Лиценз
- Apache-2.0
- Последна проверка на записа
- 22.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add letta-ai/letta-codeСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Adding Models
This skill guides you through adding a new LLM model to Letta Code.
Quick Reference
Key files:
src/agent/remote-model-catalog.ts- Runtime catalog loading and projectionsrc/agent/model-catalog.ts- Model lookup and compatibility aliases.github/workflows/ci.yml- CI test matrix (optional)src/tools/manager.ts- Toolset detection logic (rarely needed)
Workflow
Step 1: Find Valid Model Handles
First identify the agent source. These inputs are deliberately different:
| Agent source | Rows shown | Labels, presets, and capabilities |
|---|---|---|
| Cloud hosted | GET /v1/models/catalog only | GET /v1/models/catalog |
| Cloud organization BYOK | BYOK rows from GET /v1/models | Match to catalog metadata using provider metadata and model name; retain the BYOK handle for selection |
| Local | pi-ai inventory | pi-ai metadata |
| Custom App Server | Server runtime inventory | Server runtime metadata |
In Cloud mode, never use base/hosted rows from GET /v1/models to filter,
supplement, delay, or provide a fallback for the hosted catalog. This once made
GPT-4o appear in a selector even though the Cloud catalog deliberately omitted
it. GET /v1/models remains necessary for organization-specific BYOK rows.
Query the Cloud hosted catalog to see hosted preset IDs, handles, and capabilities:
curl -s https://api.letta.com/v1/models/catalog | jq '.models[] | [.id, .handle]'
To inspect organization BYOK rows from a Cloud backend, query its model
inventory and filter by provider_category:
curl -s https://api.letta.com/v1/models/ \
| jq '.[] | select(.provider_category == "byok") | [.handle, .provider_type]'
Do not use this response as a second hosted catalog.
Common provider prefixes:
anthropic/- Claude modelsopenai/- GPT modelsgoogle_ai/- Gemini modelsgoogle_vertex/- Vertex AIopenrouter/- Various providers
Step 2: Update the Owning Catalog
Letta Code does not bundle a model catalog:
- Cloud hosted rows and presets come from the server's
GET /v1/models/catalogresponse. - Cloud
GET /v1/modelscontributes only organization BYOK rows to selectors. - Local model inventory comes from pi-ai and the active provider runtimes.
Add the model at the source that owns it. A hosted preset belongs in the server catalog. A local provider model belongs in pi-ai or that provider's discovery runtime.