miniblog.

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.

Shower thought: using a tool like cargo-semver, could you build a package registry where the uploader never chooses the version number? E.g. your last release was 5.2025-09-13 and you've just changed a type, so today's release is 6.2025-11-05.

One nice feature of cargo that I wasn't previously aware of: you don't need to do anything after updating your Cargo.toml. In npm, you need to remember to `npm i` after changing package.json. It's not declarative and the state can get out of sync.