You should have completed the Installation and
Authentication sections before proceeding. If
you haven’t, please complete them first.
How the Narada SDK Works
The Narada Python SDK uses two core objects:Environment
An environment is the execution target. Use
BrowserEnvironment for a local browser, CloudBrowserEnvironment for a hosted browser, RemoteBrowserEnvironment for an existing browser window, or LambdaEnvironment for cloud execution without browser actions.Agent
An agent runs tasks inside an environment. Create
Agent(environment=env) and call await agent.run(...) for natural-language automation.go_to_url(), agentic_selector(), and Google Sheets helpers are methods on Agent. Lifecycle details such as close(), browser_window_id, and cloud_browser_session_id are methods or properties on the environment.
You do not need to prefix prompts with
/Operator when using Agent.run(). The default agent kind is AgentKind.OPERATOR, which adds the correct command prefix for browser automation.Demo: Narada SDK in Action
Watch this demonstration of the complete SDK workflow:Your First SDK Automation
Start with a simple local browser automation:The first time you run a local browser environment, the SDK opens Chrome and guides you through any missing extension or login setup. The environment initializes lazily on the first
Agent.run() call or browser action.Eagerly Initialize the Browser
You can callawait env.start() when you need the browser window ID before running a task:
Structured Output
Use a Pydantic model when you need typed data instead of free-form text:Choose an Agent Kind
The defaultAgent uses AgentKind.OPERATOR, which is best for browser automation. Use AgentKind.CORE_AGENT for read-only reasoning and conversation-style tasks.
Error Handling
The SDK raises typed exceptions for common failures:Troubleshooting
SDK won't start
SDK won't start
- Verify
NARADA_API_KEYis set. - Make sure Chrome is installed and up to date.
- Install and sign in to the Narada Chrome extension.
- Check your internet connection and firewall settings.
Automation fails
Automation fails
- Make prompts clear and specific.
- Increase
timeoutfor complex tasks. - Wait for slow pages to load before asking the agent to inspect them.
- Call
await agent.reset_agent_state()after a timeout to cancel inflight work while preserving browser pages.
What’s Next?
Parallel Execution
Run multiple browser environments simultaneously
Error Handling
Handle timeouts, retries, and initialization errors
Structured Output
Extract typed data using Pydantic models
Action Trace
Capture and analyze automation workflows
Need Help?
GitHub Examples
Explore complete SDK examples
Support
Contact support for assistance