This page takes you from zero tooling to the point where you can run any command in the Getting Started guide.
In this document we will walk through:
If you don’t already have a code editor installed, download one of your choice, for example VS Code, Windsurf, or Cursor.
You can also install a more sophisticated terminal like warp which makes development even easier.
Creating a GitHub account will make it easier for you to manage your code projects. We recommend creating an account and installing the GitHub Command Line Interface (CLI) to make GitHub management seamless. Follow the installation instructions for the GitHub CLI based on your machine.
Open your terminal and run the following to install python and verify the version
Most distros already ship a recent python version but if not run
You can either use pip or uv as your Python package manager. Pip is the classic package manager, uv is a newer, faster drop-in replacement for pip. We recommend using uv since it makes package management easier.
Verify the uv installation instructions for your machine on the astral website. You will likely run:
Verify uv is installed correctly:
If you prefer to use pip, it should already be installed with Python. Verify it’s working:
If you have a GitHub account, create a repository and then clone it to your machine:
gh repo clone YOUR_REPO_NAME
If you don’t have a GitHub account, create a new project folder where we’ll run the code samples:
Virtual environments are important because they isolate your project dependencies from your system Python installation. This prevents version conflicts between different projects and keeps your system clean.
In your terminal, inside the project folder, run the following commands to create your virtual environment based on the package manager you are using:
Now activate the virtual environment (you will do this every time you cd into the project folder where you’re running your code)
You’ll know your virtual environment is active when you see .venv
at the beginning of your terminal prompt.
Now that you have your virtual environment setup you can install MeshAgent!
Note: Any shell that does glob-expansion (zsh, fish, PowerShell) treats the square brackets as a wildcard unless they’re quoted or back-escaped, this is why you need to put quotes around the meshagent[all]
install command. Installing meshagent[all]
is beneficial because you will get all of the python libraries associated with MeshAgent. If you are installing individual packages with Python you do not need to run the install command with quotes. For example, if you only wanted to install one of the MeshAgent libraries, like the MeshAgent CLI, you would run the command like this:
Note: Inside an activated virtual-env pip already points to the right interpreter, so pip
or pip3
both work. Outside a venv you may need to run pip3
to avoid Python 2 leftovers.
Congratulations! You now have everything set up to run the examples in the Getting Started guide.
uv run python your_script.py
to automatically use the virtual environment. If your virtual environment is already activated you can also just run python your_script.py
.