Files
paseo/packages/client
d016bf0b44 fix(timeline): stop the frame-budget fallback when a page cannot shrink
A tail page starts at the first row of the source span it lands in. When
one tool call starts before an oversized turn and completes after it, its
span covers every row, so a smaller limit returns the same page. The
fallback halved the limit down to 1 and then reported that a single item
was too large. It now stops at the first reselect that does not shrink and
says that one item spans more than the limit.

Document in the SDK reference, the plugin hook docs, and the zh-CN copies
that a whole-turn page over the message limit arrives as an item page that
can start partway through a turn.

Co-authored-by: AnalyticETH <hello@analytic.lol>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 02:44:10 +00:00
..

@getpaseo/client

TypeScript SDK for building integrations on top of a Paseo daemon.

npm install @getpaseo/client
import { createPaseoClient } from "@getpaseo/client";

const client = createPaseoClient({ url: "ws://127.0.0.1:6767/ws" });
await client.connect();

const agent = await client.agents.create({
  config: { provider: "codex/gpt-5.5" },
  cwd: "/Users/me/dev/storefront",
  prompt: "Review the current diff and name the riskiest change.",
});

const result = await agent.waitForFinish();
console.log(result.lastMessage);

await client.close();

The public API is the package root. Imports under @getpaseo/client/internal/* are unsupported implementation details used by Paseo's own packages.

Read the SDK documentation for agents, workspaces, terminals, provider discovery, events, recipes, and the API reference. Runnable TypeScript patterns also live in examples/.

Runtime

The client needs a WebSocket implementation. Modern browsers and Node.js 22 provide one globally.

Use a WebSocket URL ending in /ws, such as ws://127.0.0.1:6767/ws. Pass password when the daemon requires authentication.

The client advertises its supported protocol capabilities by default. Optional capabilities overrides extend or override that declaration; browser hosting must be supplied by the caller. Connecting alone does not subscribe to agent timelines or catalog events. See the event guide for subscription lifetimes and timeline replacements.

Stability

The high-level API exported from @getpaseo/client is the supported SDK surface. The SDK and daemon remain protocol-compatible across versions, but newly added capabilities can require a newer daemon.