I built Doozy becasue support at my company (Spur) is understaffed and kept on waiting on engineering to run a query for customer or wanted to verify something if it was a bug. The first version was a slack bot with read access to our postgres and stripe, but it was very hacky. It could barely read files sent in a thread, but agent was smart enough to find them through slack search and finish the task anyway. It got used far more by support and success than by engineers, which surprised me. 13 people at Spur use it every single day and is basically a critical part of the team today.
Doozy is the rebuilt, multi-tenant version. You mention it in a thread with task, it runs the task connected to your systems, in it's own isolated environment and posts the result and files in the thread.
2 comments
[ 4.5 ms ] story [ 18.2 ms ] threadDoozy is the rebuilt, multi-tenant version. You mention it in a thread with task, it runs the task connected to your systems, in it's own isolated environment and posts the result and files in the thread.