Live data from Hacker News

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

news.ycombinator.com

11–20 of 29 posts

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

#11
post #5

Any ideas how to solve the agent's don't have total common sense problem? I have found when using agents to verify agents, that the agent might observe something that a human would immediately find off-putting and obviously wrong but does not raise any flags for the smart-but-dumb agent.

Only solution is to train the issue for the next time.

Architecturally focusing on Episodic memory with feedback system.

This training is retrieved next time when something similar happens

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

#12
post #5

Any ideas how to solve the agent's don't have total common sense problem? I have found when using agents to verify agents, that the agent might observe something that a human would immediately find off-putting and obviously wrong but does not raise any flags for the smart-but-dumb agent.

Only solution is to train the issue for the next time. Architecturally focusing on Episodic memory with feedback system. This training is retrieved next time when something similar happens

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?

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

#16

Testing voice agents would require some kind of knowledge integration. Do you have any plans to support custom knowledge bases for test voice agents ?

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

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

#17

How do you handle sessions where the correct outcome is an incomplete flow — e.g. the agent correctly refuses to move forwards because the caller failed verification, or correctly escalates to a human?

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

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

#19
post #12

Earlier quoted context omitted.

Only solution is to train the issue for the next time. Architecturally focusing on Episodic memory with feedback system. This training is retrieved next time when something similar happens

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?

Nope - just use memory layer with model routing system.

https://github.com/rush86999/atom/blob/main/docs/EPISODIC_ME...

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

#20
The full-session evaluation framing is the right call - most teams don't realize the failure happened in turn 2 until they've spent 3 hours blaming the model. One thing worth thinking about as you grow: connecting caught regressions to production conversation data. When your simulation flags a new failure mode, being able to say "this pattern has already surfaced X times in prod this week" cuts the prioritization debate in half. Does Cekura currently let you correlate simulation failures back to real user sessions, or is that still a manual step?
Post reply on HN