Treat client cancellation as a deadline, not provider cancellation
Design application cancellation so a stopped HTTP wait cannot silently become a replacement paid action or an untracked running resource.
Lupin field guides
More guides. More useful agents.
Articles 181–198 of 200
Treat phone calls and SMS as separate agent capabilities
Map messaging profiles, voice connections, permissions and asynchronous outcomes before sharing a number between workflows.
Treat web page instructions as untrusted content
Keep a website’s text separate from the user’s authority when researching or acting through a browser.
Understand a sandbox’s isolation and authority
Separate hosted execution isolation from command authorization, network access and secret handling.
Understand an autonomous agent’s bootstrap permissions
Use reception, reading and drafts while keeping sending, key creation and paid effects outside the bootstrap boundary.
Understand proxy allocation, remaining traffic and usage
Separate allocated megabytes, remaining balance, derived usage and the retail billing event before setting a proxy budget.
Understand recipient restrictions before sending agent email
Separate autonomous registration, human-email verification and recipient lists so denied sends have a clear remedy.
Understand Scribe v2 Realtime in a phone audio pipeline
Follow audio formatting, partial text, manual commits and recognizer preparation without attributing the entire agent to ASR.
Understand what a browser page read contains
Interpret visible text, links and controls without mistaking a bounded page snapshot for the entire DOM or a structured application API.
Understand what stop and resume mean for a sandbox
Use the supported lifecycle without assuming memory checkpointing, permanent retention or unchanged processes after resume.
Use agent run traces to diagnose behavior without replaying actions
Inspect selected context, approvals and tool outcomes while respecting privacy, retention and measurement limits.
Use browser screenshots as visual evidence
Capture bounded JPEG screenshots, pair them with page observations and avoid treating a picture as proof of an action outcome.
Use email labels without bypassing spam visibility controls
Separate workflow labels from system states and account for protected messages in searches and summaries.
Use Lupin’s checked-in SDK and CLI without assuming public packages
Choose direct HTTPS or authorized source clients, then verify real operation coverage before building automation.
Use parsed email fields and raw MIME for different jobs
Keep normal agent reading simple while retaining a path to inspect original MIME structure and headers.
Validate MCP tool arguments against discovered JSON schemas
Use the concrete schema to reject unknown fields, missing identities and ambiguous provider versions before execution.
Verify agent code with a small local fixture
Use deterministic inputs and semantic assertions to test transformation logic without making paid or consequential live calls.
Verify email webhook signatures against the raw request body
Check signatures, timestamps and event identity without trusting parsed or reconstructed payloads.