1. Ah, this commit message feature isn't available in JetBrains yet, unfortunately. Most things carry over since they both use the same underlying code, but thi

1. Ah, this commit message feature isn't available in JetBrains yet, unfortunately. Most things carry over since they both use the same underlying code, but this is more editor-specific. 2. Your "reasonable near-term goal" is right in line with what we are thinking. Basically, "auto-edits" is f(edit that meets deterministic trigger criteria) --> multi-file diff. Here are some examples we have in mind; any others you had in mind? update a type signature --> ripple that change across to all call sites/value literals (kinda like symbolic rename does today, but for more than just the name) rename something --> update the docs change code with a comment nearby --> update the comment if it's now invalid update a func impl --> propose a new test case