[2001zhaozhao]

But why build your own from scratch when you can do it on top one extensible UI platform that already has all of your organizational context, not to mention coding agents already built-in that you can just tell it to build & deploy your personalized workflow softwaree from scratch? ;-)

[customguy]

Because it's fun! I don't "really" use LLM for anything serious yet, but after discovering playing with a custom harness I licked blood. Like going back to edit any message to start a new conversation branch off that, or being able to go back and remove things that turned out to to be dead ends from the history. Not really "useful" [0] for now, I always wondered about that and I was dumbfounded how trivial and tiny a first MVP was. Of course, that's also because it is trivial, it's just chat, it affords none of the usefulness you'd want for any "work", but it's still very interesting.

And for some simple recurring tasks or local housekeeping stuff, having something where I 100% know what files it reads or writes will surely be useful. E.g. if I wanted to watch out for certain topics on HN, I'd rather make something myself that grabs the feed and turns that into a list of titles and topic ID, which is probably 1% of what the front page HTML would be, and then only have the LLM process that output -- rather than telling an LLM to do all that every time. Even if tokens may not be that precious, and the difference in "cognitive performance" not worth speaking of, that would feel way neater to me.

[0] https://imgur.com/a/ZL8dhYg

[papascrubs]

That's an option right? When I say roll your own-- it could be extending another platform. There's definitely different levels. Customization is in reach regardless of where you want to start and stop your stack.