> For the complete documentation index, see [llms.txt](https://docs.friggframework.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.friggframework.org/tutorials/quick-start/start-your-frigg-app.md).
# Start Your Frigg App
Ready to see Frigg in action? Let's start it up!
Make sure you're in the root directory of your application, then use:
```
npm run start
```
Your browser should open to `http://localhost:3000` and you should see your Login screen.
Login screen of your Frigg app
Before you continue, make sure that both your frontend and backend are running. An easy way to know is to check if your terminal looks something like this:
The terminal output shows the backend server running locally, with a list of active routes and endpoints available for testing and development
If your terminal shows that the backend is also running, you can now experience with your app as an end-user and connect it to see live data coming through!
---
# 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://docs.friggframework.org/tutorials/quick-start/start-your-frigg-app.md?ask=&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.
