{"slug": "amd-hpc-assistant-open-source-ai-agent-for-supercomputers", "title": "AMD HPC Assistant: Open-Source AI Agent for Supercomputers", "summary": "AMD released HPC Assistant, an open-source AI coding agent for supercomputers, on November 17 at SC26 in Chicago, running live on Finland's LUMI supercomputer and deploying to Oak Ridge National Laboratory's Frontier exascale machine. The MIT-licensed tool, hosted at silogen/hpc-assistant on GitHub, lets researchers submit Slurm jobs, profile AMD GPUs with rocprofv3, track per-job energy use, and query cluster-specific documentation in plain English, running the LLM locally and SSHing into the cluster for execution. Pekka Manninen, Director of Science and Technology at CSC – IT Center for Science, said the assistant \"understands the full researcher workflow, from job submission to GPU profiling, energy visibility and launching scientific models without manual environment setup.", "body_md": "AMD shipped an open-source AI coding agent for supercomputers on November 17 at SC26 in Chicago. Called HPC Assistant, it runs live on LUMI — Finland’s flagship supercomputer — and is deploying to Frontier, the world’s first exascale machine at Oak Ridge National Laboratory. Researchers can now submit Slurm jobs, profile AMD GPUs, and query cluster documentation in plain English. The sysadmin ticket queue gets shorter.\n\n## HPC Is Hard. That’s the Problem This Solves.\n\nUsing a modern supercomputer is not like using a cloud VM. You’re writing [Slurm](https://slurm.schedmd.com/documentation.html) job scripts with the right partition names, memory limits, and GPU counts. You’re managing module environments where conflicting library versions silently break your code. You’re reading system-specific documentation that’s often 200+ pages long and updated quarterly. Researchers without a CS background — the majority of HPC users — routinely spend weeks on this overhead before writing a single line of science code.\n\nHPC Assistant’s bet is that an AI agent with access to cluster-specific documentation can absorb that operational burden. Not by giving you better docs to read, but by handling the operations directly.\n\n## What It Does (Specifically)\n\nThe tool ships as a set of site-specific skills covering the most time-consuming parts of cluster work:\n\n- **Slurm job management** — Submit, monitor, and cancel jobs via`sbatch` ,`srun` ,`squeue` , and`scancel` commands, issued in natural language\n- **AMD GPU profiling** — HIP/ROCm application profiling with`rocprofv3` : kernel tracing, performance counters, cache efficiency metrics\n- **Energy monitoring** — Per-job energy consumption tracking via Omnistat and Grafana dashboards\n- **RAG-powered documentation** — Retrieves answers from LUMI’s or Frontier’s actual documentation: storage policies, project quotas, partition requirements — your cluster’s answers, not generic ones\n- **Scientific agent launching** — Spin up domain agents like OpenFold3 for protein structure prediction without manually configuring environments\n\n“The HPC Assistant brings something genuinely new to LUMI. It understands the full researcher workflow, from job submission to GPU profiling, energy visibility and launching scientific models without manual environment setup.”\n\nPekka Manninen, Director of Science and Technology, CSC – IT Center for Science\n\n## How It Works\n\nThe architecture explains why this works at all. HPC clusters don’t allow you to run large language models on login nodes — resource limits prevent it. So AMD HPC Assistant uses a local execution model: you run the agent on your own machine, and it SSHes into the cluster to execute operations. The LLM runs locally (or via API); the cluster work happens remotely.\n\nUnder the hood, the stack has four layers: markdown skill files with YAML frontmatter define what operations the agent can run; MCP servers expose the RAG knowledge base and cluster tools; a LiteLLM proxy translates between Anthropic and OpenAI-compatible backends; and Singularity/Apptainer containers handle cluster-side execution without system-wide installs.\n\nIt supports Claude Code and OpenCode as agent frameworks. For backends, you can use an Aitta token (LUMI-native), an Anthropic API key, or any OpenAI-compatible endpoint.\n\n## Open Source, Self-Hostable\n\nThe repo is [silogen/hpc-assistant](https://github.com/silogen/hpc-assistant) on GitHub, MIT licensed for AMD-authored components. Any HPC center can deploy their own instance and load it with their own site-specific knowledge base and skills. That’s the key differentiator from asking ChatGPT about Slurm: HPC Assistant’s answers are grounded in your cluster’s actual configuration, not generic Linux documentation.\n\nFrontier support is in progress. Dr. Antigoni Georgiadou from Oak Ridge National Laboratory confirmed AMD is working to bring HPC Assistant to Frontier, though no rollout date has been announced.\n\n## AMD’s Broader SC26 Bet\n\nHPC Assistant sits inside a larger AMD push at SC26. The company announced the [MI430X GPU](https://newsroom.amd.com/news/amd-advances-instinct-mi400-series-ai-scientific-computing/) — its first chip specifically designed for the convergence of high-precision FP64 simulation and AI, with 432 GB of HBM4. The new Lux supercomputer (No. 14 on TOP500) built by HPE with MI355X GPUs delivers 220.79 petaflops and is designated as the first U.S. AI Factory for the Department of Energy’s Genesis Mission. AMD now powers 202 of the 500 fastest supercomputers — over 40% of the list.\n\nThe pattern is deliberate: build the hardware, build open-source software tools, get centers to adopt them, sell more hardware. HPC Assistant is as much a go-to-market play as it is a developer tool — which is not a critique, just context for evaluating AMD’s long-term commitment to maintaining it.\n\n## Getting Started\n\nIf you’re on LUMI today, HPC Assistant is live. For other clusters, the [GitHub repo](https://github.com/silogen/hpc-assistant) covers local mode setup: configure SSH multiplexing, run `hpc-assistant-local-setup` with your remote host credentials, and launch your agent framework. The skill files are readable markdown — adding site-specific knowledge for a new cluster is a documentation exercise, not an engineering project.\n\nThe full [AMD SC26 announcement](https://www.amd.com/en/blogs/2026/amd-brings-agentic-ai-to-supercomputing-with-open-source-amd-hpc.html) and [LUMI’s SC26 highlights](https://lumi-supercomputer.eu/sc26-highlights/) have additional context on the broader deployment.\n\nAI agents have been colonizing the developer stack from the top down: code editors, then cloud infrastructure, now HPC clusters. If you run workloads on supercomputers, this is worth fifteen minutes of your time.", "url": "https://wpnews.pro/news/amd-hpc-assistant-open-source-ai-agent-for-supercomputers", "canonical_source": "https://byteiota.com/amd-hpc-assistant-open-source-supercomputer/", "published_at": "2026-11-18 02:09:35+00:00", "updated_at": "2026-11-18 02:11:34.829840+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-agents", "ai-tools", "developer-tools", "ai-infrastructure"], "entities": ["AMD", "HPC Assistant", "LUMI", "Frontier", "Oak Ridge National Laboratory", "Pekka Manninen", "CSC – IT Center for Science", "Antigoni Georgiadou"], "also_reported_by": [], "takeaway": "HPC Assistant runs the LLM on the researcher's local machine and SSHes into the cluster to execute Slurm, rocprofv3 and container operations, using markdown skill files with YAML frontmatter, MCP servers for RAG and cluster tools, and a LiteLLM proxy that supports Claude Code and OpenCode with Aitta", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/amd-hpc-assistant-open-source-ai-agent-for-supercomputers", "markdown": "https://wpnews.pro/news/amd-hpc-assistant-open-source-ai-agent-for-supercomputers.md", "text": "https://wpnews.pro/news/amd-hpc-assistant-open-source-ai-agent-for-supercomputers.txt", "jsonld": "https://wpnews.pro/news/amd-hpc-assistant-open-source-ai-agent-for-supercomputers.jsonld"}}