A BAML project has the following structure:

.
├── baml_client/ # Generated code
├── baml_src/ # Prompts live here
│   ├── __tests__/ # Tests loaded by playground
│   │   ├── YourAIFunction/
│   │   │   ├── test_name_monkey.json
│   │   │   └── test_name_cricket.json
│   │   └── YourAIFunction2/
│   │       └── test_name_jellyfish.json
│   ├── main.baml
│   ├── any_directory/
│   │   ├── bar.baml
│   │   └── baz.baml
│   └── foo.baml
# The rest of your project (not generated nor used by BAML)
├── app/
│  ├── __init__.py
│  └── main.py
├── pyproject.toml
└── poetry.lock

  1. baml_src/ is the directory where you write your BAML files with the AI function declarations, prompts, retry policies, etc. It also contains generator blocks which configure how and where to transpile your BAML code.

  2. baml_client/ is the directory where BAML will generate code, and where you’ll import the generated code from.

from baml_client import baml as b

await b.YourAIFunction()
  1. baml_src/__tests__/ are where your unit tests live. The .json files store the test inputs that can be loaded, deleted, created, and ran using the BAML VSCode extension. You can also write programmatic python/TS tests anywhere you like. See here for more information.

You should never edit any files inside baml_client directory as the whole directory gets regenerated on every baml build (auto runs on save if using the VSCode extension).

If you ever run into any issues with the generated code (like merge conflicts), you can always delete the baml_client directory and it will get regenerated automatically once you fix any other conflicts in your .baml files.

​
imports

BAML by default has global imports. Every entity declared in any .baml file is available to all other .baml files under the same baml_src directory. You can have multiple baml_src directories, but no promises on how the VSCode extension will behave (yet).

generator