> ## Documentation Index
> Fetch the complete documentation index at: https://docs.domino.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Domino 6.3.0 (August 2026) (LA)

Additional component updates are available in [ddlctl and fleetcommand-agent Release Notes](/6.3/admin/installation/releases).

## Improvements

### Workspace coding assistants

Domino Workspaces now include built-in support for AI coding assistants as part of the Domino Standard Environment, enabling model developers to accelerate data analysis, model training, and validation workflows directly from their workspace.

* Domino now includes built-in support for three coding agents: Copilot, Claude Code, and Codex. For VS Code workspaces, all three are available as pre-installed extensions. Claude Code and Codex are also available as CLI tools in any workspace IDE, including the VS Code terminal.

* Coding assistants are Domino-aware. Agents automatically detect that they are running inside a Domino project and interact with platform resources including datasets, jobs, and registered models.

* A new skills framework extends coding assistant capabilities with Domino-specific actions, including AI-assisted modeling, experiment tracking, job execution, model deployment and monitoring, app initialization and deployment, distributed computing, data connectivity, Gen AI tracing, and more.

* Home directory persistence saves coding agent extensions and settings across workspace restarts.

* CLI agents retain chat history independently, without requiring home directory persistence.

### Deployment identification for product analytics

Domino now supports tagging product analytics events with `customer_name` and `deployment_name`, identifying your organization and environment.

* We recommend setting these values, and keeping them consistent afterward. You can set them at install time or any time afterward by running the deployer. Doing so helps Domino Support quickly identify your deployment when you reach out, so we can resolve issues faster.

* Both values can also be changed afterward through a configuration record, without reinstalling or upgrading. As with any configuration record change, a restart of the Domino services is required for the update to take effect. See [Deployment identification](/6.3/admin/configuration/deployment-identification) for the full configuration reference.

## Bug fixes

## Known issues

* When working with Workspace coding assistants, if you are authenticating a coding agent for the first time, the link in the popup dialog does not work. To complete authentication, copy the URL displayed in the terminal and open it in your browser.

* Domino skills might not work by default for coding agents other than Claude Code.

* In some cases, the VS Code Claude Code extension panel appears blank. To fix this, refresh your browser.

* Codex needs to be authenticated from the terminal (CLI) before it can be used by the VS Code extension.

* After upgrading to version 6.1.1 from 6.1.0, Workspaces running in the local data plane with SSH enabled must be restarted once to retain SSH access.

* Flows is only supported in Domino Cloud, AWS, and Azure. A future update will add support for Google Cloud and on-premises installs.

* Some Flyte features are not yet available in Flows, such as [dynamic workflows](https://docs.flyte.org/en/latest/user_guide/advanced_composition/dynamic_workflows.html) and [map\_task](https://docs.flyte.org/en/latest/user_guide/advanced_composition/map_tasks.html).

* In Azure Blob Store deployments, Projects with many files may fail to sync through the Domino CLI. To work around this issue, do not disable file locking when prompted by Domino.

* You cannot view the latest raw file if you click **View Latest Raw File**. In the navigation pane, go to **Files** and click a file to view its details.

* If idle timeout is configured on a deployment, Domino may not recognize pages opened in spawned tabs (e.g., via `Ctrl+Click`) or outside of an iFrame as being active. Users may be unintentionally logged out despite activity in the spawned pages.

* When uploading a large file to the Azure blob store by [syncing a Workspace](/6.3/platform-capabilities/core-concepts/workspaces/sync-changes-in-a-workspace), you may encounter a Java Out of Memory error from Azure if the file/blob already exists. To work around this issue, use the [Domino CLI](/6.3/reference/cli) to upload the file to the Project.

* Model Monitoring data sources aren’t validated. If you enter an invalid bucket name and attempt to save, the entry will go through. However, you won’t be able to see metrics for that entry, because the name points to an invalid bucket.

* When restarting an RStudio workspace with home directory persistence enabled, the user may see a notice stating that the previous session was abnormally terminated due to a crash. This notice is only due to how the new feature interacts with RStudio and does not result in any data loss.

* Domino instances that make use of Azure Blob Storage may experience stalled Jobs within Projects with many large files.

* If you attach a Git repository to a DFS Project that points to a tagged release, the tag won’t be honored when building a Domino endpoint in that Project. The build log will show an error similar to the following, and the model will be built using the default branch of your Git repository instead of the tagged branch:

  ```
  Jul 05 2023 14:36:27 -0500 #10 6.481 WARN [d.r.d.GitRepoUpdater] could not parse ref: v1.3.0 checking out default branch correlationId="iA2qWrYSLQ" thread="main"
  ```

  To work around this issue, use the branch name when building Domino endpoints instead of the release tag.

* If an admin resets a user’s password, it invalidates all the user’s authentication tokens, including tokens used for long-running tasks like Jobs, Workspaces, or Apps. The user must create a new password, log back into Domino, and restart all executions. This also applies to CLI authentication; the user must re-login to their Domino CLI.

* Data storage page fails to load when the dataplane agent in the remote data plane is scaled down to zero.

* Nucleus Dispatcher restart hangs during Quartz Scheduler startup following a MongoDB replica set scale-down. As a workaround, manually remove the unavailable replica from the replica set using the Mongo CLI command.

* During a 48-hour soak test, the `nginx-ingress-controller` pods exhibited a gradual increase in memory usage while handling heavy Domino Endpoint workloads. The cause is under investigation.

* Agent monitoring dashboard retains only the current day’s data (charts have missing data and traces are gone). Historical data from previous days are lost, regardless of what time window is selected.

## Breaking changes and deprecations

* **Project tasks (formerly Project goals) are deprecated.** The Project tasks feature, including task stages and task status, is deprecated in 6.3. Project owners can no longer rely on Domino to track task-level milestones inside a Project; use your organization's issue tracker instead. Project-level [stages](/6.3/platform-capabilities/core-concepts/projects/track-projects/set-project-stages) and [status](/6.3/platform-capabilities/core-concepts/projects/track-projects/set-project-status) are unaffected.

* **The Project-level Jira integration is removed.** Domino no longer supports linking a Domino Project to a Jira ticket or syncing Domino tasks with Jira subtasks. Any existing per-Project Jira credentials and links are no longer honored. Administrators no longer need to configure an application link between Domino and Jira for this feature.

## Validated frameworks

## Upgrade notes

* NGINX ingress now runs a FIPS-validated OpenSSL that drops the legacy static-RSA TLS ciphers. If you set an explicit `ssl-ciphers` override and front NGINX with an AWS Classic Load Balancer over TLS, update it before upgrading or the installer stops with a configuration error. Default installs and NLB/ALB deployments are unaffected. See [Deploy Domino on AWS EKS](/6.3/admin/installation/manage-deployments/aws/deploy).

* Component and compatibility updates this release:

  * OpenShift version compatibility has been updated to 1.34 (OpenShift 4.21).

  * GKE version compatibility has been updated to 1.35.

  * AKS version compatibility has been updated to 1.35.

  * EKS version compatibility has been updated to 1.35.

  {/* - RabbitMQ version remains at 4.1.2. */}