godot-remote-executor

To execute GDScript remotely, connect to the Hastur broker-server using a Bearer token and base URL, then issue an execute request targeting the editor or game executor via executor_id, project_name, or project_path.

Yes, remote GDScript execution allows you to inspect the scene tree, query runtime state like FPS and input variables, create or modify nodes, and perform editor operations directly on a running Godot instance.

You need a running Hastur broker-server instance, a valid Bearer token for authentication, and the base URL to establish the connection for targeting Godot editor or game executors.

Yes, the system supports two executor types: editor and game. You can run code to automate editor tasks or query live game runtime state, using either snippet mode or full class mode execution with structured outputs.

You can target a specific Godot project by providing the executor_id, project_name, or project_path in your execute request sent through the Hastur broker-server.

Remote GDScript execution depends on the Hastur broker-server connection and proper authentication. While it enables live scene manipulation and runtime inspection, network connectivity and valid targeting parameters are required for successful operations.