Skip to content

Document supported Google models and accurate manifest requirements - #459

Draft
erain wants to merge 1 commit into
mainfrom
docs/supported-model-providers-371
Draft

erain wants to merge 1 commit into
mainfrom
docs/supported-model-providers-371

Conversation

@erain

@erain erain commented Oct 13, 2026

Copy link
Copy Markdown
Collaborator

Applying the documented Anthropic Model succeeds, but the workspace planner fails with unsupported provider. The guide now documents the implemented Google provider and removes the unsupported example. It also explains Model resource scope and secret namespace, corrects the supported-kind count and Task image requirements, and replaces a broken example link.

Fixes #371.

Validation on Go 1.27.1, Linux/amd64 (all exited 0):

  • Uncached full tests, race tests, build, vet, module cleanliness, and whitespace checks.
  • The actual documented YAML passes through a real gRPC API, memory store, planner, and Google-format loopback HTTP fixture; request and response assertions pass.
  • The original Anthropic example fails the regression; the unsupported-provider control makes zero HTTP requests. Local documentation links resolve.

Prepared with an AI coding assistant.

Regression output, API/provider fixture, and validation limits

A regression test reads the actual Model YAML from docs/manifests.md, sends it through a real loopback gRPC AX server and memory store, then runs the workspace planner against a local Google-format HTTP fixture. It checks the saved spec, secret reference, request method/path/authentication, workspace goal/system instruction, exact returned plan, request count, and fixture cleanup. An Anthropic negative control verifies API acceptance followed by generation failure with zero provider requests.

Reproduction and captured behavior

go test -count=1 -v ./internal/server -run '^TestManifestGuideModels$'

Before the documentation correction, on base ac2332829f22360ff97b0ba34d94dd0dd782f17e with the regression test added:

YAML -> gRPC UpdateModel/GetModel: provider=anthropic model=claude-opus-5
generating environment plan for workspace guide-workspace: unsupported provider "anthropic"
--- FAIL: TestManifestGuideModels/claude-model/documented
exit_status=1

After the correction:

YAML -> gRPC UpdateModel/GetModel: provider=google model=gemini-3.8-flash
store -> workspace planner -> Google HTTP: model=gemini-3.8-flash summary="fixture bootstrap plan"; requests=1
negative control: generating environment plan for workspace guide-workspace: unsupported provider "anthropic"; HTTP requests=0
HTTP provider fixture stopped
gRPC fixture stopped
--- PASS: TestManifestGuideModels
exit_status=0

Validation

On Go 1.27.1, linux/amd64, all of these completed with exit status 0:

GOFLAGS=-count=1 make test
go test -race -count=1 ./...
go vet ./...
make build
go mod tidy
git diff --exit-code go.mod go.sum
git diff --check

The full test suite contained no skipped tests. Checked all local links in the edited guide and reviewed the complete diff, including the new test.

The provider fixture runs entirely on loopback with a synthetic secret resolver; this is API/store/planner/client integration evidence, not a live Google service, Kubernetes Secret, paid-model, or Substrate sandbox test. It does not establish external availability of the example model ID. The current Task runner has its own Gemini bootstrap configuration; Model resources do not automatically configure arbitrary agent frameworks. The image digest and API key placeholders require user substitution.

The model client implements the Google provider while the guide also
advertises an unsupported Anthropic configuration. Correct the manifest
guidance and exercise its actual model YAML through the API, store, and
model provider client.
@erain
erain force-pushed the docs/supported-model-providers-371 branch from e5f02e2 to 875c042 Compare November 10, 2026 16:50
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.

docs: Model manifest documents provider: anthropic, but only the google provider is implemented

1 participant