Skip to content

Services support the work you create in Playbooks: supplying inputs, keeping editable results, storing application data, running background tasks, and checking what happened. Start with the capability you need, then check where it is available.

Chats, Agents, and Projects share conversational content capabilities. Projects also use application services during development; Sites operate independently configured production services. A service's availability does not transfer data, credentials, or permissions between those places.

Choose where the work runs

I want to…Start here
Have an Operator use a websiteBrowser sessions
Read a public page from my applicationApplication Web Access
Run commands and inspect a working previewProject sandboxes
Host a static site or a backend at a visitor-facing addressRelease a first Site and production runtime
Give visitors an application loginApplication sign-in
Generate a response from my backendApplication inference
Look up an address or display a mapMaps and location
Generate an illustration for an applicationMedia generation
Call a reusable specialist from my applicationAgent access and execution

Inputs and execution

Bring material into a conversation, develop it into useful work, and decide how to retain or share the result.

For example, attach a spreadsheet as a Source, develop a report in the File system, and retain an interactive calculator as an Artifact. Those are deliberate choices: editing the report does not change the original spreadsheet, and sharing the calculator does not expose its producing conversation.

For retained interactive experiences, see Artifacts.

For lasting background across tasks, use configuration Files.

Data and automation

Build application behavior in a Project, then configure the production resources needed by its Site.

A customer portal might keep account records in a database, uploaded documents in Storage, and prepare exports through Jobs. Releasing its code does not automatically copy development records or credentials into production.

Visibility and quality

Use evidence from the appropriate environment to investigate problems and judge whether work is ready.

Content, execution, and diagnostics by surface

A dash means the service is unavailable on that surface.

CapabilityChatsAgentsProjectsSites
Analytics———Measure production traffic
BrowserBrowse authorized websitesBrowse authorized websitesBrowse websites and inspect previews—
Databases——Store development recordsStore production records
File systemEdit files in the ChatEdit files in the Agent’s working treeEdit files in the Project’s working tree—
Jobs——Develop background tasksRun production tasks
Logs——Inspect development logsInspect production logs
Monitoring———Investigate production exceptions
Sandboxes——Run commands and working previews—
Security——Scan application source—
SourcesAttach conversation inputsAttach conversation inputsAttach conversation inputs—
Storage——Store development uploadsStore production uploads
Testing——Check application behavior in developmentVerify the live release with production authorization

Each article explains the relevant scope and limitations. Supported provider setup, resource permissions, and funding still govern actual use.

Use Sharing for collaboration and distribution, Plans for reviewed execution, and Prompts for writing requests. External account setup belongs in Configuration. Production execution is covered by Site Runtime.