Summary
Cerebras publishes an official TypeScript SDK for their ultra-fast LLM inference API: @cerebras/cerebras_cloud_sdk on npm (v1.64.1, actively maintained). It provides execution APIs for chat completions, completions, embeddings, and streaming responses. The SDK has its own HTTP client based on node-fetch — it does not depend on the openai npm package. This repository has zero instrumentation for any Cerebras SDK surface — no wrapper, no channels, no plugin, no auto-instrumentation config. Users who call @cerebras/cerebras_cloud_sdk directly get no Braintrust spans.
What instrumentation is missing
The @cerebras/cerebras_cloud_sdk npm package exposes these execution surfaces, none of which are instrumented:
| SDK Method |
Description |
client.chat.completions.create({ model, messages }) |
Chat completions with tool use, structured outputs, and reasoning |
client.chat.completions.create({ ..., stream: true }) |
Streaming chat completions |
client.completions.create({ model, prompt }) |
Raw text completions |
client.embeddings.create(...) |
Text embeddings |
Cerebras is notable for extremely low-latency LLM inference (their wafer-scale hardware delivers tokens significantly faster than GPU-based providers), making observability especially valuable for latency-sensitive production workloads.
No coverage in any instrumentation layer:
- No wrapper function (e.g.
wrapCerebras())
- No diagnostics channels for Cerebras methods
- No plugin handler in
js/src/instrumentation/plugins/
- No auto-instrumentation config in
js/src/auto-instrumentations/configs/
- No e2e test scenarios
- Grep for
cerebras (case-insensitive) across js/src/ returns zero matches
Indirect coverage is insufficient:
Braintrust's Cerebras integration page documents a gateway/OpenAI SDK approach only — using the openai npm client pointed at the Braintrust gateway to route to Cerebras models. Users who call @cerebras/cerebras_cloud_sdk directly get no spans at all. The Cerebras SDK has its own separate HTTP layer (runtime deps: node-fetch, abort-controller, agentkeepalive, form-data-encoder, formdata-node) and is not patched by the existing openai auto-instrumentation.
Braintrust docs status
not_found for direct SDK instrumentation. The Braintrust Cerebras integration page documents a gateway/OpenAI SDK approach only and does not reference @cerebras/cerebras_cloud_sdk.
Upstream references
Local files inspected
js/src/auto-instrumentations/configs/ — full config list: anthropic.ts, openai.ts, ai-sdk.ts, groq.ts, mistral.ts, cohere.ts, huggingface.ts, google-genai.ts, google-adk.ts, genkit.ts, openai-agents.ts, openrouter.ts, openrouter-agent.ts, claude-agent-sdk.ts, cursor-sdk.ts, github-copilot.ts, openai-codex.ts, flue.ts — no Cerebras config present
js/src/wrappers/ — no cerebras.ts wrapper file
js/src/instrumentation/plugins/ — no Cerebras channels or plugin
e2e/scenarios/ — no Cerebras test scenarios
- Full repo grep for
cerebras (case-insensitive) in js/src/ — zero matches
- Cerebras SDK
package.json (GitHub) — confirmed runtime deps are node-fetch/agentkeepalive/form-data-encoder; no openai dependency
Summary
Cerebras publishes an official TypeScript SDK for their ultra-fast LLM inference API:
@cerebras/cerebras_cloud_sdkon npm (v1.64.1, actively maintained). It provides execution APIs for chat completions, completions, embeddings, and streaming responses. The SDK has its own HTTP client based onnode-fetch— it does not depend on theopenainpm package. This repository has zero instrumentation for any Cerebras SDK surface — no wrapper, no channels, no plugin, no auto-instrumentation config. Users who call@cerebras/cerebras_cloud_sdkdirectly get no Braintrust spans.What instrumentation is missing
The
@cerebras/cerebras_cloud_sdknpm package exposes these execution surfaces, none of which are instrumented:client.chat.completions.create({ model, messages })client.chat.completions.create({ ..., stream: true })client.completions.create({ model, prompt })client.embeddings.create(...)Cerebras is notable for extremely low-latency LLM inference (their wafer-scale hardware delivers tokens significantly faster than GPU-based providers), making observability especially valuable for latency-sensitive production workloads.
No coverage in any instrumentation layer:
wrapCerebras())js/src/instrumentation/plugins/js/src/auto-instrumentations/configs/cerebras(case-insensitive) acrossjs/src/returns zero matchesIndirect coverage is insufficient:
Braintrust's Cerebras integration page documents a gateway/OpenAI SDK approach only — using the
openainpm client pointed at the Braintrust gateway to route to Cerebras models. Users who call@cerebras/cerebras_cloud_sdkdirectly get no spans at all. The Cerebras SDK has its own separate HTTP layer (runtime deps:node-fetch,abort-controller,agentkeepalive,form-data-encoder,formdata-node) and is not patched by the existingopenaiauto-instrumentation.Braintrust docs status
not_foundfor direct SDK instrumentation. The Braintrust Cerebras integration page documents a gateway/OpenAI SDK approach only and does not reference@cerebras/cerebras_cloud_sdk.Upstream references
@cerebras/cerebras_cloud_sdknpm: https://www.npmjs.com/package/@cerebras/cerebras_cloud_sdkLocal files inspected
js/src/auto-instrumentations/configs/— full config list:anthropic.ts,openai.ts,ai-sdk.ts,groq.ts,mistral.ts,cohere.ts,huggingface.ts,google-genai.ts,google-adk.ts,genkit.ts,openai-agents.ts,openrouter.ts,openrouter-agent.ts,claude-agent-sdk.ts,cursor-sdk.ts,github-copilot.ts,openai-codex.ts,flue.ts— no Cerebras config presentjs/src/wrappers/— nocerebras.tswrapper filejs/src/instrumentation/plugins/— no Cerebras channels or plugine2e/scenarios/— no Cerebras test scenarioscerebras(case-insensitive) injs/src/— zero matchespackage.json(GitHub) — confirmed runtime deps arenode-fetch/agentkeepalive/form-data-encoder; noopenaidependency