What language is the code?

GDScript, which is Godot's own language. That is what Director 1 writes and what your project is in.

Do I need to install Godot to edit it?

Only to edit outside the app. Godot ships inside Stage Engine for building and playing. To open the project in the normal Godot editor you would download Godot, which is free and open source.

Will Director 1 overwrite my hand edits?

Nothing locks a file or merges two versions. Director 1 works on the project as it finds it, so keep the folder in version control if you are editing the same files by hand.

Can I use C# instead?

Director 1 writes GDScript, and GDScript is the language your project is in.

Is there a Stage Engine plugin for the Godot editor?

No. It is a standalone desktop app for Mac and Windows that bundles its own copy of Godot.

Can I put the project in version control?

It is a directory of ordinary files on your own disk, so nothing prevents it, and it is a good idea if you intend to edit by hand.

Can I edit the code myself?

Yes. Stage Engine writes GDScript into an ordinary Godot project in a folder on your own disk, so you can open it in Godot, read it and change it. The honest caveat is that the app expects to be where you work, not one half of a round trip between two editors.

Yes, and here is exactly what you would be editing

A Godot project. A directory of ordinary files on your machine: scenes, resources and GDScript files. There is no proprietary container, no export step to get at it, and no database that only we can read.

Godot is open source and free to download, so the software that opens your project costs nothing and does not come from us. Stage Engine bundles its own copy of Godot so you can build and play without installing anything, but that is a convenience rather than a lock. Nothing about the project depends on the bundle.

So the answer is yes, with no asterisk on the ownership. The asterisk is on the workflow, and it is a few paragraphs down.

What you can do with the files without asking anyone

Read them. Edit them. Put the folder in version control. Copy it to another machine. Back it up the way you back up anything else. Hand it to a friend who programs and have them open it in Godot and work the way they normally would.

None of that is a feature somebody built for you. It is a consequence of the project being stored in a format that somebody else already documented, and it is most of the reason that format was chosen.

It also means the game does not depend on us continuing to exist. What you built runs locally on Godot, and it is ordinary Godot code rather than something that checks in with a server before it starts.

The caveat: this is not designed as a round trip

The working assumption of the app is that you build in Stage Engine. You can open the project in Godot and change it, because the files are exactly what they look like. What does not exist is machinery that reconciles two editors, and we are not going to imply that it does.

Concretely: nothing locks a file, nothing merges two versions of a scene, and nothing warns you that Director 1 is about to write into a script you rewrote by hand last night. If you edit something yourself and then ask for a change to the same behaviour, Director 1 works on the file as it finds it. That usually goes fine and sometimes does not.

The way to be safe is the ordinary one: keep the project in version control so you can see what changed and put it back if you do not like it. And if a file matters to you, own it completely rather than sharing it.

Working with somebody who codes

Plenty of people building here have a programmer nearby: a friend, a contractor for the last ten percent, an artist with a technical streak. The arrangement that works is a clean division of ownership. They take the systems and work in Godot, you carry on in Stage Engine building the world and asking for behaviour, and you agree up front which files are whose.

The version that goes badly is a programmer called in occasionally to fix things, because each visit starts with rereading whatever changed since the last one. Ownership is cheaper than archaeology.

The project format does not fight this arrangement. It also does not manage it for you, which is the same point as the section above in a different costume.

If you would rather your own AI did the editing

Stage Engine can be driven by an agent you already use, over MCP, running on your own machine with your own model and your own credentials. That sits on the paid plans, Indie at $10 a month or Pro at $50, and Director 1 stays available whether or not you use it.

It is not a bespoke integration with any particular product. Any client that speaks the protocol should be able to connect, and how pleasant it is depends on the client, because they differ in how they handle tool discovery, errors and long-running calls.

It does not make anything offline. Asset generation and world data still come over the network no matter where your model runs.

What this is not, in case that was the question

Stage Engine is not a plugin for the Godot editor. It does not install into a copy of Godot you already have, it does not appear in your keybindings, and it does not offer completions while you type. It is a separate desktop app for Mac and Windows with its own builder and its own bundled Godot.

There is also no command line tool to install. The app is the interface.

If what you wanted was an AI coding assistant inside the Godot editor, that is a reasonable thing to want and this is not it. Knowing that before the download is worth more than finding out after.

Questions

What language is the code?: GDScript, which is Godot's own language. That is what Director 1 writes and what your project is in.
Do I need to install Godot to edit it?: Only to edit outside the app. Godot ships inside Stage Engine for building and playing. To open the project in the normal Godot editor you would download Godot, which is free and open source.
Will Director 1 overwrite my hand edits?: Nothing locks a file or merges two versions. Director 1 works on the project as it finds it, so keep the folder in version control if you are editing the same files by hand.
Can I use C# instead?: Director 1 writes GDScript, and GDScript is the language your project is in.
Is there a Stage Engine plugin for the Godot editor?: No. It is a standalone desktop app for Mac and Windows that bundles its own copy of Godot.
Can I put the project in version control?: It is a directory of ordinary files on your own disk, so nothing prevents it, and it is a good idea if you intend to edit by hand.