anomalyco / anomalyco/opencode
V1 migration nests provider state under the provider ID
Open
@rekram1-node is already working on this.
Since Aug 21, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
V1 message-part metadata is provider-keyed, for example { anthropic: { signature } }. The V2 migration copies that entire map into the V2 part state, producing { state: { anthropic: { signature } } } where the provider adapter expects { state: { signature } }. The same nesting affects tool provider state and breaks replay of migrated provider metadata.
Plugins
None
OpenCode version
V2 at 2c8e2a2b2
Steps to reproduce
- Create a V1 assistant part with provider-keyed metadata.
- Run the V1 migration.
- Inspect the projected V2 text, reasoning, or tool content.
- Observe the provider ID remains nested inside the provider-local state.
Screenshot and/or share link
N/A (SQLite migration)
Operating System
Any
Terminal
N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.