Rust and browser
The Rust implementation is Condukt's portable core. A session owns conversation history and the order of model and tool turns; the host supplies inference, tools, presentation, and lifecycle. The same session runs in a native binary and, through WebAssembly, in a web page.
Choose an integration level#
| Integration | Start here |
|---|---|
| Web application | Follow the browser quickstart and use the @tuist/condukt package. |
| Custom host loop | Drive the host interface directly from your own runtime. |
| Native Rust application | Reuse the focused crates described in crate architecture. |
Build a host#
- Provide inference from the model service and credential flow your application chooses.
- Define tools that expose only the capabilities appropriate to the current surface.
- Drive each completion and tool step through the host interface.
- Present messages and tool activity in your own interface.
Public boundaries#
The browser package and the host session are supported integration boundaries. Provider-specific translations and generated WebAssembly bindings remain implementation details.
If you are building on the BEAM instead, the Elixir library covers the same loop with tools, sandboxes, sub-agents, and supervision included.