Playground and threads
Use the browser workspace for private model exploration, attachments, and independent comparison runs.
Threads keep the product boundary clear
The Playground stores user-facing thread metadata, indexes, and billing references in D1. Message content is handled by the Agent runtime rather than being copied into the billing ledger. This keeps operational usage records useful without making them a second conversation archive.
Attachments are private
Attachments are stored in private R2 storage and validated against the owning thread before use. Their file paths and storage keys are not included in customer-visible provider billing records.
Compare up to five official models
Open a comparison from any model detail page. The comparison URL names the selected provider/model pairs, so it can be shared and revisited. You can add models until the comparison contains five; each selected model runs and bills independently.
A comparison is not a routing test
It compares public identities, published capabilities, and customer-facing output. It does not expose or select private provider routes.