> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/developer-guides/error-messages/0151-to-0179/aur0101.md).

# AUR0101

## Error Message

`AUR0101: Ast eval error: binding behavior "{{name}}" could not be found. Did you forget to register it as a dependency?`

## Description

This error occurs during binding expression evaluation when a binding behavior (used via `& someBehavior`) cannot be found in the current registration scope.

## Solution

* Ensure the binding behavior is registered (globally via `Aurelia.register(...)` or locally via a component’s `dependencies`).
* Check for typos in the behavior name used in the template.

## More Information

This code is also documented under the runtime-html section: [AUR0101](/developer-guides/error-messages/runtime-html/aur0101.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aurelia.io/developer-guides/error-messages/0151-to-0179/aur0101.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.