anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Extra inputs are not permitted, field: 'promptCacheKey' #2907

New Issue
Closed
opened 2026-02-16 17:37:45 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 17:37:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @duggthangs on GitHub (Nov 16, 2025).

Description

After authenticating with fireworks.ai, any model i select, I get the following error:

Extra inputs are not permitted, field: 'promptCacheKey', value: 'ses_571eef633ffeactcBoB0qqtDme'

Looking in the code, it looks like this field is added only if the providerID is "opencode", "openai", or npm.includes("openai"). In my case, I am using Fireworks.ai which is using the openai sdk and because of the npm condition, I believe it triggers this.

The npm condition seems pretty generic and over encompassing. Can we pair this with an exclusion list of provider ids? I don't believe fireworks uses this at all.

OpenCode version

1.0.67

Steps to reproduce

  1. Login with fireworks.ai api key
  2. select any fireworks.ai model, (Kimi K2 Instruct)
  3. type "Hello" and submit.

Screenshot and/or share link

Image

Operating System

macOS 26.0.1

Terminal

Ghostty

Originally created by @duggthangs on GitHub (Nov 16, 2025). ### Description After authenticating with fireworks.ai, any model i select, I get the following error: >Extra inputs are not permitted, field: 'promptCacheKey', value: 'ses_571eef633ffeactcBoB0qqtDme' Looking in the code, it looks like this field is added only if the providerID is "opencode", "openai", or `npm.includes("openai")`. In my case, I am using Fireworks.ai which is using the openai sdk and because of the npm condition, I believe it triggers this. The npm condition seems pretty generic and over encompassing. Can we pair this with an exclusion list of provider ids? I don't believe fireworks uses this at all. ### OpenCode version 1.0.67 ### Steps to reproduce 1. Login with fireworks.ai api key 2. select any fireworks.ai model, _(Kimi K2 Instruct)_ 3. type "Hello" and submit. ### Screenshot and/or share link <img width="1005" height="497" alt="Image" src="https://github.com/user-attachments/assets/a0706e38-3703-4eb1-aabd-662d9f8dcae0" /> ### Operating System macOS 26.0.1 ### Terminal Ghostty
yindo added the opentuibug labels 2026-02-16 17:37:45 -05:00
yindo closed this issue 2026-02-16 17:37:45 -05:00
yindo commented 2026-02-16 17:37:45 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Nov 16, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #4282: Similar "Extra inputs are not permitted" error with Vertex AI, where unsupported fields are being sent to providers that don't support them
  • #2038: Previously resolved "Extra inputs are not permitted" error with Bedrock, where extra fields were incorrectly included in API calls

Both issues involve the same root problem: OpenCode is sending additional parameters (like promptCacheKey, instructions, or name) to providers that don't support them. The fix pattern appears to be similar - adding proper provider-specific filtering of these parameters.

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Nov 16, 2025): This issue might be a duplicate of existing issues. Please check: - #4282: Similar "Extra inputs are not permitted" error with Vertex AI, where unsupported fields are being sent to providers that don't support them - #2038: Previously resolved "Extra inputs are not permitted" error with Bedrock, where extra fields were incorrectly included in API calls Both issues involve the same root problem: OpenCode is sending additional parameters (like `promptCacheKey`, `instructions`, or `name`) to providers that don't support them. The fix pattern appears to be similar - adding proper provider-specific filtering of these parameters. Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:37:45 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 16, 2025):

Fix releasing

@rekram1-node commented on GitHub (Nov 16, 2025): Fix releasing
yindo commented 2026-02-16 17:37:45 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 16, 2025):

1.0.68 fixed it

@rekram1-node commented on GitHub (Nov 16, 2025): 1.0.68 fixed it
yindo commented 2026-02-16 17:37:45 -05:00
Author
Owner
Copy Link
Copy Source

@shantur commented on GitHub (Nov 17, 2025):

@rekram1-node - #4413 enables caching with the fix

@shantur commented on GitHub (Nov 17, 2025): @rekram1-node - #4413 enables caching with the fix
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 bug opentui
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#2907
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?