This release is a pre-release and may not be stable for production use.
vibe_agents_sdk
SDK for integrating with the vibe_agents platform.
The first Unified Harness backend release and its exact local/remote support
matrix are documented in
docs/unified-harness-backend.md.
Agent folders authored with mistralai.agents use the Unified Harness remote
runtime by default. The Nuage folder loader rejects them; use
mistralai.agents.alpha for legacy Nuage agents.
The long-term system boundaries, dependency direction, and delivery plan are
documented in
docs/agents-sdk-harness-target.md.
The shared pytest and manual QA entrypoint is documented in
docs/unified-harness-qa.md.
Successful local session creation emits agents.session_started telemetry with stable identifiers and bounded
dimensions. Failed startup emits no success event.
- PyPI / distribution name:
mistralai-agents - Import path:
mistralai.vibe_agents(PEP 420 namespace package)
Layout follows the mistralai-workflows pattern: a single package
that, over time, will host both the handwritten SDK (contract types,
IntegrationManager client) and any Speakeasy-generated clients for the
vibe_agents HTTP API as sibling submodules.
What's in this package
Three stable submodules today, plus the private-preview alpha agents bundle:
-
mistralai.vibe_agents.session_workflow— pure type contract for session workflows:SessionStartIntent,SessionWorkflowStartInput/SessionWorkflowOutputincludingpublic_final_messagefor concise end-user termination text andfailure_codefor stable failed-session categories,SessionWorkflowCommanddiscriminated union and subtypes,Principal,SessionWorkflowSubscription,Toolset(per-session connector toolset binding, identified byidorname),WorkflowSessionEvent,WorkflowSessionEventType,SESSION_EVENT_TASK_TYPE, and the shared Task ProtocolHistoryEntry/StateEntry/TaskStatepayload models.Principalrequires distinctcustomer_id,organization_id, andworkspace_idUUIDs;user_idis optional.workflow_nameanddeployment_nameare control-plane dispatch metadata, not durable workflow input fields. Imported by any runtime that implements the vibe_agentsSessionWorkflowcontract. Hard dependencies are kept minimal:pydantic,structlog,typing-extensions. Emission is a one-linerworkflows.task(SESSION_EVENT_TASK_TYPE, state=WorkflowSessionHistoryEntryEvent(...).model_dump())at the caller using the concrete event variant for the row being emitted. Slack-specific integration-event helpers undersession_workflow.integration_events.slackdepend on theintegration-eventsextra. They include typed channel-scopedagent_session_stoppedcontrol events. -
mistralai.vibe_agents.integration_manager— shared IntegrationManager capability contracts and identity models, including typed Slack session status and rename operations plus code-channel creation, property updates, archival, and block-only message updates that reject empty content. Concrete HTTP clients live inmistralai.vibe_agents.integration_manager.clientand the live runtime builder lives inmistralai.vibe_agents.integration_manager.runtime; those pieces depend onhttpxbehind theintegration-managerextra. -
mistralai.vibe_agents.sessions— typed HTTP client and response models for the vibe_agents sessions API, including the nullable generated session title read field. The concrete client depends onhttpxbehind thesessions-clientextra. -
mistralai-agents-sdk-alpha— private-preview Cloudsmith bundle that installs the alpha Nuage agents runtime. It exposesfrom mistralai.agents.alpha import agents.
Future
A Speakeasy-generated client for the vibe_agents HTTP API will be added as
a sibling submodule, under mistralai.vibe_agents.<name>.*. Same package,
same distribution. This mirrors the mistralai-workflows setup where
mistralai.workflows.worker_client (autogen) lives inside the same
package as the handwritten workflow SDK.
Import discipline
The root __init__.py does NOT eagerly import the integration_manager
submodule. Importing only session workflow or IntegrationManager contract types
must not pull in HTTP client dependencies. Import concrete submodules
explicitly:
from mistralai.vibe_agents.session_workflow import SessionWorkflowStartInput
from mistralai.vibe_agents.integration_manager.client import IntegrationManagerClient
The alpha agents runtime (mistralai.agents.alpha) is documented separately - install,
quickstart, capabilities, and customization are on the official site:
https://docs-internal-frameworks.mistral.ai/agents-sdk/ (or the local quickstart in
ALPHA.md). Fastest way to install and play:
npx openskills install mistralai/dashboard/vibe_agents/nuage_v2/docs/skills/agents-sdk-alpha-helper.
What this package does NOT contain
vibe_agentsservice code. The service lives in its own package.- Any dependency on
vibe_agents. Runtimes using this SDK MUST NOT transitively pull in thevibe_agentsservice.
Contributing
make lint— ruff format check + ruff checkmake typecheck— mypymake test— pytest (includes fuzz + integration tiers; excludes perf)make test-unit— unit tier only (excludes fuzz, integration, perf); CI runs this as its own jobmake coverage— pytest with branch coverage + missing-line reportmake fuzz— Hypothesis property tests over the parse/fold surfacesmake test-integration— real client vs in-process fake ASGI servermake perf— informational pytest-benchmark microbenchmarks (never gated)make format— ruff format + fixmake installdeps— uv sync
Bundle wheel tree-shake (keep scripts/build_bundle_wheel.sh in sync)
scripts/build_bundle_wheel.sh packs the alpha SDK into one wheel and
tree-shakes subtrees the import closure never loads via a hand-maintained
PRUNE list. That list is an invariant tied to what the SDK imports, so it can
drift when imports change. When you add, move, or remove an import in the SDK
closure (or a dynamically/registry-loaded module such as a nuage integration,
a polymorphic_type, a vibe.core tool, or a kazekit subpkg), re-check the
PRUNE list: build the wheel, import it in a clean env, and confirm nothing it
pruned is now needed. Do not prune anything loaded dynamically rather than via a
static import.
Release files for mistralai-agents 1.1.0rc3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mistralai_agents-1.1.0rc3.tar.gz | 328.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mistralai_agents-1.1.0rc3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 613.5 kB
Release files / mistralai_agents-1.1.0rc3.tar.gz
| Download URL | mistralai_agents-1.1.0rc3.tar.gz |
|---|---|
| Size | 328.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4561e002b0795455ce4de0351964a985009c4c7168ce68810dd7f211923dccfb
|
|
BLAKE2b-256 checksum How to use checksums |
08b8481b505d2ee8390948890fc70407e9d238b0981f219348d575828f24c621
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / mistralai_agents-1.1.0rc3-py3-none-any.whl
| Download URL | mistralai_agents-1.1.0rc3-py3-none-any.whl |
|---|---|
| Size | 285.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6a4b561f71aa7957459b289cb0a3567556727d1a4c32665429f888ef2213de0
|
|
BLAKE2b-256 checksum How to use checksums |
933d87152b4ddd96bea8084e9354fe63f69281b43ff8666ae548c9da224df18e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency log