Managed Agents run on cloud infrastructure, automatically provisioning compute resources and managing execution environments.Documentation Index
Fetch the complete documentation index at: https://docs.praison.ai/llms.txt
Use this file to discover all available pages before exploring further.
Quick Start
How It Works
Security Model
Managed agents enforce sandbox-first security by default. Package installation requires a compute provider or explicit opt-out to prevent host system security risks.- Compute-bridged tools:
execute_command,read_file,write_file,list_filesautomatically execute in sandbox when compute provider is attached - ManagedSandboxRequired: Exception raised when packages are specified without proper sandboxing (see Local Provider security details)
| Component | Purpose | Managed By |
|---|---|---|
| Agent Definition | Model, system prompt, tools | Cloud Provider |
| Environment | Compute resources, packages | Cloud Provider |
| Session | Conversation context, state | Cloud Provider |
| Execution | Code running, tool usage | Cloud Provider |
Compute Providers
Managed Agents support multiple compute providers for different use cases:Local Provider
Run on local infrastructure with cloud management
Docker Compute
Containerized execution environments
E2B Cloud
Instant cloud sandboxes for code execution
Modal Compute
Serverless compute for scalable workloads
Daytona Workspaces
Development environments with persistent storage
Configuration Options
ManagedConfig API Reference
Complete configuration options for managed agents
Key Configuration Fields
| Option | Type | Default | Description |
|---|---|---|---|
model | str | "claude-haiku-4-5" | LLM model to use |
system | str | "You are a helpful coding assistant." | System prompt |
tools | List[Dict] | [{"type": "agent_toolset_20260401"}] | Available tools |
packages | Dict[str, List[str]] | None | Package dependencies. Requires compute provider by default (security details) |
networking | Dict[str, Any] | {"type": "unrestricted"} | Network access policy |
Custom Backend Development
Build a custom managed backend by implementing the protocol:Common Patterns
Environment with Packages
Session Persistence
Custom Tools
Best Practices
Choose the Right Compute Provider
Choose the Right Compute Provider
- Local: Development and testing with existing infrastructure
- Docker: Isolated, reproducible environments
- E2B: Quick prototyping and sandboxed execution
- Modal: High-performance, scalable workloads
- Daytona: Development environments with persistence
Manage Sessions Effectively
Manage Sessions Effectively
Save session IDs for resuming conversations across process restarts. Use
save_ids() and restore_ids() to maintain context between runs.Configure Security Appropriately
Configure Security Appropriately
Use
networking: {"type": "limited"} for untrusted code execution. Enable only required packages to minimize attack surface. The new host_packages_ok flag and ManagedSandboxRequired exception provide additional security controls - see Local Provider security details.Monitor Resource Usage
Monitor Resource Usage
Track token usage with
retrieve_session() — returns a unified schema (id, status, title, usage) on all backends. See the SessionInfo Schema page for details.Related
Agents
Core agent concepts and configuration
Tools
Available tools and custom tool creation

