It's generally recommended to add a meat-gap interface between AI systems to reduce unexpected results. Meat-gap. We have your back.
BRB rebranding to meatgap.dev
Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
171–180 of 206 posts
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#172Definitely a problem that everyone needs to solve. I wonder if you can achieve this workflow by just using prompt and the new Model Context Protocol connected to email / slack. https://www.anthropic.com/news/model-context-protocol
so I played with MCP for a while last night and I think MCP is great as a layer to pull custom tools into the existing claude/desktop/chat experience. But at the end of the day its just basic agentic loop over tool calls. If you want to tell a model to send a message to slack, sure, give it a slack tool and let it go wild. do you see a way how MCP applies for outer-loop or "headless" agents in a way that's any differ…
I think the fact that MCP is two ways, and tool call is asynchronous (since it's over network), means that it should be possible to code an approval flow with a prompt and a slack approval tool?
Yeah it still takes a bit of work, but it's more extendable (can swap slack to email) and more versatile (human can message agent to interrupt or ask for clarification).
I haven't used langchain (beyond RAG) or crewai, not sure what was capable before.
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#173congrats on the launch dex! this is a problem that i've already seen come up a dozen times and many companies are building it internally in a variety of different ways. easier to buy vs. build for something like this imo, glad its being built!
awesome - glad to hear it resonates
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#174Hiring humans to do a consistent job is gonna be a nightmare and a limit on the scalability of the service. How are you defining your service level agreements?
This really makes you take a step back and just consider the world we're in now: someone critiques a company's approach as unscalable because... "hiring humans is a nightmare" Good LLord
lol i like LLord I might steal that
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#175This is great. I can let you pay for that flight once the agent finds a match.
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#176This is great. I can let you pay for that flight once the agent finds a match.
you get it
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#177Isn't this precisely how AI started? It was a bunch of humans under the hood doing the logic when the companies said it was AI. Then we removed the humans and the quality took a hit. To fix that hit, 3rd party companies are putting humans back in the loop? Isn't that kind of like putting a band-aid on the spot where your arm was just blown off?
> Then we removed the humans and the quality took a hit.
What are you referring to exactly?
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#178You’re close. It’s not the humans in the loop in standard tasks you need though, it’s human surrogates for AI agents to do jobs they can’t for a variety of reasons (like missing a body or requiring an internet connection). I have a request for startups for this: “GraggNet: Task Rabbit for AIs Surrogate humans for AIs to use before robotics are human level” https://ageof.diamonds/rfs
[deleted]
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#179Sounds great. Perhaps an interesting aspect: I haven't discovered the right words for it but: If it is your job, answer the fucking question. This layered approach might prove more of a gain than imagined. They might not show it but some people are terrified to ask even the first question. Others think it perfectly fine to ask 100 questions they already know the answer to.
Re: Launch HN: Human Layer (YC F24) – Human-in-the-Loop API for AI Systems
#180Earlier quoted context omitted.
hah thanks dude! I am very bullish on TS as the long term thing, Not to turn this into a language vs language thread but I spend a lot of time thinking about why ppl struggle so much with python...so far I came up with concurrency abstractions keep changing (still transitioning / straddling sync+threads vs. asyncio) - this makes performance eng really hard package management somehow less mature than JS - pip been aro…
I am okay with a counterfactual alternate future where some disproportionately powerful entity squeezes Python out of the market: Big TypeScript - funded by a PAC. Offshore accounts. Culprit: random rich Googler who lost an argument to Guido Van Rossum 10 years ago.
lol this is why i come to this site