I'm currently working on a personal project that needed a way to instantly capture UI context from a user and hand it off to an AI layer. Basically, letting the user show what they're seeing instead of typing it out.
My first instinct was to just build this internally and move on. But the more I built it, the more I realized it wasn't really tied to that project at all, instead, it was a generic problem: "let a user snip part of the screen and pass it somewhere useful," which is something a lot of people building AI-powered tools probably need. So instead of keeping it in one codebase, I pulled it out and published it to npm. That way it can actually grow, get used in things I'm not even thinking about, and hopefully be useful to other people.
That's how truden came to be.
Problems I think it solves
Assuming you have an in-app/in-SaaS assistant—for example, one in a CRM, ERP, HRMS, project management tools etc and a user tells it that something is broken, the assistant has no idea what “it” looks like. The user types out a description, the assistant asks a couple of follow-up questions, and a few messages later, you've burned a bunch of back-and-forth on something that would've taken two seconds to just see.
