Integrations
Maida is framework-agnostic at its core. Adapters translate framework callbacks into the same LLM_CALL and TOOL_CALL structure; framework-specific details remain in meta, and every payload passes through Maida’s redaction and truncation before local storage.
Download the deterministic offline examples directly:
Shared contract
Framework packages are optional and loaded only when their adapter is imported.
Equivalent model and tool activity produces framework-neutral trace events.
Adapters require an active @trace or traced_run(...); they never create unrelated runs.
Framework errors remain the application’s errors and are recorded as error-status activity.
Prompts, responses, arguments, results, errors, and metadata use the same recursive redaction and byte limits as direct SDK calls.
If an optional dependency is absent, importing its adapter fails immediately with an ImportError that names the required Maida extra. Core Maida remains importable without any framework installed.