Release notes

This page tracks released versions of the Agent Engine developer tools. Each tool versions independently:

• The TypeScript SDK (@runorca/orca-sdk) is published to npmjs.org from the public orca-ae/orca-sdk-typescript repository.
• The Python SDK (runorca) is published to PyPI from the public orca-ae/orca-sdk-python repository.
• The Go SDK (github.com/orca-ae/orca-sdk-go) is published as a public Go module from orca-ae/orca-sdk-go.
• The ork CLI is distributed from the public orca-ae/orca-cli repository through Homebrew, release archives, and Go install.

These tools are pre-1.0 and under active development. The entries below summarize their released versions.

TypeScript SDK

0.2.3

Published the SDK as @runorca/orca-sdk on npmjs.org. Installations from the earlier @orca-ae/orca-sdk GitHub Packages scope need to replace the dependency and imports. The v0.2.3 release contains the package-scope change.

0.2.2

This release lets the SDK reach a self-hosted deployment. Earlier releases hardcoded /v1/registry/... in every path, which the open-source engine does not serve, so ORCA_BASE_URL pointed at one returned 404 on every call. The v0.2.2 release makes these API path and resource changes:

Breaking

• baseURL is now the host root. The client appends the full route itself, /v1/... for core operations and /apis/<group>/<version>/... for extensions. A value ending in /v1/registry, /v1, or /api/v1 is stripped with a deprecation warning, so existing configurations keep working.
• Core paths dropped the /registry infix: /v1/registry/agents became /v1/agents, and likewise for sessions, environments, files, skills, vaults, and memory stores.
• Triggers use the core /v1/triggers route and are exposed as orca.triggers. The open-source engine supports cron; StreamNative Cloud widens the same request types with Pulsar and Kafka sources. Lifecycle methods are pause and unpause, and updates are partial POST requests.
• Agent providers moved to orca.cloud.agents.providers. Connections, Pulsar Functions, packages, connector catalogs, Pulsar IO sources and sinks, and Kafka Connect are also exposed through orca.cloud.*. These methods require the deployment to advertise cloud.sn.io and throw a typed ExtensionNotAvailableError when it does not.
• beta_version was removed from every request body. It was never a real field: no request schema defined it, and permissive servers ignored it until one did not.

Earlier 0.2.x releases

0.2.0 realigned the SDK with the registry OpenAPI surface - paths, HTTP verbs, and resource hierarchies. Later releases in that line added operations.

Added

• orca.triggers - agent triggers, with create, list, retrieve, update, and delete, plus start, stop, and restart lifecycle actions. See Agent triggers.
• orca.triggers.sessions.list(triggerId, params?) - paginated sessions created by a trigger.
• Streaming requests now send an Accept: text/event-stream header.

Breaking (introduced in 0.2.0)

• Sessions and their sub-resources are top-level, no longer nested under an agent. The agentId positional parameter was removed from every method on orca.sessions, orca.sessions.events, orca.sessions.resources, orca.sessions.threads, and orca.sessions.threads.events. The owning agent is still set through the agent field on the create body.
  • orca.sessions.create(agentId, params) became orca.sessions.create(params).
  • orca.sessions.list(agentId, params?) became orca.sessions.list({ agent_id, ...params }).
  • orca.session(agentId, sessionId) became orca.session(sessionId); SessionHandle.agentId was removed.
• Non-agent resource paths dropped the /agents/ infix to match the spec's /v1/registry base - for example /v1/registry/agents/environments became /v1/registry/environments (and likewise for files, memory_stores, skills, and vaults).
• Archive endpoints use the /archive sub-path rather than an action form, across agents, sessions, sessions.threads, memory_stores, environments, vaults, and vaults.credentials.
• HTTP-method fixes: memoryStores.update is now PATCH; sessions.update is now PUT; agents.archive is now POST /agents/{id}/archive; the thread events stream is rooted at /sessions/{sessionId}/threads/{threadId}/stream.
• Removed the memoryStores.memories and memoryStores.memoryVersions sub-resources, which are not in the current spec.

Added (in 0.2.0)

• orca.vaults.credentials gained retrieve, update, archive, and validate (the last validates a credential's MCP OAuth configuration).

Earlier 0.1.x releases

Initial releases through GitHub Packages.

Added

• The Orca client with Bearer-token authentication (static string, async token function, or null to disable), automatic retries with exponential backoff, configurable timeouts, and structured logging.
• Cursor-based pagination on every list method, with async iteration over all pages.
• Server-sent-events (SSE) streaming for session and thread events.
• Multipart upload helpers for files and skills.
• Resources: agents (with versions and providers), sessions (with events, resources, and threads, plus per-thread events), environments, files, skills (with versions), vaults, and memory_stores.
• The orca.session(sessionId) handle for ergonomic single-session work.
• A README, the docs/surface-status.md surface map, and runnable examples under examples/.

Python SDK

0.3.0

The v0.3.0 release is the initial public PyPI release under the runorca distribution name. Install it with pip install runorca==0.3.0 and import Orca or AsyncOrca from orca. It requires Python 3.10 or later.

The SDK provides synchronous and asynchronous methods for core registry resources, policy and pricing extensions, and hosted Cloud extensions. It supports page iteration, session-event streaming, typed errors, and Bearer-token authentication. See the Python SDK guide and the repository's API surface.

Go SDK

0.4.0

The v0.4.0 release is public and installable with go get github.com/orca-ae/orca-sdk-go@v0.4.0. It requires Go 1.25 or later. The client covers core registry resources, session events, policy and pricing extensions, and hosted Cloud extensions. It sends a Workspace API key as x-api-key or an OIDC token as Authorization: Bearer; supply exactly one. See the Go SDK guide for a tested local example.

ork CLI

0.5.0

The public v0.5.0 release includes ork local and release archives for macOS, Linux, and Windows. Install it with brew install orca-ae/tap/ork on macOS or Linux, or use go install github.com/orca-ae/orca-cli/cmd/ork@v0.5.0 with Go 1.25 or later. The CLI manages a Workspace's registry resources: agents, sessions, memory stores, vaults, environments, files, skills, triggers, and hosted extensions. See the CLI overview and local tutorial.

Earlier 0.4.1

Before 0.5.0, the CLI binary was named orca. Its v0.4.1 release added direct MCP OAuth credential authorization and clarified session-event stream cursor behavior, but did not include ork local.