News for hackers. Stuff that matters.

atarus

Re:Launch HN: Relvy (YC F24) – On-call runbooks, automated on Thursday April 09, 2026 @02:03PM (#47707156)
Interesting! In my experience using custom harnesses has worked better eg: Stripe etc all did it custom largely because of the sensitive integrations. How would you handle that?
Memory is usually slow and haven't seen many voice agents atleast leverage it. Are you building in text modality or audio as well?
We track the failure modes in production directly instead of relying on simulation. So if suddenly we are seeing a failure mode pop up too often, we can alert timely. In the approach of going from simulation to monitoring, I am worried the feedback might be delayed.

Doing it in production also helps to go run simulations by replaying those production conversations ensuring you are handling regression.

This comes from our architecture. Since we are aware of the agent's context our test agents know the incomplete flows and the assertions are per session.

If we miss some cases, there's always a feedback loop to help improve your test suite

Yes, we already support knowledge base integrations for BigQuery and plan to expand the set of connectors. You can always drop knowledge files currently.

Moreover, we even generate scenarios from the knowledge base

Training is an overkill at this point imo. I have seen agents work quite well with a feedback loop, some tools and prompt optimisation. Are you doing fine-tuning on the models when you say training?
That's actually interesting. Is it a dependancy on user to create the HTTP endpoints for the /speak and /transcript?

One of our learnings has been to allow plugging into existing frameworks easily. Example - livekit, pipecat etc.

Happy to talk if you can reach out to me on linkedin - https://www.linkedin.com/in/tarush-agarwal/

To clarify you are using the "fast brain, slow brain" pattern? Maybe an example would help.

Broadly speaking, we see people experiment with this architecture a lot often with a great deal of success. A few other approaches would be an agent orchestrator architecture with an intent recognition agent which routes to different sub-agents.

Obviously there are endless cases possible in production and best approach is to build your evals using that data.

Yes, we do support integrations with different chat agent providers and also SMS/Whastap agents where you can just drop a number of the agent.

Let us know how your agent can be connected to and we can advise best on how to test it.

Launch HN: Cekura (YC F24) – Testing and monitoring for voice and chat AI agents

Hey HN - we're Tarush, Sidhant, and Shashij from Cekura (https://www.cekura.ai). We've been running voice agent simulation for 1.5 years, and recently extended the same infrastructure to chat. Teams use Cekura to simulate real user conversations, stress-test prompts and LLM behavior, and catch regressions before they hit production.The core problem: you can't manually QA an AI agent. When you...

( Read More... | 25 comments | 21 points | on HN )

Cekura (YC F24) Is Hiring

Cekura is growing fast, and we’re now building our Customer Success vertical from the ground up. If you love owning outcomes, turning customers into champions, and shaping 0→1 playbooks, this is for you.You will be joining at that perfect moment where what we’ve built works and our customers are challenging us everyday.We grew as much in the first week of November as in all of October - equal...

( Read More... | no comments | on HN )
Re:Gemma 3 Technical Report [pdf] on Wednesday March 12, 2025 @03:10AM (#43340609)
Looks great! So excited about this! We have been using gemma models since gemma 1.0 and they are so far ahead of the curve!