I had copilot compare the js and python api.md and this is what I got from it, maybe you'll find useful. Since they use stainless for generation I figured it might be nearly identical and the comparison indicated most of this seems feature equivalent.

Based on posts on x from Dax, I think they are working on a v2 of the SDK so this might all improve/change in the near future as well.

Copilot analysis

Looking at both files, they're functionally equivalent. Same endpoints, same types, same methods. The differences are purely language conventions.

Summary: Both SDKs expose identical API surfaces. Every resource (Event, App, Find, File, Config, Session, Tui) has the same methods hitting the same HTTP endpoints. The type definitions mirror each other 1:1. Stainless did its job - these are the same API in two languages.

Aspect	Python SDK	JS SDK	Notes
Import style	`from opencode_ai.types import ...`	`<a href="./src/resources/... ">`	Language convention
Method params	`**params`	`{ ...params }`	kwargs vs object destructuring
Return type links	Full path `./src/opencode_ai/types/...`	Short path `./src/resources/...`	Directory structure difference
Type location	Separate `types/` directory	Inline in `resources/`	Stainless config choice
Naming	`snake_case` (e.g., `append_prompt`)	`camelCase` (e.g., `appendPrompt`)	Language convention
Truncated lines	Several `[...]` truncations	None visible	Rendering issue in Python doc

The truncated lines in the Python api.md are a documentation artifact, not a feature gap. Both SDKs cover the same ground.

Is it full functional as JS sdk #39

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions