Загрузка видео...

Не удалось загрузить видео

На главную

Agent harnesses explained in <90 seconds. TLDR: if you’re not working on the model, you’re working on the harness.

15,584 просмотров • 11 дней назад •via X (Twitter)

Комментарии: 8

Фото профиля 安叫兽|Bird🕊️ 🔶 BNB
安叫兽|Bird🕊️ 🔶 BNB11 дней назад

模型还没搞明白,套件先学会了也挺真实的

Фото профиля Matthew
Matthew11 дней назад

What's going ond Sounds like someone's trying to describe a new way of understanding something!.

Фото профиля Ramanu Henri Jan
Ramanu Henri Jan11 дней назад

@grok comment faire une vidéo comme ça

Фото профиля Anima
Anima11 дней назад

The harness distinction is key - reliability, permissions, and tool loops are where agent products become usable.

Фото профиля AgentAllowlist
AgentAllowlist11 дней назад

Yes. We spent months in the harness and the thing that kept biting us was the agent opening pages it had no business opening. No harness had a map of the web, so we built one. AI agent allow list: 40M domains, 28 page types, login, checkout and upload denied before the tool call.

Фото профиля Yi Casillas
Yi Casillas11 дней назад

这句很到位,模型会换,但上下文、工具和失败处理才是最磨人的那层。

Фото профиля Ricardo 👺
Ricardo 👺11 дней назад

this harness vs model split is so real right now. most teams i see shipping agents are just fighting the orchestration, memory, tool calling and eval loop anyway. the model is almost becoming a commodity at this point. good explainer tho, gonna check that academy course later.....

Фото профиля SOP | AI Agent Builder
SOP | AI Agent Builder11 дней назад

A harness becomes production-grade when each run emits a replayable trace: model and tool versions, arguments, state transitions, latency, cost, and evaluator verdict. Keep a small failure corpus in CI so harness changes are tested against regressions, not just happy-path demos.

Похожие видео