Skip to main content
This page shows how the individual pieces fit together in real applications. Each workflow is a complete, copy-paste-ready scenario.

Workflow 1: Full provisioning pipeline

The one-time setup every integration goes through: sanity-check auth → create a Provider → verify it → create supporting resources → create the Agent → test it via chat.

Workflow 2: Per-user chat app (the typical production shape)

The standard server pattern: a control-plane client for admin work + a runtime-plane client per incoming request. Your own auth confirms who the user is; then you scope the SDK client to them.

Workflow 3: RAG pipeline — ingest, search, attach

Build a searchable knowledge base and let an Agent use it.

Workflow 4: MCP OAuth — user-mode connection flow

Connect an OAuth-protected MCP for a specific end user (a common CRM/calendar integration).

Workflow 5: Seeding memory before first contact

Give an Agent useful context about a new user before their first message — indistinguishable from memory the Agent wrote itself.

Workflow 6: Named conversation history with files

Threads + Files + Chat working together — a user uploads a document, chats about it in a named thread, and can come back later.

Workflow 7: Stores as read-only reference material

Large reference docs mounted on an Agent, populated by you — the Agent reads them on demand.

Workflow 8: Cleanup with dependency checks

Safe teardown that respects the delete-blocking rules.

Workflow 9: Architect-driven agent creation

Let the conversational Architect build an Agent (and its Skill) for you, with approval handling:

Workflow 10: Error handling wrapper

A reusable error handler for Express-style apps, covering typed Persona errors and network failures: