Hyperloom Remote Mn Qwen3 30b logo

Hyperloom Remote Mn Qwen3 30b

Organization
AMD-AGI
hyperloom-remote-mn-qwen3-30b

Run a 4-hour multi-node Hyperloom Qwen3-30B-A3B optimization (Infera PD-disaggregated or RayJob aggregated) with --nodes 2 and sglang MoE tuning on MI325X. Hand this skill to the agent to launch and monitor the run.

Overview

PublisherAMD-AGI
RepositoryHyperloom
Skill namehyperloom-remote-mn-qwen3-30b
Stars
250
Forks
74
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by AMD-AGI on GitHub. Read the source before you install it.

Installation

Install the Hyperloom Remote Mn Qwen3 30b AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/AMD-AGI/Hyperloom/tree/main/docs/how-to/multi-node/hyperloom-remote-mn-qwen3-30b
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/AMD-AGI/Hyperloom.git /tmp/Hyperloom
mkdir -p .claude/skills
cp -r /tmp/Hyperloom/docs/how-to/multi-node/hyperloom-remote-mn-qwen3-30b .claude/skills/hyperloom-remote-mn-qwen3-30b
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hyperloom Remote Mn Qwen3 30b in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Hyperloom Remote Mn Qwen3 30b on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Hyperloom Remote Mn Qwen3 30b is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Hyperloom Remote Multi-Node — Qwen3-30B-A3B

Pinned workload for a remote multi-node optimize run. Pick one backend below and pass its FLAGS + Environment block to inference_optimizer optimize; the agent launches it in the background and monitors state.json until a terminal stop_reason — success (target_reached, global_converged, time_exhausted, max_ticks) or early failure (baseline_failed, baseline_accuracy_failed) that ends the run before optimizing. Concept and variable reference: @../../../reference/multi-node.md. Optimizer skill: @${HYPERLOOM_SKILL_PATH} (fallback @../../../../src/hyperloom/inference_optimizer/SKILL.md).

Prerequisites

  • NFS_SHARED_ROOT: cluster-wide shared mount at the same absolute path on the sandbox and every GPU pod (model, tool checkouts, session artifacts). Required; local-only paths break multi-node restart and benchmarks.
  • A provisioned cluster: the platform creates the GPU pods and hands them over via HYPERLOOM_MN_EXT_* (platform-injected; never passed on the CLI). optimize adopts that cluster and exits 2 without it. See @../../../reference/multi-node.md.

One FLAGS block, two readers

The blocks below are written for Primus-Claw and optimize: Claw parses them to size and build the cluster, then the agent runs optimize with the same block. Four flags configure the cluster Claw provisions and can be dropped when composing the optimize command. optimize accepts them so a real platform prompt parses, but nothing reads them once the cluster exists:

Claw-only flagWhat Claw does with it
--mn-imageContainer image for the GPU pods (infera needs the sshd layer)
--cpus-per-node / --mem-per-nodePer-pod CPU / memory request
--extra-env K=VBaked into pod env at create time (repeatable)

They are listed last in each block so the optimize command is the block with its tail cut off.

Everything else (--nodes, --mn-backend, --gpus-per-node, --model, --framework, --pd-*) is read by both and stays on the optimize command.

Layout under NFS_SHARED_ROOT (replace ${NFS_SHARED_ROOT} with the real mount):

text
${NFS_SHARED_ROOT}/models/Qwen3-30B-A3B/   # --model
${NFS_SHARED_ROOT}/InferenceX/             # INFERENCEX_PATH
${NFS_SHARED_ROOT}/Magpie/                 # MAGPIE_PATH
${NFS_SHARED_ROOT}/TraceLens/              # TRACELENS_ROOT

If your deployment has the TraceLens-internal checkout, set TRACELENS_INTERNAL_ROOT separately. Leave it unset for the public open-source path.


Workload A — Infera + PD disaggregation

--mn-backend infera with --pd-mode disaggregated.

FLAGS

text
--gpu-type mi325x \
--model ${NFS_SHARED_ROOT}/models/Qwen3-30B-A3B \
--target-gain 30 \
--max-hours 4 \
--mn-backend infera \
--framework=sglang \
--nodes 2 \
--gpus-per-node 8 \
--tp 8 --ep 8 \
--isl 1024 --osl 1024 --conc 128 \
--precision bf16 \
--pd-mode disaggregated \
--pd-prefill-nodes 1 --pd-decode-nodes 1 \
--pd-prefill-tp 8 --pd-decode-tp 8 \
--pd-prefill-ep 8 --pd-decode-ep 8 \
--pd-transfer-backend mooncake \
--pd-ib-device rdma0,rdma1,rdma2,rdma3,rdma4,rdma5,rdma6,rdma7 \
--pd-prefill-extra-args "--attention-backend aiter --mem-fraction-static 0.78 --disable-radix-cache --load-balance-method round_robin --watchdog-timeout 3600 --enable-dp-attention --moe-dense-tp-size 1 --enable-dp-lm-head --chunked-prefill-size 8192" \
--pd-decode-extra-args "--attention-backend aiter --mem-fraction-static 0.82 --enable-dp-attention --load-balance-method round_robin --watchdog-timeout 3600 --moe-dense-tp-size 1 --enable-dp-lm-head --chunked-prefill-size 8192 --max-running-requests 1024" \
--mn-image <INFERA_SSHD_IMAGE> \
--cpus-per-node 90 \
--mem-per-node 1024 \
--extra-env MC_GID_INDEX=3 \
--extra-env NCCL_IB_GID_INDEX=3 \
--extra-env SGLANG_USE_AITER_AR=0

Environment

text
RANDOM_RANGE_RATIO=0.8
SGLANG_DISAGGREGATION_BOOTSTRAP_TIMEOUT=1200
SGLANG_DISAGGREGATION_WAITING_TIMEOUT=1200
INFERENCEX_PATH=${NFS_SHARED_ROOT}/InferenceX
TRACELENS_ROOT=${NFS_SHARED_ROOT}/TraceLens
MAGPIE_PATH=${NFS_SHARED_ROOT}/Magpie

Large-model MoE cold start may need a longer poll budget: export HYPERLOOM_MN_POLL_TIMEOUT_S=1800 HYPERLOOM_MN_HEALTH_WAIT_S=1800.


Workload B — RayJob aggregated

--mn-backend rayjob (no PD flags). Same model / Environment as Workload A; the differences are:

  • Drop all --pd-* flags.
  • Replace --pd-*-extra-args with a single --server-args (applied each restart).
  • --mn-image is a standard Ray image (no sshd layer needed).
  • Drop the SGLANG_DISAGGREGATION_* env vars (PD-only).
  • --tp covers the whole cluster, not one node. One server spans every pod here, so --tp must be nodes * gpus-per-node (16) — sglang receives --tp <n> --nnodes 2 and splits the ranks, so --tp 8 would leave half of each pod's GPUs idle. Workload A differs because each PD role owns one node, where --pd-*-tp 8 fills all 8 of its GPUs.
  • Pod-side env reaches the GPU pods only through --extra-env, which Claw bakes in at create time (Claw-only, see the table above — drop it from the optimize command). Cross-node tensor parallel needs the RoCE GID there. The Environment block below is sandbox-side only and never reaches the pods.

FLAGS

text
--model ${NFS_SHARED_ROOT}/models/Qwen3-30B-A3B \
--target-gain 30 \
--max-hours 4 \
--mn-backend rayjob \
--framework=sglang \
--nodes 2 \
--gpus-per-node 8 \
--tp 16 --ep 16 \
--isl 1024 --osl 1024 --conc 128 \
--gpu-type mi325x \
--precision bf16 \
--server-args "--attention-backend aiter --mem-fraction-static 0.8 --enable-dp-attention --deepep-mode normal --ep-dispatch-algorithm fake --load-balance-method round_robin --watchdog-timeout 3600 --moe-dense-tp-size 1 --enable-dp-lm-head --chunked-prefill-size 8192 --max-running-requests 1024" \
--mn-image <RAYJOB_IMAGE> \
--cpus-per-node 90 \
--mem-per-node 1024 \
--extra-env NCCL_IB_GID_INDEX=3

Optional model pins (omit to use the deployment defaults): --claude-model <model> / --codex-model <model>.

Environment

text
RANDOM_RANGE_RATIO=0.8
INFERENCEX_PATH=${NFS_SHARED_ROOT}/InferenceX
TRACELENS_ROOT=${NFS_SHARED_ROOT}/TraceLens
MAGPIE_PATH=${NFS_SHARED_ROOT}/Magpie

The Kernel-Forge kernel backend needs no checkout and no path variable: KernelForge ships inside Hyperloom. Select it with KERNEL_OPT_BACKEND_ORDER=forge (Workload B only). Behind a TLS-terminating proxy add NODE_TLS_REJECT_UNAUTHORIZED=0 and ANTHROPIC_SKIP_TLS_VERIFY=true.


Run notes

  • Session lands in $USER_DATA_PATH/<model_basename>/<UTC_ts>/; USER_DATA_PATH is platform-injected and kept unchanged.
  • Crash recovery: optimize --resume-from "$SESSION_DIR" on the same session dir (never a second optimize; resume past a terminal stop_reason needs --force-resume).
  • Releasing the cluster is the platform's job, not the optimizer's — it happens when the session ends.

Frequently asked questions

What does the Hyperloom Remote Mn Qwen3 30b AI skill do?

Run a 4-hour multi-node Hyperloom Qwen3-30B-A3B optimization (Infera PD-disaggregated or RayJob aggregated) with --nodes 2 and sglang MoE tuning on MI325X. Hand this skill to the agent to launch and monitor the run.

Why use Hyperloom Remote Mn Qwen3 30b on TypingMind?

Because you install it once and use it with any model. Hyperloom Remote Mn Qwen3 30b is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Hyperloom Remote Mn Qwen3 30b in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AMD-AGI/Hyperloom/tree/main/docs/how-to/multi-node/hyperloom-remote-mn-qwen3-30b. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Hyperloom Remote Mn Qwen3 30b?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Hyperloom Remote Mn Qwen3 30b?

As many as you like. As long as a model supports skills, you can use Hyperloom Remote Mn Qwen3 30b with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hyperloom Remote Mn Qwen3 30b AI skill free?

It is published on GitHub by AMD-AGI. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇