Mohamed Boudra
5ed1f8d108
Rewinding a prompt used to rotate the timeline epoch, so every open client refetched and remounted the whole chat. A rewind is now a retirement: the daemon keeps the rewound turn stored but outside the conversation, and capable clients remove the rows that started in [retireFromSeq, seq) in place. Catch-up pages carry the retirements in their span. Clients without the timeline_rewind_operations capability get the old replacement shape. The daemon retires only what the provider actually removed. Providers report the boundary they kept. A failure known to change nothing keeps the conversation. Any other failure leaves the rewind open and refuses prompts until reloading the agent proves the outcome from the provider's replayed prompts. A recorded cut whose save failed is committed by the next prompt or the reload, which resumes the rewound session. Plugin providers complete session.revert without saying what they removed. Paseo then reloads the session itself and judges the outcome from the replay, so a no-op completion is not taken as a cut. The app anchors each row at the seq it started at, because a late update moves a row's latest seq into the rewound range. The app also refuses pages served before the newest retirement it has seen, then refetches them. Known limits: - The automatic plugin settle shows the agent as restoring briefly. - An empty or mismatched plugin replay leaves the rewind unresolved. Fork the chat to recover. - A plugin's failed revert still needs a manual reload. - An open rewind lives in memory, so a daemon restart drops it.
@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.