- Problem: When you authenticate a coding agent for the first time, clicking the link provided in the pop-up dialog does not open the authentication page.
- Workaround: Manually copy the URL displayed in the terminal output and paste it into your browser to complete the authentication flow.
-
Problem: Skill steps that call the Domino MCP server’s tools, such as
run_domino_job, don’t run in Codex or GitHub Copilot. - Details: The Domino Standard Environment copies the Domino Skills for Codex and GitHub Copilot, but only Claude Code gets the Domino MCP server. When the server’s tools are missing, the modeling assistant skill in the current plugin release says so and runs Jobs through the Domino REST API instead; see Domino skills reference for the current release.
- Workaround: Use Claude Code for tasks that need the Domino MCP server’s tools.
- Problem: After a Workspace’s environment moves to a newer image, Codex and GitHub Copilot in that Workspace keep the Domino Skills from the image the Workspace first launched with.
-
Details: The Domino Standard Environment copies the skills into
~/.codexand~/.copilotwhen the image is built. The first time a Workspace starts, Domino saves a copy of those directories with the Workspace, and every later session restores the saved copies instead of using the image’s. The saved~/.codexalso keeps the Codex CLI version from that first image. Claude Code is different: each time a Workspace starts, Domino updates its skills from GitHub while thecom.cerebro.domino.workbench.workspace.updateSkillsOnLaunchconfiguration record istrue, the default. The update needs access to GitHub and must finish within 10 seconds; otherwise Claude Code keeps its current copy. On the 6.3.0 Domino Standard Environment image, the update pulls from the deprecateddomino-claude-pluginrepository; see Preinstalled in Workspaces. - Workaround: Start a new Workspace. Codex and GitHub Copilot in it get the skills from the environment’s current image. Commit or sync your work first: the new Workspace starts without the old one’s saved agent sign-ins and chat history.
- Problem: In some cases, the VS Code Claude Code extension panel renders as a blank white or empty area after opening.
- Workaround: Refresh your browser page. The panel renders correctly after a page reload.
- Problem: When using Claude Code, the agent defaults to a model tier such as Opus, which may differ from your preferred setting.
- Workaround: Change the active model in the Claude Code panel. The model selector appears at the top of the Claude Code interface. Click to switch to your preferred tier like Sonnet, Opus, etc.