Edit code and add custom nodes

The explorer on the left lists the workspace folders: the catalogue, your custom nodes, your sessions. A click on a Python file opens it in the editor with line numbers and syntax colouring. The assistant on the right reads the file that is open; its answers quote the lines they rest on.

When the assistant proposes a change to the open file, the disk is left as it was. The editor shows the proposal as a diff over the current text: removed lines in red, added lines in green, with the count of additions and deletions in the bar above. Accept writes the file; Reject restores the text as it was. The keyboard does both: Alt+Enter accepts, Alt+Backspace rejects.

Ask for a node and the assistant writes a Python file under custom_nodes. The file follows the node contract: a signal function that returns the position series, parameters declared at the top. Once saved, the node appears in the Add node menu of the composer under Custom, with the parameters it declared, and it runs through the same engine and the same gates as the shipped kernels.

The explorer keeps the workspace files at hand: a click reopens a node, a saved session or a data file in the editor. The tab bar holds the open files; the size beside each name is the size on disk.