Skip to content

feat: add app-server model registry#40

Merged
galligan merged 1 commit into
mainfrom
feat/model-registry-service-tiers
Jun 11, 2026
Merged

feat: add app-server model registry#40
galligan merged 1 commit into
mainfrom
feat/model-registry-service-tiers

Conversation

@galligan

@galligan galligan commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add an App Server-backed models op/CLI route/MCP grouped action for current Codex model defaults, model catalog rows, reasoning efforts, and service-tier aliases
  • resolve explicit service_tier values for new/fork through model/list so user-facing fast maps to the App Server tier id (for example priority) before thread/turn start
  • persist model catalog and per-lane model/service-tier provenance in schema v5, including observed metadata from attach/sync/discover
  • update docs, plugin/skill guidance, and package version to 0.5.0

Testing

  • just check
  • uv run dispatch schema models | jq -e ' .op == "models" and (.input.properties.refresh.type == "boolean") and (.output.properties.models.type == "array") '\n- isolated live smoke with temp DISPATCH_HOME: dispatch up, dispatch models --json, dispatch models --no-refresh --json, dispatch down\n\nLive smoke confirmed the current local catalog shape: supportedReasoningEfforts is object-shaped, config default service tier can be fast, and models such as gpt-5.5 advertise alias fast -> priority.\n\n## Notes\n\n- models --no-refresh still reads current config defaults, but does not call model/list; catalog rows come from the registry cache.\n- Omitted model/tier options preserve Codex defaults in outbound calls; Dispatch records defaults for output truth without forcing them into App Server requests.

Copy link
Copy Markdown
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@galligan galligan marked this pull request as ready for review June 11, 2026 16:45

galligan commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

Merge activity

  • Jun 11, 4:46 PM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Jun 11, 4:47 PM UTC: @galligan merged this pull request with Graphite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant