Priyam Sekra

The one where setting up a local AI brain stops being a spelling test pick a chip, done.

And it's a special one: this is Skim's first release built on a pull request from an outside contributor.

Since our last launch we've been heads-down on one thing: making "this integration works" actually mean something. Here's what changed, and why we're more confident than a month ago.

What we shipped?

Five integrations now recognize the bugs people actually hit and prove the fix with a real before/after:

I've shipped work where 90%+ of the code came from prompting an agent, with me mostly reviewing, testing, and directing the architecture. Never explicitly disclosed that to the client, they just know it got done fast, works well, and stayed in budget.

Is that dishonest, or is it no different from using a framework, a library, or a junior dev and not itemizing every line's origin? Nobody used to ask what percentage of a website a developer typed themselves versus copied from Stack Overflow or scaffolded with a generator.

But this feels different somehow, maybe because the speed and volume are so much higher, or because "AI-written" still carries a stigma that "used a library" doesn't.

Where's your personal line? Do you disclose upfront, stay quiet unless asked, or does it depend entirely on who's paying and what they'd actually do with that information?