> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/gpcscripting/gpc-script-guide/start-here/use-zen-studio-live-as-a-tight-feedback-loop.md).

# Use Zen Studio Live as a tight feedback loop

For each example:

{% stepper %}
{% step %}
Create or open a `.gpc` file in Zen Studio Live.
{% endstep %}

{% step %}
Paste the complete example, not only the body of `main`.
{% endstep %}

{% step %}
Connect Zen through its PROG USB port, then use **Compiler → Build and Run** or press **F5**. Build and Run compiles the script and sends the temporary test build directly to the connected Zen, so it is faster than repeatedly programming memory slots while developing.
{% endstep %}

{% step %}
If the build fails, read and fix the first compiler message from the top before chasing later messages.
{% endstep %}

{% step %}
Use Device Monitor to verify physical input, outgoing values, traces, controller type, and VM behavior while the test build is running.
{% endstep %}

{% step %}
Test with the intended console and controller; a successful compile proves syntax, not device behavior.
{% endstep %}

{% step %}
Program a memory slot only when you want to keep the tested script on Zen after the development session.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Use a harmless test profile before adding automation to an existing large script. Large scripts can contain later output writers, remaps, menus, or gates that hide otherwise correct code.
{% endhint %}


---

# 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://guide.cronuszen.com/gpcscripting/gpc-script-guide/start-here/use-zen-studio-live-as-a-tight-feedback-loop.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.