Build with AgenticDriver
On this page
Choose your starting pointInstall the current previewWhat you can buildYour application stays in controlKnow the supported scopeBuild with the agents your users already have. AgenticDriver connects your application to explicitly selected provider subscriptions, installed CLI sessions or API keys — locally or over authenticated HTTPS.
Choose your starting point
- Install & connect — set up a host and make your first request.
- Desktop companion — manage providers, connections and usage on Linux.
- SDK clients — build in JavaScript, TypeScript, Python, Go or Rust.
- Remote connections — connect your application's backend to another machine.
Install the current preview
npm install @agenticdriver/sdk@rcThe rc channel tracks the current release candidate. Your lockfile records the installed version. The npm latest channel remains the earlier stable release.
Python is available as a wheel download while PyPI approval is pending. Find all four language examples in Install & connect.
What you can build
| Capability | Start here |
|---|---|
| Explicit provider, account and model choice | Discovery |
| Streaming, tool progress and cancellation | Execution controls |
| Application tools and approval decisions | Tools · Approvals |
| Scoped retrieval with source revisions and citations | Retrieval · Ingestion |
| Local execution or a remote host | Host setup · Connections |
| Usage reporting to your existing backend | Usagestat |
Your application stays in control
Your app owns authentication, data, tools and approval decisions. Embedding the SDK requires no AgenticDriver account or extra login service. Provider credentials stay on the execution host; clients use separately scoped host credentials.
Choose the provider, account and model explicitly. There is no automatic account or billing fallback, and no default generation deadline or inactivity timeout. Inactivity cancellation is opt-in.
Updating an existing installation? Upgrade the host before management clients, preserve accounts and grants, and check advertised capabilities. A matching wire version alone does not guarantee compatibility. See Upgrading.
Know the supported scope
The desktop archive is qualified for Linux x64. Native execution evidence covers the selected Codex and Claude Code subscriptions and models; discovery does not establish successful execution for every model. See Compatibility and Current qualification for the recorded scope.
These guides reuse the maintained SDK documentation. Historical validation reports are dated evidence, not new installation instructions.