Run real agent work without giving up control.
Give agents the durable runtime to carry work through—and keep the context, decisions, tools, and evidence you need to trust the result.
Choose your path
Start locally, collaborate with a team, or bring the runtime into a product you already own.
01
02
03
See Kestrel at work
The product surfaces are different because the work is different. The underlying model for durable agent execution stays consistent.
Kestrel Desktop · Beta
Open a repository, folder, research collection, or blank project. Kestrel can inspect the material, use approved tools, produce artifacts, and keep the session ready for your next return.
Durable work · visible control
Kestrel treats agent execution as durable work rather than a disposable request. People remain part of the operating loop.
Sessions and context remain available when you close the window or return later.
Review progress, answer questions, approve important actions, and redirect the work.
Interrupted or failed work leaves enough state and evidence to understand what happened.
Runs preserve tool outcomes, checkpoints, artifacts, and explicit terminal results.
One runtime · two deployment forms
Desktop, CLI, Kestrel One, and server applications use the same execution architecture and explicit result contracts.
Desktop · CLI · local SDK target
Kestrel One · remote SDK target
Kestrel runtime
The same execution model for sessions, runs, tools, persistence, cancellation, recovery, and terminal results.
Open platform
Use Kestrel from the terminal or connect a trusted Node.js application to Local Core or a hosted runner service.
import { createAgent } from "@kestrel-agents/sdk";
const agent = createAgent({
id: "project-agent",
profileId: "reference",
target: {
kind: "remote",
baseUrl: runnerUrl,
authToken: runnerToken,
},
});
const terminal = await agent.run({
sessionId: "project-123",
message: "Summarize the current project.",
}, context);Beta is a product stage, not a hidden program. We document the current state, ship in public, and use real feedback to improve the products.
Desktop and Kestrel One are actively evolving Beta products.
Capabilities and availability may change as the products mature.
Release status and known limitations stay documented publicly.
Reproducible issues and product feedback directly inform development.
Start where the work is
Work locally in Desktop, move together in Kestrel One, or bring the runtime into your own application.