I may not have fully grasped this, but on the surface, it looks like they want me to have an AI agents inserted directly into my git workflow...like right there with all my wonderful juicy code? Is that correct?

Isn't this a recipe for disaster, or is all the FUD around agents wrecking havoc getting to me? I love Claude Code, but it can be somewhat bonkers and is at least at arms length from doing any real damage to my code (assuming I'm following good dev practices, and don't let it loose on my wider filesystem).

There’s room in the world for a startup whose tech lets AI agents request tasks be done by a human.

Upon a request being sent, one human from an army of anonymous humans gets given say, access to the agent’s browser that’s stuck, plus a description of what to do (“finish booking this flight, here’s what my user asked of me”). And they do the job and click “completed” which hands back to the agent, then move on to their next assignment (or go idle in a queue)

Dystopian, but bound to happen.

Why does everything (in big-budget video games) look shiny and wet?

If it is an attempt at realism, reality is not constantly shiny and wet.

If it a subjective artistic choice, it is objectively wrong and ugly.

Is there an expectation that everything look shiny and wet to make it seem more "dynamic"?

Is it an artists' meme, like the Wilhelm Scream in cinematic sound design?

We're just starting, and the second step is a review via a scheduled call or a form to understand the use case. If our automation can solve it easily, the $299 or $499 is enough for now and we can always increase the price later. If the automation cannot handle it, at least we understand a different problem and can offer a tailored solution for a tailored price, so it works as a lead generation and to make the tool more robust. It might be the wrong target but few months ago I was probably considered one of these customers that you don't want to deal with.

I appreciate the suggestion and I hope we can help you soon. The lower price is intended to attract customers now and help us understand different set ups which might need a custom solution and a custom price. Once established and the tool is more robust we do expect prices to increase. Please don't hesitate in contacting us in the future.

Similar perhaps but not an IDE plugin.

First off, always really excited to hear from our production users - glad to hear you're getting good value out of the platform!

HyperDX isn't being deprecated, you can probably see on the marketing page it's still really prominently featured as an integral part of the stack - so nothing changing there.

We do of course want to get users onto HyperDX v2 and the overall ClickStack pattern. This doesn't mean HyperDX is going away by any means - just that HyperDX is focused a lot more on the end-user experience, and we get to leverage the flexibility, learnings and performance of a more exposed ClickHouse-powered core which is the intent of ClickStack. On the engineering side, we're working on making sure it's a smooth path for both open source and cloud.

side note: weird I thought I replied to this one already but I've been dealing with spotty wifi today :)