DOCUMENTATION ENTRY
The contract is clear. The distribution is not public yet.
Tabyard's architecture and interface direction are documented today. Runtime installation and official SDK packages follow successful private validation.
PRIVATE ALPHA NOTICE
Do not copy a command that does not exist.
This marketing repository intentionally does not ship the private control plane, a public package, or a hosted endpoint. Examples describe the intended stable contract and are labelled conceptual until release evidence exists.
INTEGRATION DIRECTION
HTTP lifecycle. Standard browser connection.
Create a bounded session, connect with the automation client you already use, and release in a finally path after both success and failure.
// Conceptual API — not yet a published SDK
const session = await tabyard.sessions.create({
name: "research-agent",
timeoutMs: 300_000,
metadata: { agent: "trace", task: "market-research" },
});
const browser = await chromium.connectOverCDP(session.websocketUrl);
try {
const page = await browser.newPage();
await page.goto("https://example.com");
} finally {
await tabyard.sessions.release(session.id);
}READ THE SYSTEM
Start with the boundaries.
Root validation key now; scoped hashed tokens next.
Name, timeout, viewport, metadata, and optional policy inputs.
A private or scoped CDP-compatible endpoint for standard clients.
Idempotent cleanup from a guaranteed finally path.