> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/automations/the-live-editor.md).
# The Live Editor
## What is the Live Editor?
Rewst Classic's *Live Editor* is an interactive environment in the Rewst Classic platform where you can test and debug workflows, Jinja, PowerShell, and variables in real time. Instead of building blindly and hoping it works later, check your code and see if it delivers your desired result.
* Run individual steps or entire branches of a workflow and see how things behave.
* Inspect the actual data moving through a workflow, including step outputs, parsed inputs, and runtime values.
* Test your Jinja expressions directly on real data without deploying the full workflow.
## Use the Live Editor in Rewst
Access the Live Editor by navigating to **Automations > Live Editor** in the left side menu of your Rewst Classic platform.
The **Context** panel in the Live Editor is where you provide mock or sample data that your Jinja template can reference during rendering. Since the Live Editor runs outside of an actual workflow execution, there's no real `CTX`, `TASKS`, or other runtime data available. The Context panel lets you simulate that data so you can test your templates realistically. Variables you define in the Context panel are accessed in your template using the `CTX.` prefix. If you add `"username": "Alice"` in the context, your template should reference it as `{{ CTX.username }}`, not just `{{ username }}`.
Click the **switch** button in the top right of your **Editor** panel to switch between the two available languages in the editor. The name of the language currently in use for the editor will display in blue on the button.
Click **Render** to display your code's result in the **Result** pane.
Click **Share** to create a link to share your context and code in the editor, to be opened by another individual later. This is particularly helpful for sending to coworkers or Rewst support staff.
## Live Editor shortcuts
* Access the Live Editor in other menus in Rewst Classic, in any fields where you see the button.
* Press `F1` within the editor to see menu and shortcut options
* Press `Ctrl + Space` to get the initial root options
* Add `|` to the end of your variables to access [Jinja filters](https://docs.rewst.help/documentation/jinja/list-of-jinja-filters). e.g.: `{{ ORG.ATTRIBUTES.id|default('test default string') }}`
{% hint style="info" %}
For more on how to use Jinja in Rewst, see our [Jinja documentation here](https://docs.rewst.help/documentation/jinja), and sign up for courses in [Cluck University](https://learn.rewst.io/).
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.rewst.help/documentation/automations/the-live-editor.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.
button.
* Press `F1` within the editor to see menu and shortcut options
* Press `Ctrl + Space` to get the initial root options
* Add `|` to the end of your variables to access [Jinja filters](https://docs.rewst.help/documentation/jinja/list-of-jinja-filters). e.g.: `{{ ORG.ATTRIBUTES.id|default('test default string') }}`
{% hint style="info" %}
For more on how to use Jinja in Rewst, see our [Jinja documentation here](https://docs.rewst.help/documentation/jinja), and sign up for courses in [Cluck University](https://learn.rewst.io/).
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.rewst.help/documentation/automations/the-live-editor.md?ask=