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

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

На главную

Get to know River, our internal agent that among other things drastically reduces the cost of context gathering across the company. No more digging through docs, Slack, and requiring people to spread context. A new kind of information architecture. Talked about this with tobi lutke on our Context episode:

jessicarhertz's profile picture

Jessica Hertz

2,596 subscribers

14,162 просмотров • 4 месяцев назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

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

Фото профиля Jessica Hertz
Jessica Hertz4 месяцев назад

Worth the read:

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

@tobi Love this, Jessica! River is such a smart leap forward, turning scattered context into instant clarity without the usual Slack/doc slog. This new info architecture feels like the real unlock for scaling teams. Game-changer for productivity! 🚀

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

One of the most fun things I get to do is host amazing people in our Shopify internal podcast (called Context). What do we talk about? Things like this with Tim Urban.
2:12

One of the most fun things I get to do is host amazing people in our Shopify internal podcast (called Context). What do we talk about? Things like this with Tim Urban.

tobi lutke

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

Slack has rolled out a new plugin that allows you to connect to Slack for search, messaging, document creation and more. Use this to get context from Slack into Claude Code so it has context on what you're working on or to post updates.
0:25

Slack has rolled out a new plugin that allows you to connect to Slack for search, messaging, document creation and more. Use this to get context from Slack into Claude Code so it has context on what you're working on or to post updates.

Thariq

141,793 просмотров • 7 месяцев назад

Excited to announce that Bret Taylor is joining the Shopify Board of directors today. We recorded an episode for our internal podcast context a few days ago. But it's fun so I'll share it here.
1:02:31

Excited to announce that Bret Taylor is joining the Shopify Board of directors today. We recorded an episode for our internal podcast context a few days ago. But it's fun so I'll share it here.

tobi lutke

165,099 просмотров • 3 лет назад

The new company brain. Context is the soul of your company, I learned today. Since I wrote a book, “Age of Context,” years ago I see that context is what we now call our private data. That data should be stored in a way to let AI agents and humans get more and more use out of it. This is precisely what PromptQL does and here Tanmai Gopal goes deep on how it now is a company brain, or, rather, a wiki that everyone updates and uses.
49:34

The new company brain. Context is the soul of your company, I learned today. Since I wrote a book, “Age of Context,” years ago I see that context is what we now call our private data. That data should be stored in a way to let AI agents and humans get more and more use out of it. This is precisely what PromptQL does and here Tanmai Gopal goes deep on how it now is a company brain, or, rather, a wiki that everyone updates and uses.

Robert Scoble

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

Giving some more context about #ChristinaAguilera's new residency in #LasVegas. Here's a preview of our longer chat. This and more on our latest show! Listen to The Perez Hilton Podcast with Chris Booker in full at
0:58

Giving some more context about #ChristinaAguilera's new residency in #LasVegas. Here's a preview of our longer chat. This and more on our latest show! Listen to The Perez Hilton Podcast with Chris Booker in full at

Perez

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

Excited today to share with you the next step in the evolution of GM World Our new website features exceptional up-and-coming artists and offers more context on our curation, including the first episode of our new video series: From The Studio
3:58

Excited today to share with you the next step in the evolution of GM World Our new website features exceptional up-and-coming artists and offers more context on our curation, including the first episode of our new video series: From The Studio

BΞN

10,139 просмотров • 3 лет назад

Clip from Context (Shopify internal podcast) with Rousseau Kazi felt worth sharing. We talked about how the role of PM is evolving in a world of vibes and AI. What is changing, and what isn't
4:46

Clip from Context (Shopify internal podcast) with Rousseau Kazi felt worth sharing. We talked about how the role of PM is evolving in a world of vibes and AI. What is changing, and what isn't

tobi lutke

67,942 просмотров • 1 год назад

This is unfortunate, but completely understandable!! It must be hard for people to come across our church without context on these types of things
1:46

This is unfortunate, but completely understandable!! It must be hard for people to come across our church without context on these types of things

Braden

19,551 просмотров • 1 год назад

Context matters for agentic workflows. Robert Smith of Vista Equity: - In a traditional manual workflow environment, evaluating insurance claims in one of our systems would cost ~$8M - When you run the workflow through a general LLM with some systems underlying, the cost comes down to $3-4M - In our proprietary systems the inference cost falls to $200K with a faster, higher fidelity output, because we have the context of what fraud claims are through our insurance platform
1:13

Context matters for agentic workflows. Robert Smith of Vista Equity: - In a traditional manual workflow environment, evaluating insurance claims in one of our systems would cost ~$8M - When you run the workflow through a general LLM with some systems underlying, the cost comes down to $3-4M - In our proprietary systems the inference cost falls to $200K with a faster, higher fidelity output, because we have the context of what fraud claims are through our insurance platform

SouthernValue

24,797 просмотров • 4 месяцев назад

🚨On the next episode of the Context Podcast: “Our readiness has never been put to question throughout our 23 years of existence. We have always been united for a collective purpose” East Africa Standby Force Director, Brigadier General Ronald Rwivanga, discusses the organisation’s mandate, readiness to serve and more on the Context Podcast.
1:26

🚨On the next episode of the Context Podcast: “Our readiness has never been put to question throughout our 23 years of existence. We have always been united for a collective purpose” East Africa Standby Force Director, Brigadier General Ronald Rwivanga, discusses the organisation’s mandate, readiness to serve and more on the Context Podcast.

The New Times (Rwanda)

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

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.
0:22

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

🚨 JUST NOW — KEVIN O'LEARY ON THE STRAIT OF HORMUZ: "When we get out of this thing, I guarantee you there will be a new policy on keeping that two miles stretch open in perpetuity no matter what the cost is!" "For the US, costs so far about $11-12 billion. I know it sounds like a lot of money — it's a rounding error in the cost of this thing staying closed to all of our allies that buy our goods and services. You have to put it in context."
1:10

🚨 JUST NOW — KEVIN O'LEARY ON THE STRAIT OF HORMUZ: "When we get out of this thing, I guarantee you there will be a new policy on keeping that two miles stretch open in perpetuity no matter what the cost is!" "For the US, costs so far about $11-12 billion. I know it sounds like a lot of money — it's a rounding error in the cost of this thing staying closed to all of our allies that buy our goods and services. You have to put it in context."

Eric Daugherty

711,907 просмотров • 7 месяцев назад

94% OF ENGINEERING ORGS USE AI. ONLY 6% SCALE IT The missing link is context and governance. That’s exactly what Atlassian is going after with its new agentic engineering stack: Code Context + governed agent loops in Atlassian Jira + DX measurement. The idea is simple: make agents a native part of your engineering system instead of a side quest in a terminal. > Code Context grounds them in your architecture > Governed loops take work from backlog to pull request > DX measures the impact And the data backs up the context thesis: DX found context-rich AI teams shipped ~64% more per developer 👊 A pretty strong signal that context is becoming one of the biggest leverage points in agentic engineering.
1:00

94% OF ENGINEERING ORGS USE AI. ONLY 6% SCALE IT The missing link is context and governance. That’s exactly what Atlassian is going after with its new agentic engineering stack: Code Context + governed agent loops in Atlassian Jira + DX measurement. The idea is simple: make agents a native part of your engineering system instead of a side quest in a terminal. > Code Context grounds them in your architecture > Governed loops take work from backlog to pull request > DX measures the impact And the data backs up the context thesis: DX found context-rich AI teams shipped ~64% more per developer 👊 A pretty strong signal that context is becoming one of the biggest leverage points in agentic engineering.

Charly Wargnier ♨️

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

Your engineering team is about to snap. And your AI coding agent is making it worse. Introducing CodeRabbit Agent for Slack 🎉 A second brain for engineering teams. Because your tribal knowledge lives in Slack threads nobody can find. At CodeRabbit, we review millions of PRs every week and know how ace engineering teams operate on the planet. The same three things slow every team we see: - Context and decisions that live elsewhere. - Lack of a team-level durable knowledge base - And a trust layer that gives a safety net to your teams Built for Agentic SDLC workflows, CodeRabbit Agent for Slack solves all three problems in one shot while enabling teams to collaborate in real-time with the Agent. CodeRabbit Agent is Slack-native and builds your team’s operating context from every thread, every decision, every conversation your team has ever had. Make your team’s context compound!
1:37

Your engineering team is about to snap. And your AI coding agent is making it worse. Introducing CodeRabbit Agent for Slack 🎉 A second brain for engineering teams. Because your tribal knowledge lives in Slack threads nobody can find. At CodeRabbit, we review millions of PRs every week and know how ace engineering teams operate on the planet. The same three things slow every team we see: - Context and decisions that live elsewhere. - Lack of a team-level durable knowledge base - And a trust layer that gives a safety net to your teams Built for Agentic SDLC workflows, CodeRabbit Agent for Slack solves all three problems in one shot while enabling teams to collaborate in real-time with the Agent. CodeRabbit Agent is Slack-native and builds your team’s operating context from every thread, every decision, every conversation your team has ever had. Make your team’s context compound!

Harjot Gill

4,777,968 просмотров • 5 месяцев назад

This is Repo Prompt 1.5 The new Context Builder connects to your agent of choice, using your existing subscriptions, to fully automate the process of building the perfect context for a given token budget. All of Repo Prompt's power, fully automated, with 1 click
2:37

This is Repo Prompt 1.5 The new Context Builder connects to your agent of choice, using your existing subscriptions, to fully automate the process of building the perfect context for a given token budget. All of Repo Prompt's power, fully automated, with 1 click

eric provencher

195,327 просмотров • 1 год назад

Glen is building the organizational learning and context layer for agents. Every agent session your team runs produces reasoning worth keeping, and nearly all of it is discarded the moment the window closes. Glen is the layer that unifies every agent and model your company run. Glen pulls in agent sessions from Claude Code, Codex and Cursor, plus Slack messages, GitHub prs, tickets, docs and calls. When a new agent picks up a task, Glen finds relevant prior context and injects it in the agents context window to steer it, producing knowledge work that is significantly higher quality, faster and cheaper than ever before. 29% less context and 21% faster to be exact. And Glen does more... > query the original agent behind any line of code > search every session your org has ever run > dynamic skill distillation > multiplayer agents > unified transcripts you can hand between Claude Code, Codex, and Cursor mid-task, > a company brain in Slack. Glen is in early access, sign up for the waitlist below.
2:29

Glen is building the organizational learning and context layer for agents. Every agent session your team runs produces reasoning worth keeping, and nearly all of it is discarded the moment the window closes. Glen is the layer that unifies every agent and model your company run. Glen pulls in agent sessions from Claude Code, Codex and Cursor, plus Slack messages, GitHub prs, tickets, docs and calls. When a new agent picks up a task, Glen finds relevant prior context and injects it in the agents context window to steer it, producing knowledge work that is significantly higher quality, faster and cheaper than ever before. 29% less context and 21% faster to be exact. And Glen does more... > query the original agent behind any line of code > search every session your org has ever run > dynamic skill distillation > multiplayer agents > unified transcripts you can hand between Claude Code, Codex, and Cursor mid-task, > a company brain in Slack. Glen is in early access, sign up for the waitlist below.

Nikos

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