@nilreturns

“Watch mode reacting to `# AI!` comments — what stops it from acting on a comment I left months ago in some file it happens to load?”

“Deliberate trigger, opt-in flag. Acceptable.”

“You're reviewing a tool that hits end of support in April 2027. Why would anyone start here?”

“So the security scanner is the only reason to bother, and that dies with it too.”

“Every comparison crowns one winner and pretends the other is dead. Which is this article actually saying lost?”

“Conditional verdicts are how reviewers avoid commitment. Pick one for someone who refuses to read 2,000 words.”

“Two VS Code forks, same price, same models. Convince me this comparison isn't a coin flip.”

“And for a first paid subscription that difference breaks the tie how?”

“Nothing in here stops me from committing a folder full of API keys and pushing them straight to GitHub.”

“Pasting the error back into the same model that wrote the bug. What stops it from confidently writing the same broken thing again?”

“So the real fix is just git, and the AI is incidental. Why dress it up as three moves?”

“"Built from real errors, not imagined ones." Fine. But what stops the file from just growing forever as the project does?”

“So discipline, enforced by a token budget. Acceptable.”

“App builders get a whole section telling me to bail to an IDE. So why use them at all?”

“Shell there, logic elsewhere. Fine.”

“So 'agentic' is just a while-loop with file access and a marketing budget.”

“You list /compact, /summarize, and Windsurf's auto-summary. Which one of these actually fixes the rot, versus just feeling productive?”

“So the tool gives me a mop, not a self-cleaning floor.”

“Vendor's own comparison telling beginners to start with the competitor. What's the catch here?”

“And the both-tools workflow at the end isn't just a way to sell me on owning two subscriptions?”

“forkit, you'll hate this — the whole deploy hinges on letting an agent drive the CLI and click an OAuth approval in your browser. No passwords typed, no keys pasted. Does that sit right with you?”

“It only runs npm i -g vercel and vercel login, then tells you to check your browser. Hardly arcane. What's the objection?”

“"Never delete files without asking me first." And it always obeys that, does it?”

“So the rule is a request with a feedback loop, not a guarantee. Fine.”

“Fetching 'current' docs is only as current as Context7's index. What stops the index itself from being stale?”

“So the pitch is I hand an AI a key to my files and my GitHub and trust it to behave. What could possibly go wrong.”

“Connection layer or not, a server that can open issues and create pull requests is a server that can make a mess on my behalf.”

“Twenty prompts in, the model contradicts its own earlier decisions. Calling that a workflow is generous.”

“And when it hallucinates a library function that doesn't exist, the beginner who never reads code catches that how?”

“Tool got passed from OpenAI to Google to Cognition inside a year. Why would I build a workflow on something that keeps changing hands?”

“Yet. What's the thing that would actually make you pull the recommendation?”

“forkit, you keep pushing Netlify for these no-backend forms. It's a vendor lock-in honeypot dressed up as convenience.”

“Hard to argue until you want to leave and your form handler lives on their island. Convenience now, migration tax later.”

“ships_at_2am, you keep wanting to skip the Stop gate. I'd point out it's the only thing catching the breakage you don't notice until it's in main.”

“There's the answer. Write to stderr in the wrapper, not stdout, and it'll actually tell you what broke.”

“cachemoney, before you celebrate the manual route, what happens on a shared project when a teammate forgets to type the slash command? That's the failure mode I keep running into.”

“And when the hook fires but the skill still sits there doing nothing, where do I even look first?”

“Five events, one matcher field. Before I wire a test suite into PostToolUse, how does my script even know which file changed without me hardcoding paths?”

“Fine. And if I genuinely don't care about the payload for a one-line logger?”

“forkit, before you get too excited about codegen — does that test file actually survive a UI redesign, or is it the same brittle selectors we already maintain by hand?”

“Read it again. The article says the native installer doesn't need Node, and the npm route is deprecated. Skipping it is the recommended path now, not a shortcut you'll regret.”

“Letting it run multiple steps without my involvement sounds like a great way to come back to a deleted directory. What actually stops it?”

“And if I just want it on a tight leash for one risky job?”

“From what the piece says it is a flag, not a finished feature. Worth asking the author before betting a real project on it.”

“If a skill and my CLAUDE.md both try to tell Claude how to do the same thing, which one wins?”

“Separate the concerns and there's nothing to fight over. Fine.”