docs: document the [opik_cc] config section - #13
Merged
Conversation
Document how to set a separate workspace/project for Claude Code traces via an [opik_cc] section in ~/.opik.config, and note that it must be placed below [opik] since later keys override earlier ones in the current parser. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jverre
force-pushed
the
jacques/readme-updates
branch
from
June 3, 2026 10:41
f97ac47 to
b50acae
Compare
jverre
changed the title
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Document how to send Claude Code traces to a different workspace/project than the rest of your Opik setup, using a dedicated
[opik_cc]section in~/.opik.config:Why
This already works with the released plugin — confirmed against the exact config from the field. No code change needed.
The one caveat worth documenting: the current parser reads recognized keys (
workspace,project_name,url_override,api_key) from the whole file with later values overriding earlier ones, so[opik_cc]must be placed below[opik]for its values to win. The doc calls this out, and notes thatOPIK_CC_WORKSPACE/OPIK_CC_PROJECTenv vars always take precedence over the file.Docs-only — no
config.gochanges.🤖 Generated with Claude Code