docs(seqera-ai): align Enterprise Co-Scientist docs for 26.1#1381
Draft
llewellyn-sl wants to merge 2 commits intoenterprise-26.1-documentationfrom
Draft
docs(seqera-ai): align Enterprise Co-Scientist docs for 26.1#1381llewellyn-sl wants to merge 2 commits intoenterprise-26.1-documentationfrom
llewellyn-sl wants to merge 2 commits intoenterprise-26.1-documentationfrom
Conversation
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
bebosudo
reviewed
May 4, 2026
| ```bash | ||
| export SEQERA_AUTH_DOMAIN=https://cloud.seqera.io/api | ||
| export SEQERA_AUTH_DOMAIN=https://platform.example.com/api | ||
| export SEQERA_AUTH_CLI_CLIENT_ID=seqera_ai_cli |
Member
There was a problem hiding this comment.
Suggested change
| export SEQERA_AUTH_CLI_CLIENT_ID=seqera_ai_cli |
this doesn't seem to be needed
Member
There was a problem hiding this comment.
I added these 4 to my shell when trying to get the CLI working. TBD if they were all necessary:
- `SEQERA_AI_BACKEND_URL`
- `SEQERA_AUTH_DOMAIN`
- `SEQERA_AUTH_CLI_CLIENT_ID`
- `TOWER_ACCESS_TOKEN`
gwright99
reviewed
May 4, 2026
Member
gwright99
left a comment
gwright99
left a comment
There was a problem hiding this comment.
Commented on the parts of this PR which touched upon deployment. I did not review the "how to use the CLI" since this was not part of my efforts last week.
| - **Token encryption key** for encrypting sensitive tokens at rest. Generate with: | ||
| - Seqera Platform Enterprise 26.1 or later deployed with the [Seqera Platform Helm chart](./platform-helm.md). | ||
| - Helm v3 and `kubectl` installed locally. | ||
| - DNS names and TLS certificates for the Platform, agent backend, MCP server, and portal web interface hosts. |
Member
There was a problem hiding this comment.
If created manually, where are they getting the FQDNs from? Having to look at the Helm chart config?
| - Seqera Platform Enterprise 26.1 or later deployed with the [Seqera Platform Helm chart](./platform-helm.md). | ||
| - Helm v3 and `kubectl` installed locally. | ||
| - DNS names and TLS certificates for the Platform, agent backend, MCP server, and portal web interface hosts. | ||
| - Access to pull the `agent-backend`, `mcp`, and `portal-web` images from `cr.seqera.io`, or mirrored copies in your internal registry. |
Member
There was a problem hiding this comment.
Define repo? How does this align to the comments @bebosudo made today about the new proxy sites?
| - Helm v3 and `kubectl` installed locally. | ||
| - DNS names and TLS certificates for the Platform, agent backend, MCP server, and portal web interface hosts. | ||
| - Access to pull the `agent-backend`, `mcp`, and `portal-web` images from `cr.seqera.io`, or mirrored copies in your internal registry. | ||
| - A MySQL 8 database for the agent backend. You can use the same MySQL instance as Platform with a separate database and user, or a separate instance. |
Member
There was a problem hiding this comment.
Minor version? I assume we want 8.4?
| - DNS names and TLS certificates for the Platform, agent backend, MCP server, and portal web interface hosts. | ||
| - Access to pull the `agent-backend`, `mcp`, and `portal-web` images from `cr.seqera.io`, or mirrored copies in your internal registry. | ||
| - A MySQL 8 database for the agent backend. You can use the same MySQL instance as Platform with a separate database and user, or a separate instance. | ||
| - A Redis 7 instance for agent backend task coordination. |
Member
There was a problem hiding this comment.
Minor version? 7.2.x or something else?
Talk about Valkey support?
| - Keep the agent backend token encryption key stable across upgrades. Changing it prevents the backend from decrypting existing encrypted values. | ||
| - MCP uses the user's Platform token to call Platform APIs. The agent backend does not need a separate long-lived Platform service credential for user-scoped tool calls. | ||
| - Use separate MySQL credentials for the agent backend database. | ||
| - Enable Redis TLS and MySQL TLS when your managed services require encrypted connections. |
Member
There was a problem hiding this comment.
See earlier comment about Valkey
| See [Authentication](./authentication.md) for a comprehensive authentication guide. | ||
|
|
||
| If you are testing a development build of the CLI against the hosted production Seqera AI service, see [Install Seqera AI](../enterprise/install-seqera-ai.md#connect-the-cli-to-seqera-ai) for the required environment variables. | ||
| For Enterprise deployments, set `SEQERA_AI_BACKEND_URL` to your organization's agent backend before you start Co-Scientist. See [Authentication](./authentication.md#connect-to-an-enterprise-backend) for the full environment variable reference. |
Member
There was a problem hiding this comment.
Is this on the Platform config page?
| ### npm install | ||
|
|
||
| ```bash | ||
| npm install -g seqera |
Member
There was a problem hiding this comment.
Pretty sure I saw this covered somewhere else too? (Maybe that was the internal docs rather than external)?
Contributor
There was a problem hiding this comment.
They're in the Enterprise installation docs and this is the CLI installation section so it's somewhat duplicated.
| @@ -0,0 +1,112 @@ | |||
| --- | |||
| title: "Modes" | |||
Member
There was a problem hiding this comment.
Did not do this as part of install. Not commenting.
justinegeffen
changed the base branch from
master
to
enterprise-26.1-documentation
llewellyn-sl
force-pushed
the
26-1-docs-update
branch
from
239f207 to
403a157
Compare
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.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
4 participants
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.
Summary
Validation
git diff --checkplatform-enterprise_docs/enterprise-sidebar.jsonNotes