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

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

На главную

Agent Trace: Capturing the Context Graph of Code We are delighted to collaborate with Cursor, OpenCode, Vercel, Jules, Amp, Cloudflare, and Sasha Varlamov in an open standard for mapping back code:context. here's how we see the potential of code context graphs and the new era of better tooling and...

39,869 просмотров • 7 месяцев назад •via X (Twitter)

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

Фото профиля Cognition
Cognition7 месяцев назад

@opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov our full writeup below . Thank you to @leerob for his leadership in driving this spec. We're encouraging the rest of the coding agents industry to join us.

Фото профиля fkz
fkz7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov Ai slop ppt

Фото профиля Spenser Skates
Spenser Skates7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov Sign us up:

Фото профиля Rey Neill
Rey Neill7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov was too ahead of its time

Фото профиля Shamim Hossain
Shamim Hossain7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov That's great

Фото профиля Cheng Yang
Cheng Yang7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov without anthropic it will be hard, but nice to see more players try to define new open standards

Фото профиля Kyle Tran
Kyle Tran7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov Open standard for tracing agent conversations to code is a pragmatic move toward interoperable tooling and tangible ROI

Фото профиля Saïd Aitmbarek
Saïd Aitmbarek7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov based, let's go!

Фото профиля y_qecea
y_qecea7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov tahts insane if free

Фото профиля naeem (e/acc)
naeem (e/acc)7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov Nice, a universally agreed method to store the context of AI generated code.

Фото профиля Robert Hu 🦉
Robert Hu 🦉7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov Context graphs solve the single biggest failure mode for AI coding agents: they stop asking the codebase what it already knows.

Фото профиля Eddie
Eddie7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov so sure about wars and usd boosts? history says markets shrug off even the loudest bets. good luck with that crystal ball.

Фото профиля madison
madison7 месяцев назад

@cursor_ai @opencode @vercel @julesagent @AmpCode @Cloudflare @savarlamov wtf is this music

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

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,180 просмотров • 3 месяцев назад

We've built 40+ AI agents and internal tools. The hardest part is Context Creation. AI runs playbooks and makes judgment calls for you. But without your company's context, you get slop. Context Creation means extracting the subject matter expertise and playbooks that live in people's heads, not in LLM training data, or even your tools. As forward deployed engineers (FDEs), we create context and turn it into code. We evaluate the business impact, how it aligns with the dev roadmap, and come up with creative solutions. We built The FDE Factory to replace ourselves. It drives AI adoption inside our clients' companies by running discovery sessions using prototypes to create context. Here's how it works: We put a prototype in front of a stakeholder. The stakeholder gives feedback via voice while they're using or reviewing it. Then our FDE Factory Agents builds in their expertise in minutes: > Context Agent reviews the codebase and feedback, extracts the requirements, and creates a spec > Scope Agent checks the spec against the development roadmap, validates it, and hands it off > Engineering Agent builds a new feature and wires the integration > QA Agent runs tests to prove to itself it works > PR merges, feature goes live, product updates itself in real time It's like the nontechnical stakeholder wrote the code without even knowing it. Coding agents are great at turning good development plans into code, and they're getting better at turning context into good development plans in collaboration with professional engineers. But nontechnical people are capped on what they can build without product people and engineers. The bridge that takes nontechnical people from vibe coding basic apps to building production AI tools that run on first party context is FDEs. Our new FDE Factory gives you the system to go from idea to production. Context Creation is the first and most important step in our FDE lifecycle, and we just automated it. Now clients get the right agents and tools built for them, customized to their unique business and encoded with their expertise. PS: If you're building AI agents within your company, reply "Playbook" and I'll DM you the entire FDE playbook we've run with 30+ companies. It covers finding high-impact AI use cases, building them, and deploying them across the org.

Mike Fishbein

10,171 просмотров • 3 месяцев назад