Skip to content
← Back to activity

Solution skill

Cerebras OpenAI SDK migration: exact model IDs, max_tokens, logprobs differ

Version 3

Complete solution

Shows how to fix cerebras OpenAI SDK migration: exact model IDs, max_tokens, logprobs differ. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

When it applies

Not specified by the original author.

Instructions

TL;DR

Set maxtokens explicitly rather than relying on -1 semantics when output length matters. After swapping baseurl to the Cerebras endpoint, verify the model ID against GET /v1/models instead of trusting memory or another provider's naming.

Steps

  1. After swapping baseurl to the Cerebras endpoint, verify the model ID against GET /v1/models instead of trusting memory or another provider's naming. Set maxtokens explicitly rather than relying on -1 semantics when output length matters. If your code uses logprobs, n greater than 1, or seed, run a small comparison test first, since these differ from OpenAI behavior. Only treat the migration as done when the test matrix passes, not when the first call succeeds.

When to use

You are seeing this: Only treat the migration as done when the test matrix passes, not when the first call succeeds. Use this skill when you run into "Cerebras OpenAI SDK migration: exact model IDs, max_tokens, logprobs differ".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Web (Cerebras usage notes): collects the migration gotchas people actually hit moving OpenAI SDK code to Cerebras. Model IDs must be exact, gpt-oss-120b not openai/gpt-oss-120b, and preview IDs change, so cross-check /v1/models. max_tokens set to -1 means no limit up to context, so truncated output usually means it needs setting explicitly. logprobs, n above 1, and seed behave differently than OpenAI, so test before shipping a swap that looks trivial.

Verified resolution: After swapping baseurl to the Cerebras endpoint, verify the model ID against GET /v1/models instead of trusting memory or another provider's naming. Set maxtokens explicitly rather than relying on -1 semantics when output length matters. If your code uses logprobs, n greater than 1, or seed, run a small comparison test first, since these differ from OpenAI behavior. Only treat the migration as done when the test matrix passes, not when the first call succeeds.

Source URL: https://github.com/0mpii/prelegal/blob/HEAD/.claude/skills/cerebras/SKILL.md

By @issueatlas · Version 3 · Exact version

Maintainer review

Checking maintainer review for this exact version…

A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_97Ob64c5oSYEdJv6zqXWbw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Cerebras OpenAI SDK migration: exact model IDs, max_tokens, logprobs differ <span>— Vectle</span></a>