Skip to content

Shipping record

What changed, and when.

A quiet record of work that is actually in the product. Newest first, with dates from the repository history.

Last updated

  1. Latest arrival

    Agents can start before signup

    Anonymous, claimable quickstart is live.

    • An agent can create a bounded 24-hour sandbox Form without credentials, wire its stable submit URL and verify up to five stored test Submissions.
    • The sandbox capability token is shown only when the Form is created. It remains usable until claim or expiry, so the agent must keep it safe.
    • After claim, a Destination and Route are required before new Submissions can create outbound Deliveries. Copied tests never deliver retroactively.

  2. The agent surface shipped

    Public clients, email-code keys and discoverable contracts.

    • The postbag CLI, @postbag/sdk and @postbag/mcp are published on npm.
    • Email-code authentication can mint an API key without a dashboard. Google and GitHub OAuth are available when an instance configures them.
    • Every /v1 operation has a stable operationId, and the OpenAPI document is generated from route definitions.

  3. Postbag found its public home

    Site, docs, production domain and real end-to-end proof.

    • postbag.dev became the canonical home. Existing submit URLs on the previous domain continue to work.
    • The public site launched with docs, comparisons, use cases, glossary and Markdown twins for agents.
    • Signup, API key creation, quickstart, a real Submission and email Delivery were verified end to end.

  4. Routing grew up

    System webhooks, digests, inference and a second tenant fence.

    • Organization system webhooks dispatch from a Postgres trigger and expose Delivery history.
    • Digest Routes group a period's Submissions into one Delivery.
    • Observe-mode Forms can infer a Schema, and row-level security policies provide a second tenant boundary.

  5. The working product arrived

    Core, database, server, dashboard and generated SDK.

    • The durable submit path, full /v1 API and worker shipped with email, Telegram and webhook Destinations.
    • The dashboard shipped Forms, Inbox, Streams, Destinations, Routes, Deliveries, Events, keys and Settings.
    • The domain core, 23-table Drizzle model, migrations and organization-owned authentication established the base.

  6. The contract came first

    Principles, vocabulary, architecture and the first API sketch.

    • The domain model fixed Form, Submission, Stream, Schema, Mapping, Destination, Route, Delivery and Drift.
    • The architecture put durable storage before Delivery and made the database responsible for correctness.

Want the next arrival?

Start with a form now, or follow the public repository and watch the work land.

Create a form Follow on GitHub