[NA][FE] fix: include workspace name in agent onboarding prompt#5923
[NA][FE] fix: include workspace name in agent onboarding prompt#5923AndreiCautisanu wants to merge 1 commit intomainfrom
Conversation
Without the workspace, the SDK defaults to "default" which causes 401 errors on Opik Cloud. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
💡 suggestion | Completeness The Consider adding a workspace name field alongside the existing ones, using the same 👋 Review summary What looks good
Overall Inline comments: 1 suggestion (non-blocking, follow-up scope) 🤖 Review posted via /review-github-pr |
JetoPistola
left a comment
There was a problem hiding this comment.
Looks good — clean, minimal fix. The workspace suggestion for ManualIntegrationList can be a follow-up.
|
|
||
| const buildPrompt = (shouldMaskAPIKey: boolean) => | ||
| `Instrument my agent with Opik, use project name "${agentName}"${ | ||
| workspaceName ? `, workspace "${workspaceName}"` : "" |
There was a problem hiding this comment.
| workspaceName ? `, workspace "${workspaceName}"` : "" | |
| workspaceName ? `, workspace name "${workspaceName}"` : "" |
Since it's not an ID, we should have it be name
Details
The agent onboarding "Install with AI" prompt includes the project name and API key but not the workspace name. Without
OPIK_WORKSPACE, the SDK defaults to"default"which causes401 User not allowed to access workspaceerrors on Opik Cloud.This adds the active workspace name to the generated prompt so the coding agent sets
OPIK_WORKSPACEcorrectly.Change checklist
Issues
AI-WATERMARK
AI-WATERMARK: yes
Testing
cd apps/opik-frontend && npm run lint— passesInstrument my agent with Opik, use project name "X", workspace "Y" and API key "Z". Once you are ready...Documentation
N/A
Companion PR for opik-skills: https://github.com/comet-ml/opik-skills/pull/2