Autonomous Scientific Discovery on HPC
A few details for the admin reviewing your request.
Your operational overview
Active background tasks — auto-refreshes every 30s
| Task | Session | Status | Events |
|---|
Browse and open project workspaces
Your identity on Trinity
This information is visible to admins and helps identify you on the platform.
Sign out of Trinity on this device.
Injected as context at the start of every chat. Use this to tell Trinity about your role, preferences, or recurring constraints — like ChatGPT's custom instructions.
Connect the facilities you use — each button grants just that facility's access. You can also pick a facility right at sign-in.
OLCF uses project access tokens that expire and must be renewed manually from myOLCF ↗ → Projects → API Tokens.
Queue, allocation & username are saved per system — switch the Default system to view/edit each. Jobs use the values for whatever system they target.
Token status & OLCF token entry moved to Authentication. These are fallback/debug tools for when the redirect login fails.
Per-user environment variables injected into every Claude session. Use this to set service credentials like ClearML, GitHub, or API keys that override shared server defaults. Values are stored encrypted per-user and never visible to other users.
Click to prefill the key name above.
Download all your conversations. Each session includes messages, timestamps, and token usage.
Trinity is an agentic platform for autonomous scientific computing on DOE leadership systems. Describe your science in plain language and Trinity plans and runs the whole workflow — choosing a facility, staging data, writing and submitting jobs, monitoring them, and returning results — across ALCF (Polaris, Aurora, Crux, Sophia), NERSC (Perlmutter), and OLCF (Frontier). It is built on the Claude Agent SDK and rides Globus for identity, data movement, and compute, so a single conversation can reach every facility you are authorized to use.
Under the hood it composes reusable building blocks — Agents (domain specialists and multi-agent campaigns), Workflows (curated HPC pipelines), and Skills (atomic capabilities) — and records its work as Knowledge, Traces, and Provenance so results stay auditable and reproducible. Trinity is multi-tenant: each user's tokens, sessions, and settings are isolated. Built and maintained at the Argonne Leadership Computing Facility.
Select agents and compose a multi-agent science campaign.
HPC workflow catalog — click Use to start a session with this workflow.
Atomic skills & playbooks — click Use to invoke one in chat (e.g. /submit-job).
Validated scientific K-atoms — confirmed domain facts used by agents during campaigns.
Full audit trail of autonomous campaign decisions — traces, tool calls, alternatives considered.
| Username | Role | Projects | File Write |
|---|
Interactions with other agents across all your sessions.
Connect with people, then start a group chat. Both sides must accept.
API tokens & cost across your sessions.
Trinity systematic test-suite — does it work & what does it cost.
Select a session and click View Trace
Saved as .trinity.md
in the project directory. Trinity injects it into every conversation for this project.
Anyone with this link can view this session (read-only). They don't need a Trinity account.
A driver can send messages into this session; a viewer only watches. ⚠️ Driver actions run under your HPC credentials.