black-forest-labs/flux-action

Python

95

1 commits

updated Sep 23, 2026

See the code

README

FLUX 3 Action

FLUX 3 Action: robot manipulation, driving and game clips

Standalone full fine-tuning and action prediction for FLUX 3 Action. The package includes data preparation, distributed training, checkpoint/resume, export and inference. SO-101 task LoRA uses the linked LeRobot integration.

transformer.py, transformer_inf_bf16.py and transformer_inf_fp8r.py keep training and inference implementations separate so readers, especially coding agents, can follow each path directly without tracing inheritance or configuration branches.

The FLUX 3 Action collection contains separate DROID and SO-101 policy repositories. Their frozen encoders are shared through the base repository.

DROID offers BF16 and FP8r packages for base, guidance-distilled and single-step inference.

RecipeBF16 subfolderFP8r subfolder
Base: 4 steps with guidanceroot (omit subfolder)variants/fp8r
Guidance-distilled: 4 stepsvariants/gdvariants/gd-fp8r
Step-distilled: 1 stepvariants/sdvariants/sd-fp8r

Standalone FLUX Action supports all six packages. BF16 packages also include LeRobot configs; native FP8r packages require FLUX Action. LeRobot reads config.json; FLUX Action reads config.native.json when present, otherwise config.json. See checkpoint selection for commands.

Get started

GuideWhat you’ll do
Setup & inferenceInstall dependencies, download weights and predict actions with DROID or SO-101
DROID full fine-tuningPrepare DROID data, run the reproduction recipe, resume and export
SO-101 LoRAAdapt the prepared SO-101 checkpoint to your task with LeRobot
Custom tasks and embodimentsDefine your own observations and actions, using games as a worked example

black-forest-labs/flux-action

Python

95

1 commits

updated Sep 23, 2026

See the code

README

FLUX 3 Action

FLUX 3 Action: robot manipulation, driving and game clips

Standalone full fine-tuning and action prediction for FLUX 3 Action. The package includes data preparation, distributed training, checkpoint/resume, export and inference. SO-101 task LoRA uses the linked LeRobot integration.

transformer.py, transformer_inf_bf16.py and transformer_inf_fp8r.py keep training and inference implementations separate so readers, especially coding agents, can follow each path directly without tracing inheritance or configuration branches.

The FLUX 3 Action collection contains separate DROID and SO-101 policy repositories. Their frozen encoders are shared through the base repository.

DROID offers BF16 and FP8r packages for base, guidance-distilled and single-step inference.

RecipeBF16 subfolderFP8r subfolder
Base: 4 steps with guidanceroot (omit subfolder)variants/fp8r
Guidance-distilled: 4 stepsvariants/gdvariants/gd-fp8r
Step-distilled: 1 stepvariants/sdvariants/sd-fp8r

Standalone FLUX Action supports all six packages. BF16 packages also include LeRobot configs; native FP8r packages require FLUX Action. LeRobot reads config.json; FLUX Action reads config.native.json when present, otherwise config.json. See checkpoint selection for commands.

Get started

GuideWhat you’ll do
Setup & inferenceInstall dependencies, download weights and predict actions with DROID or SO-101
DROID full fine-tuningPrepare DROID data, run the reproduction recipe, resume and export
SO-101 LoRAAdapt the prepared SO-101 checkpoint to your task with LeRobot
Custom tasks and embodimentsDefine your own observations and actions, using games as a worked example

Languages

Python

100.0%