anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-21 17:56:33 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[BUG] Anti-gravity models fail with enum TYPE_STRING validation error in memory_rate_memory tool #4968

New Issue
Closed
opened 2026-02-16 17:47:11 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 17:47:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @zensi-dev on GitHub (Jan 12, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

When using anti-gravity models in OpenCode, the following validation error occurs:

Invalid value at 'request.tools[0].function_declarations[33].parameters.properties[1].value.enum[0]' (TYPE_STRING), -1
Invalid value at 'request.tools[0].function_declarations[33].parameters.properties[1].value.enum[1]' (TYPE_STRING), 0
Invalid value at 'request.tools[0].function_declarations[33].parameters.properties[1].value.enum[2]' (TYPE_STRING), 1

Root Cause

The memory_rate_memory tool (function_declarations[33]) has a rating parameter with numeric enum values [-1, 0, 1], but the anti-gravity model API requires enum values to be strings, not numbers.

Expected Behavior

The tool should work with anti-gravity models without validation errors.

Actual Behavior

Anti-gravity models reject the tool schema due to type mismatch in enum values.

Proposed Solution

Update the memory_rate_memory tool definition to use string enum values:

  • Change enum: [-1, 0, 1] to enum: ["-1", "0", "1"]
  • Or remove the enum constraint and use type validation with description

Environment

  • OpenCode version: latest
  • Model provider: Anti-gravity models
  • Platform: Linux

Additional Context

This issue only occurs with anti-gravity models. Other model providers appear to have more lenient schema validation and accept numeric enum values.

Originally created by @zensi-dev on GitHub (Jan 12, 2026). Originally assigned to: @rekram1-node on GitHub. ## Description When using anti-gravity models in OpenCode, the following validation error occurs: ``` Invalid value at 'request.tools[0].function_declarations[33].parameters.properties[1].value.enum[0]' (TYPE_STRING), -1 Invalid value at 'request.tools[0].function_declarations[33].parameters.properties[1].value.enum[1]' (TYPE_STRING), 0 Invalid value at 'request.tools[0].function_declarations[33].parameters.properties[1].value.enum[2]' (TYPE_STRING), 1 ``` ## Root Cause The `memory_rate_memory` tool (function_declarations[33]) has a `rating` parameter with numeric enum values `[-1, 0, 1]`, but the anti-gravity model API requires enum values to be strings, not numbers. ## Expected Behavior The tool should work with anti-gravity models without validation errors. ## Actual Behavior Anti-gravity models reject the tool schema due to type mismatch in enum values. ## Proposed Solution Update the `memory_rate_memory` tool definition to use string enum values: - Change `enum: [-1, 0, 1]` to `enum: ["-1", "0", "1"]` - Or remove the enum constraint and use type validation with description ## Environment - OpenCode version: latest - Model provider: Anti-gravity models - Platform: Linux ## Additional Context This issue only occurs with anti-gravity models. Other model providers appear to have more lenient schema validation and accept numeric enum values.
yindo added the zen label 2026-02-16 17:47:11 -05:00
yindo closed this issue 2026-02-16 17:47:11 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label zen
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4968
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?