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

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

На главную

🚀 Discover Agent Host in Visual Studio Code and see how your agent sessions persist across projects and run across multiple environments. From VS Code to the web and across machines, your sessions stay in sync wherever you work. 🧵 Check out the resources below 👇

33,711 просмотров • 2 месяцев назад •via X (Twitter)

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

Фото профиля Visual Studio Code
Visual Studio Code2 месяцев назад

🔗 Agent Host in VS Code:

Фото профиля Visual Studio Code
Visual Studio Code2 месяцев назад

🔗 Agent Host Protocol:

Фото профиля Visual Studio Code
Visual Studio Code2 месяцев назад

🔗 VS Code issue tracker:

Фото профиля Manas Tripathi
Manas Tripathi2 месяцев назад

the persistent session state across environments is a game changer for context switching. curious how you’re handling the diffs when multiple agents touch the same Next.js routes.

Фото профиля Allan Montilla
Allan Montilla2 месяцев назад

Closing a split shouldn't kill the agent. Persist the session across windows. That's the part I want.

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

Another insane Jev use case! Jev makes it incredibly cheap to evaluate and classify agent runs at scale. And finally, someone open-sourced a self-improving memory layer that can put that capability to work across agent harnesses. It turns your agent sessions into a compounding knowledge layer, where every successful run can make future agents smarter across: - Codex - Claude Code - Cursor - OpenCode and 20+ more Beacon by Asymptote Labs continuously builds a shared history across your agent harnesses and uses Jev to identify the runs worth learning from. It then turns the best workflows, corrections, and debugging patterns into reusable skills. GitHub repo: (don’t forget to star it ⭐) Most agent runs are messy. They contain exploration, failed commands, dead ends, and one-off fixes that should never become permanent memory. So Beacon preserves the full session history, while Jev helps decide what should be promoted, reviewed, or discarded. The recording below shows this in action. Beacon found 579 sessions across 5 coding-agent harnesses and normalized them into one consistent history. From there, Jev surfaces the lessons worth keeping and makes them available across your agent stack. - A pattern learned in Cursor can carry into OpenCode. - A lesson from Claude Code can improve the next Codex run. Every successful run adds to the shared knowledge layer, making future agents smarter. If you want to dive deeper into Jev, I also wrote a breakdown of how it works. The article is quoted below.

Akshay 🚀

120,930 просмотров • 1 месяц назад