A browser session lifecycle an agent can reason about
Create, inspect, connect and close Cloudflare Browser Run sessions without confusing access links with persistent browser state.
The Lupin field guide
Build agents.
Understand the infrastructure.
Practical answers for the parts between a model and a useful agent. Learn the workflows, compare your options, and plan for what happens when a request fails.
Search 200 published articles by topic.
Browse the field guides
Articles 1–18 of 200
Account for connection slots, pending setup and tool costs
Understand pending capacity reservations, creation usage and unbounded tool effects before planning integration costs.
Apply recipient allow and block lists at the correct scope
Combine send, receive and reply policies without assuming an inbox setting overrides a broader restriction.
Approve apparent reads as well as writes in connected apps
Use actual tool behavior, account identity and exact arguments to authorize connected application execution.
Assign an inbox to an agent without sharing your mailbox
Choose a dedicated inbox, preserve its identity and give an agent only the access its workflow needs.
Authorize agent tools by the exact effect they can cause
Distinguish ordinary lookups, sensitive writes and provider actions that need explicit human review.
Bind every resource lookup to its authenticated workspace
Keep tenant ownership attached to resource identifiers, delayed recovery and human claims instead of relying on a caller-supplied target ID.
Bound command output before it reaches the agent
Keep logs useful, retain failure status and separate a small diagnostic summary from full artifact storage.
Budget sandbox runtime around complete task stages
Allocate finite compute time, leave room for verification and distinguish running usage from command count.
Build a framework-independent Lupin HTTP client
Use standard HTTPS, explicit error handling and durable operation records without depending on a particular agent framework.
Build a retry queue that respects Retry-After and action identity
Schedule bounded retries from structured errors and HTTP delay hints without creating a burst of replacement actions.
Build an email draft lifecycle with explicit state transitions
Create, update and retire drafts while preserving source messages and separating drafting from sending.
Build an email webhook receiver that queues work safely
Authenticate inbound events, isolate tenant routing and acknowledge only after durable acceptance.
Build an email-to-tool pipeline with an approval boundary
Turn verified inbound events into proposed actions while keeping sender content separate from account authority.
Carry unresolved reservations across the UTC month boundary
Explain why a new budget month can still show committed spend and how to reconcile older reservations without erasing accounting history.
Check an owned number before enabling agent voice
Verify number ownership, Telnyx routing, allowed peers and voice admission before planning an agent conversation.
Check browser proxy support before wiring products together
Understand why a proxy user does not automatically route a Lupin Cloudflare Browser Run session.
Check provider readiness separately from permissions and quotas
Discover configured capabilities, then verify that the current workspace may actually use the requested resource.