Hacker Newsnew | past | comments | ask | show | jobs | submit | jaynate's commentslogin

The underpants gnomes. Well played!


1000%. The expense of writing software was and still is high.

Whether it’s commercial software company or an internal team writing custom software, the return on that investment depends on many things outside of the code itself.


When I initially saw this I was excited because what I’m trying to solve for is visibility of both semi and fully autonomous and agents at runtime. Marble is an improvement over chat and Claude but it’s incremental IMO.

We’ve toyed with a meta agent style interface which you chat to do everything. Add tools, connect datasets, build agents, deploy and schedule them, build skills, etc.

But at some point agents have to have an interface for human approvals, validation, training, and tuning.

I guess it’s like a spreadsheet. Ultimately agents are part of custom apps which are each going to be as unique like snowflakes. So it’s difficult to have one standard abstracted runtime interface without feeling obtuse to a business user. I think what I’m describing and wanting are new app layer building blocks vs one interface to rule them all.

All of this said, I’m all for a better personal llm harness interface (which is what this is). So keep up the great work guys!


>> Thanks for reading! Let me know if anyone's interested in more posts about this bowling nonsense.

I’d say, “yes!” judging from the upvotes.


Wow, can’t understand why this isn’t getting more attention.


Not sure. But thanks for the attention though have loads of features in main - to be released soon!


Are you running in any enterprise environments that you know of?


Got an update. Some startups are using it. It comes with Zscaler/Netskope/etc compability as well!


For clarity, inference is typically a COGS and therefore hits Gross Margin vs model training which would typically be in OpEx (where R&D lives) and would hit operating margin.


Feels like we’re continuing to trend toward deterministic workflows which may actually be okay in 90% of cases. Reality is there’s a lot of unnecessary token burn happening right now. Simple market dynamics will solve that, i.e., when token cost subsidies begin to fade away and we face the true cost of agent applications.


Bingo. All this agentic hype is just people discovering POCs. Yes you can hodgepodge semi-reliable solutions where you don't really know what you're trying to build so you wrap it in a layer than can sometimes approximate logic and decision making, so that you don't have to use logic or make decisions. Amazing.

Sooner or later you have to build the real thing, and the cost and slowness of token-based computation become unacceptable.


Yes, and the free-for-all building of nonsense (and insecure) apps by non engineers is probably going to slow down as well.


Simply... amazing


Isn’t there coverage on any other site with fewer ads and popups? I could literally barely navigate the article on my phone.


“Their relationship with the software is one of pure dependency, and when the software doesn’t do what they need, they just… live with it”

Or, more likely, they churn off the product.

The SaaS platforms that will survive are busy RIGHT NOW revamping their APIs, implementing oauth, and generally reorganizing their products to be discovered and manipulated by agents. Failing in this effort will ultimately result in the demise of any given platform. This goes for larger SaaS companies, too, it’ll just take longer.


And I think it’s less about letting agents modify the product source. That’s more of a platform capability which should also be a requirement for certain types of use cases. All comes back to listening to and / or innovating for customers.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: