> For the complete documentation index, see [llms.txt](https://chaoses-ib.gitbook.io/directory-opus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chaoses-ib.gitbook.io/directory-opus/manual/scripting/script_editor/editors.md).

# Editors

The main editor panel is a tabbed window which displays editors for the various script assets.

* [Code Editor](/directory-opus/manual/scripting/script_editor/editors/code_editor.md): Edit script code, with syntax highlighting for VBScript and JScript. You can also configure an external editor for editing script code.
* [Dialog Editor](/directory-opus/manual/scripting/script_editor/editors/dialog_editor.md): Edit script dialogs with a full WYSIWYG editor.
* [String Editor](/directory-opus/manual/scripting/script_editor/editors/string_editor.md): Edit string translations, which let your script support multiple languages.

The editor panel can also display previews of icons and images.

To edit (or view) a script asset, simply double-click it in the asset panel, or use the **Open** command in the *Assets* menu (or right-click context menu). A new tab will open in the editor panel for each asset. If an asset has been modified since the script was last saved, the tab indicates this with a red dot: ![](https://3597805814-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3XSZSwWow0fDf6fQJobd%2Fuploads%2Fgit-blob-a885bb2255d0b5b6df2dbfd571d6af64cfbeea92%2Fscripteditor_tab.png?alt=media)

The corresponding tab in the asset panel also uses a red dot to indicate that something within it has changed. You can close the tab for the modified asset without losing your changes - Opus will alert you if you try to close the whole editor while changes are unsaved.


---

# 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://chaoses-ib.gitbook.io/directory-opus/manual/scripting/script_editor/editors.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.