tom

- user’s choice between alarm fatigue (pre-tool call checks) or getting tool calls spammed - no formal control over which tool to use, nor when - no differentiation between (non)destructive tools - no concept of resource-intensive tools - no onus on clients to show audit data on how tools were used

"How do we handle auth b/w frontend and backend?" "What's Dave working on?" "How has the payments service changed in the last week?" These are just some of the questions you can have answered without needing to switch contexts. aren't you lucky

just because my DMs have been filled with people asking to see more of lovely mug (this really happened, promise), here's an explainer on how you can use Rover to really understand your code 👇 www.youtube.com/watch?v=J1Rb...