miniblog.

@tristanC That's an option! There's often cases where you know what the user wanted though, so you can provide a sensible AST that the toolchain can handle. For example, a malformed string literal can still be parsed a string so type checking etc can be helpful.

Has anyone built a great solution to 'run all my unit tests automatically'? It's straightforward to write a while loop in bash, but handling timeouts, syntax errors etc well is hard. Running on save would be good, although I wonder if you could run fast tests on each keystroke.

One subtle behaviour of Claude that wasn't obvious to me: whilst each conversation is transient, permissions persist across conversations. So if you've given permission to run e.g. 'cargo test' or even 'cargo run', you need to be sure that all future invocations are safe too. You can see the current permissions with /permissions.