Skip to main content

Co-Scientist in Seqera Platform

The Co-Scientist panel is an assistant docked inside Seqera Platform. It opens over the page you are working on and reads that page as context. Ask about a run, pipeline, dataset, or data-link without describing it first.

info

Seqera is rolling out the Co-Scientist panel to Seqera Platform Cloud organizations. If you do not see Co-Scientist in the navigation, contact Seqera to enable it for your organization.

Open the panel​

  1. Sign in to Seqera Platform and open a workspace.
  2. Select Co-Scientist in the navigation.

Your work stays on screen behind the panel. Close the panel to return to where you were, or keep navigating Seqera Platform while the conversation stays open.

Page context​

Co-Scientist reads the page you are viewing and sends that context with each message. The context includes:

  • The organization and workspace you are working in.
  • The primary resource in view, such as a run, pipeline, dataset, or data-link.
  • A screenshot of the page content area.

Co-Scientist scopes its Platform requests to the current organization and workspace, and acts within that workspace unless you ask it to look elsewhere.

Because the panel already has this context, you can ask questions that refer to the page directly:

  • "Why did this run fail?"
  • "What does this pipeline do?"
  • "Summarize the results in this dataset."

Screenshots​

The screenshot captures the main content area of the page. It excludes the navigation, the side menu, and the Co-Scientist panel itself. It includes everything else on the page, such as run logs, parameter values, and resource names.

The current page's screenshot appears as a chip above the message box. Remove the chip before sending if you do not want the screenshot attached to that message.

Conversations and history​

Each conversation is a separate thread. Past conversations are grouped by recency, and you can search them by title to return to earlier work.

When you delete a conversation from the conversation list, it is removed from your account.

Reference resources with @​

Type @ in the message box to reference a Platform resource by name (a pipeline, run, or dataset) and attach it to your message. Use this to bring in a resource other than the one on screen.

Background work​

A request keeps running after you navigate away or switch workspaces. Reopen the panel to see the result. Long-running work draws on the same credits as any other Co-Scientist usage. Check your active conversations before you leave requests running.

Work with GitHub repositories​

Co-Scientist can clone GitHub repositories, create branches, push commits, and open pull requests. It reaches private repositories through the Seqera Co-Scientist GitHub App. You connect your own GitHub account to the app the first time Co-Scientist needs access to a private repository.

This connection is separate from the Git credentials that Seqera Platform uses to launch pipelines.

To connect GitHub:

  1. Ask Co-Scientist to work with a private repository. If you have not connected GitHub, Co-Scientist replies with a link to authorize the Seqera Co-Scientist GitHub App.
  2. Open the link and approve the authorization on GitHub. The page that opens shows a connection ID.
  3. Copy the connection ID and paste it into the conversation to finish connecting.
  4. If the repository belongs to a GitHub organization where the app is not installed, Co-Scientist returns an install link for the app. Ask an organization admin to install the app and grant it access to the repository, then ask Co-Scientist to retry.

The authorization link and the connection ID expire after a short time. If either expires, ask Co-Scientist to start again.

note

If your GitHub organization enforces SAML single sign-on (SSO), GitHub rejects access until you authorize the connection for that organization. Co-Scientist tells you when this happens. Open the authorization link from GitHub, approve access for the organization, and retry.

Download session files​

Some requests produce files, such as a generated configuration or a converted pipeline. When a session has produced files, use the sandbox chip above the message box to download the session contents as a .tar.gz archive.

Learn more​

  • Co-Scientist: Overview and where Co-Scientist is available
  • Credits: Co-Scientist credits and how to request more
  • Projects: Group workspace resources with Platform labels
  • Troubleshooting: Troubleshoot common errors
On this Page