teaspill
Changelog

Changelog

New features, improvements, and fixes in teaspill.
v1

teaspill v1

The first release of teaspill — durable AI agents that survive restarts, spawn sub-agents, and stream every step to your UI.

We're excited to share the first release of teaspill, a platform for durable AI agents. Agents you build on teaspill keep running across restarts, crashes, and deploys — spawn sub-agents, talk to each other, share context, and stream their every step to a browser in real time. This release covers the full path from defining an agent to watching it work in your own UI.

Durable agents by default

Every agent runs on top of durable execution, so progress is never lost to a crash or a redeploy. An agent picks up exactly where it left off, its history is recorded as an append-only timeline, and long-running work simply survives. You write ordinary agent logic; the platform makes it durable.

Build agents with the Agents SDK

@teaspill/agents-sdk is the developer-facing way to define an agent:

  • defineAgent — declare an agent type with typed spawn arguments, inbox messages, and state, all validated with Zod schemas.
  • Choose your harness — run agents on the built-in native harness or on the Claude Agent SDK, without changing how you define them.
  • Tools — extend agents with platform tools (spawn and message other agents), workspace tools, and your own.
  • State that evolves safely — an additive-only rule keeps an agent's state schema forward-compatible as you ship changes.
  • Serve and register — stand up an agent deployment and register it with the platform in a couple of calls.

Stream everything to your UI

@teaspill/frontend-sdk turns an agent's live timeline into something your frontend can render:

  • Materialize an agent's timeline into UI-ready messages, updated as events arrive.
  • Stream token-by-token deltas for a responsive, typing-style experience.
  • Subscribe to a live catalog of agents — filter by type and status to build dashboards and inboxes.
  • Issue commands (spawn, message, and lifecycle actions) through a small actions client.
  • Drop-in React bindings are included; the core is framework-agnostic.

Browser clients read agent history over short-lived read tokens and can start from a recent snapshot instead of replaying full history, so even long-lived agents load fast.

Run it yourself

teaspill is self-hostable from day one:

  • A single Docker Compose stack brings up everything an agent needs.
  • The teaspill CLI gives you a fast dev loop plus commands to inspect agents and manage access.
  • One gateway is the single entrypoint for your services, UIs, and the CLI — the internal services are never exposed directly.
  • API keys guard write access, with an optional read path for browser clients.
  • Back up and restore your data with documented, supported store combinations.

A stable v1 event vocabulary

The canonical timeline event schema is frozen for v1, giving you a stable foundation to build tooling, integrations, and UIs against.

This is just the beginning. Follow the changelog for what comes next.