> 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/app.md).

# App screens

- [Task list](https://learn.mechanic.dev/app/home.md): The Mechanic task list — view installed tasks, monitor current activity, and see recent Shopify automation events.
- [Activity](https://learn.mechanic.dev/app/activity.md): Review Mechanic activity over time, spot failures, and drill into event details from the Activity page.
- [Task editor](https://learn.mechanic.dev/app/task-editor.md): Create, edit, and test Mechanic tasks — configure options in Basic mode or write Liquid code in Advanced mode.
- [Forms](https://learn.mechanic.dev/app/forms.md): Collect quote requests, wholesale applications, service inquiries, and more with forms connected to your Mechanic tasks.
- [Events](https://learn.mechanic.dev/app/events.md): Monitor Shopify webhook events, filter by topic or error, and investigate task run results in the Mechanic Events page.
- [Settings](https://learn.mechanic.dev/app/settings.md): Configure your Mechanic account — contact email, Shopify permissions, outbound email, webhooks, integrations, and more.
- [Ask Mechanic](https://learn.mechanic.dev/app/ask-mechanic.md): Ask Mechanic is a built-in AI assistant that answers platform questions, explains features, and helps you find tasks — no setup required.
- [Liquid console](https://learn.mechanic.dev/app/liquid-console.md): Test Mechanic Liquid code in a live scratchpad — experiment with filters, inspect event data, and debug task logic without creating a task.
- [Keyboard shortcuts](https://learn.mechanic.dev/app/keyboard-shortcuts.md): Keyboard shortcuts for navigating Mechanic, creating tasks, and toggling Ask Mechanic — with a full shortcut reference.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.mechanic.dev/app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.