正在加载视频...

视频加载失败

Introducing Trajectories in LangSmith. A view of agent behavior that everyone on the team can understand at a glance.

25,015 次观看 • 12 天前 •via X (Twitter)

7 条评论

Anurag Bhagsain 的头像
Anurag Bhagsain12 天前

@trylatitude already does this and @manuelnavid and team shipping everyday 🔥

Jan Kvaček 的头像
Jan Kvaček10 天前

Readable trajectories are hugely useful, but I'd separate two questions: 1. What path did the agent take? 2. Did the task actually succeed? The trajectory explains process. A separate acceptance test should prove outcome. A perfect trace can still document a perfectly executed wrong result.

Tommy YC 的头像
Tommy YC12 天前

A trajectory view turns agent debugging from replay archaeology into a team habit.

Hershal Rao 的头像
Hershal Rao12 天前

finally a visualization tool so PMs can watch my agent fail in real time

Enterprise Hub AI 的头像
Enterprise Hub AI12 天前

A trajectory that shows the tool calls is useful — you can finally see what the agent tried. It seems the part that’s still missing on a real write is whether someone approved that version of the plan, under a scoped identity, and whether you can read the record back after commit. If the write never went through, does the trajectory say “refused,” or does it just stop?

Nikhil Bhade 的头像
Nikhil Bhade12 天前

Telemetry FTW

Divyendra Singh 的头像
Divyendra Singh12 天前

Can teams redact sensitive tool outputs before sending trajectories to SME annotation queues?

相关视频