Two entry points: local and remote
Use the same SDK for an embedded local Agent or for a RemoteAgent HTTP client that talks to another runtime.
Compose local Agents, RemoteAgent clients, sessions, and plugins into your application flow so the agent becomes an embeddable execution layer.
Integration, sessions, plugins, and API guidance now live in the standalone agent-sdk-docs site.
Use the same SDK for an embedded local Agent or for a RemoteAgent HTTP client that talks to another runtime.
Keep run, stream, history, and fork centered on the Session model so application integration stays stable.
Let the caller decide which plugins and tools are mounted instead of relying on automatic platform assembly.