Repository navigation
feat(models): add available_in_agent to the catalog and drop GPT-OSS and Llama from Maple Work - #1386
Merged
Merged
Conversation
…and Llama from Maple Work Every model in /v1/models/catalog now carries available_in_agent. GPT-OSS 120B and Llama 3.3 70B are false, so Maple Work stops offering them; the catalog and /v1/models still list both for Research and the API. defaults.agent is DeepSeek V4.1 Flash on every plan, so Free no longer gets GPT-OSS. The Rust and TypeScript SDK catalog types gain the optional field. Maple Work drops models marked false and treats a missing field as available, so either side can deploy first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Maple Work stops offering GPT-OSS 120B and Llama 3.3 70B. The server decides which catalog models Maple Work may offer, so the list can change later with a backend change only.
model_config.rs): every model in/v1/models/catalognow carriesavailable_in_agent. It isfalseforgpt-oss-120bandllama3-3-70bandtruefor every other listed chat model. Both models stay in the catalog and in/v1/models, so Research and the API keep them. API-only entries are set tofalsebut never reach the catalog.defaults.agentis DeepSeek V4.1 Flash on every plan, so the per-plan branch is gone. Before, Free gotgpt-oss-120b.available_in_agenton the RustCatalogModeland on the TSModelCatalogItem.apps/maple-agent):selectable_catalog_modelsdrops models withavailable_in_agent: false. A model without the field counts as available, because older servers don't send it. When the execution computer runs an older build, the controller applies the same rule to that computer's list.Tasks already locked to GPT-OSS or Llama get no special handling. A saved pick of either model falls through to
defaults.agent, as for any model the catalog stops offering (the order from PR #1360).Rollout
Either order is safe:
defaults.agent; I checkedapps/maple-research,sdk,proxyand the docs.Validation
services/opensecret: fmt, clippy--all-targets --all-features -D warnings,cargo test --all-features: 1078 passed, 54 ignored. Two new tests:defaults.agentnames a listed, enabled, tool-capable model withavailable_in_agent: trueon every plan./v1/models.sdk/rust: fmt, clippy-D warnings, lib tests (123 passed),cargo doc -D warnings.sdk(TS): prettier, build (tsc + vite), unit tests (259 pass).apps/maple-agent, through the pre-commit hook:just ci-lint: fmt, clippy-D warningsfor every feature set, packaging tests.just ci-test:maple-agent781 passed, app 1150 passed, Pi crates all pass.available_in_agenttrue, false and missing.just ci-extra: every target builds, headless tests 352 passed.Catalog from the local server on this branch. Excerpt: one line per model, other fields left out. Free and Pro match.
{ "data": [ {"id": "gpt-oss-120b", "enabled": true, "available_in_agent": false}, {"id": "gemma4-31b", "enabled": true, "available_in_agent": true}, {"id": "glm-5-3-flash", "enabled": true, "available_in_agent": true}, {"id": "kimi-k3", "enabled": true, "available_in_agent": true}, {"id": "glm-5-3", "enabled": true, "available_in_agent": true}, {"id": "deepseek-v4-1-flash", "enabled": true, "available_in_agent": true}, {"id": "deepseek-v4-1-flash-1017-uncensored", "enabled": true, "available_in_agent": true}, {"id": "llama3-3-70b", "enabled": true, "available_in_agent": false} ], "defaults": {"quick": "auto:quick", "powerful": "auto:powerful", "agent": "deepseek-v4-1-flash"} }On master's server, the same request returns no
available_in_agenton any model, and Free'sdefaults.agentisgpt-oss-120b.Screenshots
New task, Pro fixture, server on this branch: GPT-OSS and Llama 3.3 are gone.
Same app build, server running master's model config (no
available_in_agent): the app treats the missing field as available and lists all eight models. This is also the before state.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.