Skip to content

[Opencode Sync] Core CLI: Provider Integrations #312

@adolago

Description

@adolago

Scope

  • Base ref: origin/main
  • Source ref: opencode/dev
  • Theme id: opencode-provider
  • Commits mapped: 65
  • Date span: 2026-01-21 to 2026-02-13

Theme Summary

Model/provider integration logic and provider-specific behavior.

Mapping Rule

Commits are assigned to one issue by dominant touched-path prefix (most matched files in commit; ties resolved by longest prefix then fixed theme order).

Top Path Hotspots

  • packages/opencode/src/provider/transform.ts (34)
  • packages/opencode/src/provider/provider.ts (20)
  • packages/opencode/test/provider/transform.test.ts (11)
  • packages/opencode/src/provider/models.ts (9)
  • packages/opencode/src/provider/sdk/copilot/chat/convert-to-openai-compatible-chat-messages.ts (4)
  • packages/opencode/test/provider/copilot/convert-to-copilot-messages.test.ts (4)
  • packages/opencode/src/session/llm.ts (3)
  • packages/opencode/src/provider/sdk/copilot/chat/openai-compatible-chat-language-model.ts (3)
  • packages/opencode/test/provider/copilot/copilot-chat-model.test.ts (3)
  • bun.lock (3)

Commits

Acceptance Checklist

  • Validate each commit intent is represented in this theme
  • Define parity implementation tasks for Zee based on these commits
  • Mark commits that are not applicable to Zee

Metadata

Metadata

Assignees

No one assigned

    Labels

    opencode-syncTrack opencode/dev parity mapping

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions