> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/faq/does-my-theme-need-to-be-updated-for-mechanic.md).

# Does my theme need to be updated for Mechanic?

Most Mechanic tasks don't need anything enabled in your theme. Tasks that run JavaScript in your online store do: they use Mechanic's **Online store JavaScript** setting in the theme editor.

If one of your enabled tasks needs this and setup is incomplete, Mechanic shows a **Mechanic in your theme** card on the homepage and the task page. Click **Enable Mechanic in your theme**, make sure **Online store JavaScript** is turned on under **App embeds**, and click **Save** in the theme editor. Then return to Mechanic to confirm setup. [See the setup guide](/core/tasks/advanced-settings/javascript.md#enable-mechanic-in-your-theme).

This is a one-time setup for your current theme and serves all your enabled tasks that use storefront JavaScript. You can leave it enabled when you disable a task; disabled tasks won't run on subsequent page loads. Enabling Mechanic doesn't require editing theme code.

When you publish a different theme, open Mechanic and check whether it asks you to enable Mechanic in that theme. Saving the setting in a draft theme doesn't complete setup for the published theme.

Some tasks also need custom theme changes, such as a button or a form. Follow those tasks' instructions, and check with whoever configured them before switching themes. Enabling Mechanic loads their JavaScript; it doesn't copy custom theme changes into a new theme.

If your tasks already use Mechanic's older JavaScript integration, follow the same theme setup steps. Mechanic handles the change in the background after confirming that you've saved activation in your published theme. You don't need to reinstall your tasks or remove the old integration yourself. [Learn about existing tasks](/core/tasks/advanced-settings/javascript.md#existing-tasks).


---

# 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://learn.mechanic.dev/faq/does-my-theme-need-to-be-updated-for-mechanic.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.