Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
121–130 of 206 posts
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#122Earlier quoted context omitted.
so what I'm hearing is, if the approval is transparent and the agent doesn't see it, thats cool, but tell the agent "hey use the human as needed" and now we're getting into sci fi territory ?! either way i don't totally disagree
get more emphatic names, something better than "human_as_a_tool".
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#123Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#124So this is flipping the Human-AI working model and basically using the human as the tool?
The limits of LLM capabilities will cause AI agents to displace people from warehouses/offices to their home doing conceptually the same job. And at a much lower salary, since they'll compete against anyone in the world with internet access.
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#125The API contains a "human_as_tool" function. That's so like Marshall Brain's "Manna".
"Machines should think. People should work." Less of a joke every day.
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#126Startup owner using AI with this need - needless to say, a real problem. I've considered DIYing an internal service for this - even if we went with you we'd probably have an intern do a quick and dirty copy, which I rarely advocate for if I can offload to SAAS. I'm sure you've put a fair bit of work into this that goes well beyond the human interaction loop, but that's really all we need. Your entry price is steep (I…
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#127Oh look! Corrupt Dang made another launch HN a top post. So much corruption on this website.
The instructions for YC founders are here: https://news.ycombinator.com/yli.html, if anyone wants to take a look.
I think most people here consider it fair that HN gives certain things back to YC in exchange for funding it.
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#128So this is an automated foreman for the customer's own employees, like a call center controller? Or does HumanLayer provide the human labor, like Mechanical Turk? The API contains a "human_as_tool" function. That's so like Marshall Brain's "Manna". "Machines should think. People should work." Less of a joke every day.
> "Machines should think. People should work." Less of a joke every day.
yes. I agree. a little weird. I forget where I heard this but the other version is "we should get ai/robots to cook and do laundry so we can spend more time writing and making art...feels like we ended up the other way around"
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#129Earlier quoted context omitted.
i never thought about undoable actions but I love that workflow in tools like superhuman. I will chat w/ some customers about this idea. I also like that idea of: not just a button but like 'I'm $PERSON and I approve this action' or type out 'Signed-off by' style semantics
I think the canonical sort of approach here is to make them confirm what they're doing. When you delete a GitHub repo for example, you have to type the name of the repo (even though the UI knows what repo you're trying to delete). If the table name is SuperImportantTable, you might gloss over that, but if you have to type that out to confirm you're more likely to think about it. I think the "meat space" equivalent of…
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#130Nice. I guess the issue is that this is such a basic i/o feature that any system with some modicum of customization can already do it. It's like offering a service that provides storage by api for agents. Yeah, you can call the api, or call the s3 api directly or store to disk. That said, I would try it before rolling my own.
And what we build still only serves a small subset of use cases (e.g. to support attachments there's a whole other layer of MIMEtype management and routing to put things in S3 and permission them properly)