You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
agent cant use read tool SchemaError(Expected number | undefined, got "2480" at ["offset"]). #26870
→ Read AL\alphaLiquidatorV3.py [limit=90, offset=2490]
The read tool was called with invalid arguments: SchemaError(Expected number | undefined, got "2490"
at ["offset"]).
Please rewrite the input so it satisfies the expected schema.
Thinking: The read tool is rejecting all my offsets. Let me try without the offset parameter and just read larger chunks.
→ Read AL\alphaLiquidatorV3.py [limit=200, offset=2480]
The read tool was called with invalid arguments: SchemaError(Expected number | undefined, got "2480"
at ["offset"]).
Please rewrite the input so it satisfies the expected schema.
Thinking: The offset parameter is causing issues. Let me try without offset, or use a lower offset.
→ Read AL\alphaLiquidatorV3.py [limit=150, offset=2480]
The read tool was called with invalid arguments: SchemaError(Expected number | undefined, got "2480"
at ["offset"]).
Please rewrite the input so it satisfies the expected schema.
Thinking: The offset parameter doesn't accept large numbers. Let me try a smaller offset.
→ Read AL\alphaLiquidatorV3.py [limit=150, offset=2400]
The read tool was called with invalid arguments: SchemaError(Expected number | undefined, got "2400"
at ["offset"]).
Please rewrite the input so it satisfies the expected schema.
Thinking: The offset must be a number, not a string with leading zeros. Let me try 2494.
→ Read AL\alphaLiquidatorV3.py [limit=150, offset=2494]
The read tool was called with invalid arguments: SchemaError(Expected number | undefined, got "2494"
at ["offset"]).
Please rewrite the input so it satisfies the expected schema.
Thinking: The read tool keeps failing with "offset" errors. Let me try with offset without quotes:
→ Read AL\alphaLiquidatorV3.py [limit=150, offset=2550]
The read tool was called with invalid arguments: SchemaError(Expected number | undefined, got "2550"
at ["offset"]).
Please rewrite the input so it satisfies the expected schema.
Thinking: The offset seems to be the problem. Let me try reading from the end of the file.
→ Read AL\alphaLiquidatorV3.py [limit=100, offset=2590]
The read tool was called with invalid arguments: SchemaError(Expected number | undefined, got "2590"
at ["offset"]).
Please rewrite the input so it satisfies the expected schema.
Additionally, this issue is missing several required fields from the bug report template: Steps to Reproduce, OpenCode version (listed in the body as V1.14.33 but not in the designated field), Operating System, and Terminal. Please edit the issue to fill in these fields — this context helps narrow down whether it's model-specific behavior or a broader schema enforcement issue.
If you believe this was flagged incorrectly, please let a maintainer know.
windows 10, wnidows terminal the new one, zsteps to reproduce idk,, it started happening in a sess outta sudden, welkl if it ain ni da best field put it AI BOYT
hey, suddenly I'm experiencing the same problem , did you find a solution?
immediately, changed to a new session and didn't have the issue again till now. I still have the contaminated session saved if they want it anonoymized here
Activity
github-actions commentedon May 11, 2026
This issue might be a duplicate of existing issues. Please check:
offsetandlimitparameters are passed as strings instead of numbers by the model, causing a schema validation error ("Expected number, received string").Additionally, this issue is missing several required fields from the bug report template: Steps to Reproduce, OpenCode version (listed in the body as V1.14.33 but not in the designated field), Operating System, and Terminal. Please edit the issue to fill in these fields — this context helps narrow down whether it's model-specific behavior or a broader schema enforcement issue.
If you believe this was flagged incorrectly, please let a maintainer know.
spacewalkingninja commentedon May 11, 2026
windows 10, wnidows terminal the new one, zsteps to reproduce idk,, it started happening in a sess outta sudden, welkl if it ain ni da best field put it AI BOYT
Dariel0628 commentedon May 11, 2026
hey, suddenly I'm experiencing the same problem , did you find a solution?
spacewalkingninja commentedon May 11, 2026
immediately, changed to a new session and didn't have the issue again till now. I still have the contaminated session saved if they want it anonoymized here
github-actions commentedon Jul 11, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
floyd-fuh commentedon Aug 17, 2026
fyi you can probably do a fix similar to #10813