hermes-ai.net

문서 보기 →
HermesHermes Agent 문서
← Back to case library
Case / 2100928490367230201자동화
Case media / 1MP4 ↗
Verified

Localized reading

@typesafeai Jev에 조기 액세스하고 이를 구축하는 데 몇 시간을 보냈습니다. 제가 계속 겪고 있는 문제는 에이전트 추적을 통해 어떤 도구가 실행되었는지, 얼마나 오래 걸렸는지, 무엇을 반환했는지 알려 주지만 에이전트가 작동하는지 여부는 알려주지 않는다는 것입니다.

Original post / EN

Got early access to @typesafeai Jev and spent a few hours building on it. The problem I keep hitting: agent traces tell you which tool ran, how long it took, what it returned but never whether the agent is actually getting anywhere. An agent editing, testing and reverting the same file six times looks perfectly healthy in the logs. So I made JevScope. It watches an AI agent work and asks Jev what each step actually means is this aligned with the task, is it progress, is it repeating itself, is it stuck. Every step, plotted over time. Here's a coding agent getting stuck on a race condition. Watch the yellow line. No log line says "I'm stuck." The curve does. Detailed demo, code and writeup coming soon.
views
1.2천
likes
8
saves
1
reposts
1
원문 보기 ↗

Quoted post

Diogo Almeida @CompleteSkeptic

After co-inventing ChatGPT, I kept asking myself: why have superhuman chat models not led to AGI? I’ve spent the last 2 years in stealth building a new way to train models (RLCD), and a new type of frontier AI model that we are releasing today: Jev • 20-200x faster • 40-400x https://t.co/JSybNG2BKJ

원문 보기 ↗

출처

This independent archive preserves a public post with attribution. Text, media, account details and trademarks belong to their respective owners.