Editor Integrations¶

Arqon Maestro becomes substantially more capable when it can work through an editor integration instead of only through generic system input.

Video placeholder: editor plugin installation and first coding workflow.

Supported Editor Paths In This Build¶

The current onboarding flow points users toward:

VS Code
Atom
JetBrains

Why Integrations Matter¶

With an integration, Maestro can operate on code structures rather than only sending raw keystrokes or clipboard content.

That improves:

navigation
selector resolution
editing reliability
code generation quality

Without A Plugin¶

If your target app does not have a plugin, Maestro can still operate through:

system text insertion
dictate mode
text input
revision box

That keeps Maestro useful as a general Arqon ecosystem control layer instead of making it editor-only.

Recommended Setup Path¶

install the editor integration
open an empty file
enable listening
run a basic tutorial
test add, go to, change, and undo

Learn By Tutorial¶

The onboarding flow already pushes users toward a language tutorial after setup. That is the correct default because it teaches the grammar interactively instead of through static reading alone.