What is the implications / meaning of that? If a software comes from a trusted source and there's adequate mechanisms to make sure file contents aren't stolen / accessed -- why be concerned with who else has the same software?

Anecdotal solely to me, very unnerving and even with formatting marks enabled makes me feel uneasy seeing a space without a space formatting mark.

I had several roommates, and we each were responsible for a utility. I was responsible for internet, and Cox was our provider.

I received multiple e-mails from Cox about copyright infringement. I can't recall them, but I remember it being serious enough for me to tell people to stop.

Thinking back, I feel like Cox's position is right and fair; let users know they're being observed by copyright holders, and inform the user that they could be compelled to provide their identity to complainants.

But ultimately, the responsibility to "stop" the supposed infringement is on the holder, not Cox.

The agent made a mistake that plenty of humans have made. A separate staging environment on real infrastructure goes a long way. Test and document your command sequence / rollout plan there before running it against production. Especially for any project with meaningful data or users.

What I like is that the sessions are highly configurable from their plan.md which translates a md document into a process. So you can tweak and add steps. This is similar to some of the other workflow tools I've seen around hooks and such -- but presented in a way that is easy for me to use. I also like that it can update the plan.md as it goes to dynamically add steps and even add "hooks" as needed based on the problem.