Is this page helpful?

Extension Template Generator to CLI Templates#

Isaac Sim 6.0 deprecates the UI-based Extension Template Generator extension (isaacsim.examples.extension). Use the command-line interface (CLI) repo template system instead:

./repo.sh template new

On Windows, use .\repo.bat template new.

Migration Approach#

Follow these steps to replace the deprecated generator:

  1. Generate a new extension with ./repo.sh template new from the repository root.

  2. Choose the template that matches the old generated extension’s intent.

  3. Move project logic into the generated files instead of keeping a dependency on isaacsim.examples.extension.

  4. Remove imports from isaacsim.examples.extension and update extension dependencies.

  5. Build the repo and run the generated extension test before deleting the old generated scaffold.

Concept Mapping#

Deprecated generator workflow

CLI template workflow

Loaded Scenario Template

Use the UI extension template. Move scene setup to scenario.py and custom controls to ui.py.

Scripting Template

Use the UI extension template and keep script-like actions behind explicit UI callbacks.

Configuration Tooling Template

Use the UI extension template for Python UI tooling, or the OmniGraph extension template when the tool needs custom nodes.

UI Component Library Template

Use the generated ui.py and the current UI wrapper utilities as reference code.

Direct TemplateGenerator API usage

No direct replacement. Record template answers with ./repo.sh template new --generate-playback answers.toml and replay them with ./repo.sh template replay answers.toml for automation.

Dependency Changes#

Remove deprecated dependencies such as:

"isaacsim.examples.extension" = {}

Generated extensions go into source/extensions/, where the build system discovers them automatically. Do not add an app dependency on the generator extension.

Validation Checklist#

Verify the following before removing the old scaffold:

  • ./repo.sh template new generates the selected template without manually editing generated paths.

  • The generated extension builds with ./build.sh.

  • The generated startup test under the build output passes.

  • The extension can be enabled without isaacsim.examples.extension.

  • UI workflows still load, reset, and stop cleanly after simulation playback.