Seqera
for LuumenAI
Read pipeline runs and compute environments, build Wave containers on approval
Connect Seqera and the agent can answer questions about your Nextflow work without you opening the console: which workflows ran, which compute environments they targeted, what a Wave build did and why it failed. When a run needs a new container image, the agent drafts the Wave build request and holds it for your approval before submitting. Luumen authenticates with an API key.
The Seqera toolbox
14 tools: 13 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Organization DetailsRetrieve detailed information about a specific organization.
- ReadGet Service InfoRetrieve information about the Seqera API service.
- ReadGet User InfoRetrieve information about the authenticated user.
- ReadGet Wave Build LogsGet logs for a container build by build ID.
- ReadGet Wave Build StatusRetrieve the status of a Wave container build by build ID.
- ReadInspect Wave ContainerInspect container image metadata via Wave.
- ReadList Action Event TypesList supported action event types.
- ReadList Compute EnvironmentsRetrieve a list of compute environments.
- ReadList OrganizationsList all organizations.
- ReadList PipelinesList all pipelines accessible to the authenticated user.
- ReadList WorkflowsList workflows.
- ReadValidate Action NameValidate action name.
- ReadValidate Pipeline NameValidate a pipeline name.
- WriteCreate Wave ContainerSubmit a request to Wave for accessing a private container registry or building a container image on-the-fly. Approval by default
One prompt, start to finish
What a governed Seqera run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create wave container — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Seqera — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Seqera to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.