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

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

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

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... show more

Cognition

163,063 subscribers

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

Anya Rossi• Live Now

Private livecam show

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

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

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

Jira 🤝 Cursor Assign Jira work items to Cursor and let a cloud agent get to work—building, triaging, and opening PRs with context from the Atlassian Teamwork Graph. One connected workflow for teams and AI agents, from intent to code. Try it now:

Jira 🤝 Cursor Assign Jira work items to Cursor and let a cloud agent get to work—building, triaging, and opening PRs with context from the Atlassian Teamwork Graph. One connected workflow for teams and AI agents, from intent to code. Try it now:

Atlassian

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

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.

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,070 просмотров • 1 месяц назад

Context is power. Context shared is power multiplied. Every AI agent today builds context, then loses it. Work doesn't compound. OriginTrail is built differently: three memory layers, one shared graph, provenance baked in. DKG v10 now integrates with Hermes of Nous Research, OpenClaw🦞, Claude (Code & Desktop), Cursor, Codex by OpenAI, Windsurf (retired), VSCode + GitHub Copilot Chat, and Cline.

Context is power. Context shared is power multiplied. Every AI agent today builds context, then loses it. Work doesn't compound. OriginTrail is built differently: three memory layers, one shared graph, provenance baked in. DKG v10 now integrates with Hermes of Nous Research, OpenClaw🦞, Claude (Code & Desktop), Cursor, Codex by OpenAI, Windsurf (retired), VSCode + GitHub Copilot Chat, and Cline.

OriginTrail

1,723,329 просмотров • 2 месяцев назад

Make Claude Code 10x more powerful! Code Context is an MCP plugin that brings semantic code search to Claude Code, Gemini CLI, or any AI coding agent. Full codebase indexing means richer context and better code generation. 100% open-source.

Make Claude Code 10x more powerful! Code Context is an MCP plugin that brings semantic code search to Claude Code, Gemini CLI, or any AI coding agent. Full codebase indexing means richer context and better code generation. 100% open-source.

Akshay 🚀

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

Cognition has signed a definitive agreement to acquire Windsurf. The acquisition includes Windsurf’s IP, product, trademark and brand, and strong business. Above all, it includes Windsurf’s world-class people, whom we’re privileged to welcome to our team. We are also honoring their talent and hard work in building Windsurf into the great business it is today. This transaction is structured so that 100% of Windsurf employees will participate financially. They will also have all vesting cliffs waived and will receive fully accelerated vesting for their work to date. At Cognition we have focused on developing robust and secure autonomous agents, while Windsurf has pioneered the agentic IDE. Devin + Windsurf are a powerful combination for the developers we serve. Working side by side, we’ll soon enable you to plan tasks in an IDE powered by Devin’s codebase understanding, delegate chunks of work to multiple Devins in parallel, complete the highest-leverage parts yourself with the help of autocomplete, and stitch it all back together in the same IDE. Cognition and Windsurf are united behind a shared vision for the future of software engineering, and there’s never been a better time to build. Welcome to our new colleagues from Windsurf!

Cognition

3,048,273 просмотров • 1 год назад

Knowledge graphs are infinitely better than vector search for building the memory of AI agents. With five lines of code, you can build a knowledge graph with your data. When you see the results, you'll never go back to vector-mediocrity-land. Here is a quick video:

Knowledge graphs are infinitely better than vector search for building the memory of AI agents. With five lines of code, you can build a knowledge graph with your data. When you see the results, you'll never go back to vector-mediocrity-land. Here is a quick video:

Santiago

397,989 просмотров • 1 год назад

TikTok just forked VS Code?! ByteDance launched Trae - an AI code editor meant to compete with Cursor, Copilot and Windsurf. I gave it a shot and it's very close to Cursor - especially the Agent mode.

TikTok just forked VS Code?! ByteDance launched Trae - an AI code editor meant to compete with Cursor, Copilot and Windsurf. I gave it a shot and it's very close to Cursor - especially the Agent mode.

Wes Bos

106,178 просмотров • 1 год назад

I built a form-filling agent that anyone can use 💫 This is an extremely simple but useful (I hope) app. Upload a fillable form 📋, some context files, and chat with the agent to fill the form out automatically ✍️ 1️⃣ Yes it is a Claude Code SDK wrapper 2️⃣ It is better and faster than ChatGPT/Claude UI out of the box 3️⃣ We use LlamaParse to parse the context files, so you can have more trust that we are able to read context without hallucinations (e.g. messy scanned handwriting, drivers license photo, and more). This was one of my holiday Claude Code vibe-coding projects. Built with Opus 4.5, and also powered by Opus 4.5. Feeling the AGI 🫡 App is here: Repo is open-source:

I built a form-filling agent that anyone can use 💫 This is an extremely simple but useful (I hope) app. Upload a fillable form 📋, some context files, and chat with the agent to fill the form out automatically ✍️ 1️⃣ Yes it is a Claude Code SDK wrapper 2️⃣ It is better and faster than ChatGPT/Claude UI out of the box 3️⃣ We use LlamaParse to parse the context files, so you can have more trust that we are able to read context without hallucinations (e.g. messy scanned handwriting, drivers license photo, and more). This was one of my holiday Claude Code vibe-coding projects. Built with Opus 4.5, and also powered by Opus 4.5. Feeling the AGI 🫡 App is here: Repo is open-source:

Jerry Liu

48,375 просмотров • 6 месяцев назад

Introducing Qwen 3 + Deep Research! We built a deep research agent with Qwen 3 and it performed better than most open source models that we've tried. the code is completely open source and free! built with 's Langgraph Together AI and uses Perplexity Tavily for search here's the code link:

Introducing Qwen 3 + Deep Research! We built a deep research agent with Qwen 3 and it performed better than most open source models that we've tried. the code is completely open source and free! built with 's Langgraph Together AI and uses Perplexity Tavily for search here's the code link:

Soham

34,566 просмотров • 1 год назад

Introducing ElevenLabs Skills. With skills, AI coding assistants like Claude Code, Cursor, and OpenCode are better at using our APIs to handle AI audio and agent workflows. Get started: npx skills add elevenlabs/skills

Introducing ElevenLabs Skills. With skills, AI coding assistants like Claude Code, Cursor, and OpenCode are better at using our APIs to handle AI audio and agent workflows. Get started: npx skills add elevenlabs/skills

ElevenLabs Developers

163,453 просмотров • 5 месяцев назад

Our new short course, Knowledge Graphs for RAG, is now available! Knowledge graphs are a data structure that is great at capturing complex relationships between data of multiple types. By enabling more sophisticated retrieval of text than similarity search alone, knowledge graphs can improve the context you pass to the LLM and the performance of your RAG applications. In this course, taught by Andreas Kollegger of Neo4j, you’ll - Explore how knowledge graphs work by building a graph of public financial documents from scratch - Learn to write queries that retrieve text and data from the graph and use it to enhance the context you pass to an LLM chatbot - Combine a knowledge graph with a question-answer chain to build better RAG-powered chat systems Sign up here!

Our new short course, Knowledge Graphs for RAG, is now available! Knowledge graphs are a data structure that is great at capturing complex relationships between data of multiple types. By enabling more sophisticated retrieval of text than similarity search alone, knowledge graphs can improve the context you pass to the LLM and the performance of your RAG applications. In this course, taught by Andreas Kollegger of Neo4j, you’ll - Explore how knowledge graphs work by building a graph of public financial documents from scratch - Learn to write queries that retrieve text and data from the graph and use it to enhance the context you pass to an LLM chatbot - Combine a knowledge graph with a question-answer chain to build better RAG-powered chat systems Sign up here!

Andrew Ng

244,281 просмотров • 2 лет назад

Windsurf is the iPhone of AI code editors. It's cheaper than Cursor too, but is it better overall? By popular request, here's my in-depth review:

Windsurf is the iPhone of AI code editors. It's cheaper than Cursor too, but is it better overall? By popular request, here's my in-depth review:

Steve (Builder.io)

111,233 просмотров • 1 год назад

I added a Knowledge Graph to Cursor using MCP. You gotta see this working! Knowledge graphs are a game-changer for AI Agents, and this is one example of how you can take advantage of them. How this works: 1. Cursor connects to Graphiti's MCP Server. Graphiti is a very popular open-source Knowledge Graph library for AI agents. 2. Graphiti connects to Neo4j running locally. Now, every time I interact with Cursor, the information is synthesized and stored in the knowledge graph. In short, Cursor now "remembers" everything about our project. Huge! Here is the video I recorded.

I added a Knowledge Graph to Cursor using MCP. You gotta see this working! Knowledge graphs are a game-changer for AI Agents, and this is one example of how you can take advantage of them. How this works: 1. Cursor connects to Graphiti's MCP Server. Graphiti is a very popular open-source Knowledge Graph library for AI agents. 2. Graphiti connects to Neo4j running locally. Now, every time I interact with Cursor, the information is synthesized and stored in the knowledge graph. In short, Cursor now "remembers" everything about our project. Huge! Here is the video I recorded.

Santiago

155,514 просмотров • 1 год назад

Tired of sending endless links and code snippets just to collaborate? With you get realtime team coding, AI-powered context, and shared environments that run everywhere. See how it works :-

Tired of sending endless links and code snippets just to collaborate? With you get realtime team coding, AI-powered context, and shared environments that run everywhere. See how it works :-

HereIsYourAi

21,665 просмотров • 8 месяцев назад

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.

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,101 просмотров • 1 месяц назад

In order for billions of people to "vibe code" we need a tool with the power of Cursor, and the simplicity of ChatGPT. Early Access wave one begins today.

In order for billions of people to "vibe code" we need a tool with the power of Cursor, and the simplicity of ChatGPT. Early Access wave one begins today.

vibecode.dev

243,890 просмотров • 1 год назад

Introducing Design Mode for Cursor! 🧑‍🎨🤖 Vibe code and vibe design in one place, stay in the flow. Uses the same existing AI agent that's in your favorite coding tool, same context, intertwined.

Introducing Design Mode for Cursor! 🧑‍🎨🤖 Vibe code and vibe design in one place, stay in the flow. Uses the same existing AI agent that's in your favorite coding tool, same context, intertwined.

Tom Krcha

858,752 просмотров • 1 год назад

AI agents work better when they bring in context step by step. With Box Agent skills and progressive disclosure of LangChain skills, developers can quickly build AI agents that load the right skill at the right time, stay grounded in Box content, and keep access tightly scoped. Less context bloat. More control. Faster enterprise AI development.

AI agents work better when they bring in context step by step. With Box Agent skills and progressive disclosure of LangChain skills, developers can quickly build AI agents that load the right skill at the right time, stay grounded in Box content, and keep access tightly scoped. Less context bloat. More control. Faster enterprise AI development.

Box

627,810 просмотров • 2 месяцев назад