93 karma · joined February 7, 2026
i'm trying to figure out what else i need to do to properly launch this besides some YouTube video demonstrations and additional promotion ... perhaps HN can tell me.
i realized if there's something to it, i'd probably find out organically with some selective promotion to more experienced agent wranglers.
i honestly figured i would see at least one project like this per week across here and Reddit when i started working on it last month, but i haven't seen anything with this approach. do let me know if i have missed some.
it's obviously not an "original" idea; my headline probably should have included "Pi for writers" since that seems to be the closest analogue, though i admit i have not tried Pi myself yet. but it definitely has some unique aspects.
particularly the "non-technical writer" orientation, which is likely the most interesting bit to me and definitely the most nerve-wracking ... to say nothing of my foolhardy belief that it might be useful to "writers who hate ai."
ultimately there's only one way to answer these anxieties: ship it. no use waiting around if part of my pitch is that it can still be a going concern in 100 years!
the help content surfaced in the UI is frankly most of the documentation this initial version needs, but i added some FAQ type stuff at http://enough.support too.
so: what do you think?
but if caring about and solving customer problems was an actual income driver for a company, it could be very different.
i don't think that's going to happen, because i think most users (like Anthropic's) will continue to refuse to pay >$0 for support -- or to claim that their subscription payment should somehow also cover support, which is ridiculous, since they can see with their own "eyes" how little support their "compute subscription" gets them -- and thus companies will continue to invest ~$0, if not less, in meaningful support models.
it still blows my mind that nobody is willing to try charging people an extra $20 a month for unlimited support calls. most customers are DESPERATE for people to talk to about their problems.
instead, they all just try to winnow the cost down as low as possible, and then point to the expense to explain the degradation of service.
it enforces very few paradigms, runs in the browser, and allows users to view and edit agent config files within the UI.
it's kind of a nightmare to try to figure out how to do this appropriately, but it's an interesting challenge and i have seen very few (~0?) projects with an approach like this ...
all the offline harnesses are optimized towards coding, vs. general text manipulation aka "writing."
hoping to publish v0.1.0 by the end of may.