[supermdguy]

Overall, I'm really impressed by what you accomplished! I'm not a researcher, so not sure if this is that helpful, but here are some thoughts:

- I wonder if the "move" action is difficult for the model to learn to use well. The model sees token location as positional encodings in the embedding, not sparse character offsets. Would be interesting to see something more like "jump to next/previous [token or set of tokens]". Or maybe a find/replace like most coding harness edit tools use?

- I'd move the exact training data generation details to an appendix. Could be summarized to improve the flow of the paper.

[param-updater]

Hi, thank you for your advice, I really appreciate it!

My model has been able to move pretty naturally throughout the canvas when editing, the model is able to remember the actual canvas including order of the tokens well, but I understand where you're coming from.

Jump to next/previous token is a good idea, and in the future I can definitely look into implementing it, especially for scaling the model up. Same thing with find/replace. Thanks again.