Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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

harjotsgill's profile picture

Harjot Gill

3,378 subscribers

4,777,176 Aufrufe • vor 4 Monaten •via X (Twitter)

BildungGesundheit & WellnessWissenschaft & Technologie
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Introducing the supermemory company brain A super employee with all the knowledge of your company, lives in your slack. - Learns how the team works and talks - Works across all your tools - Permission controls built-in for big teams 2 mins to set up. just invite to slack 👇
1:12

Introducing the supermemory company brain A super employee with all the knowledge of your company, lives in your slack. - Learns how the team works and talks - Works across all your tools - Permission controls built-in for big teams 2 mins to set up. just invite to slack 👇

supermemory

617,546 Aufrufe • vor 1 Monat

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

16,328 Aufrufe • vor 20 Tagen

AI agents are powerful. They're also isolated. Switch fixes that. Here's the thing about most AI agents: they work alone. They don't see what your team is discussing. They don't share context across conversations. Every new chat is a fresh start. If you've ever tried to actually integrate an agent into your team's workflow, you know the friction. Then I found 𝗦𝘄𝗶𝘁𝗰𝗵. It brings AI agents into Slack, Teams, Discord, and Telegram as named participants. They sit in the same rooms as your team, with the same context, history, and participants. What I actually like about it: → Agents join as real participants in channels — not bots you have to Mention every time → Each room carries its own context, history, and rules → Works with Claude Code, OpenAI, LangChain, Google ADK, and custom agents → Open source and self-hostable. Running in minutes. No migration. No lock-in. Just agents where your team already works. Knowledge lives in the room, not in the agent. Switch keeps people, agents, decisions, and work history together so context survives handoffs. It's from Flint AI. Open source. Runs in minutes. 👉 Human + agent teams, actually working together. 📌 Download 𝗦𝘄𝗶𝘁𝗰𝗵 Console → 🚀𝗦𝘄𝗶𝘁𝗰𝗵 is live on Product Hunt: 🔄 Repost if you've ever wished your AI agent could just join the Slack channel. — #AI #Agents #Slack #Teams #Switch #ProductHunt
0:22

AI agents are powerful. They're also isolated. Switch fixes that. Here's the thing about most AI agents: they work alone. They don't see what your team is discussing. They don't share context across conversations. Every new chat is a fresh start. If you've ever tried to actually integrate an agent into your team's workflow, you know the friction. Then I found 𝗦𝘄𝗶𝘁𝗰𝗵. It brings AI agents into Slack, Teams, Discord, and Telegram as named participants. They sit in the same rooms as your team, with the same context, history, and participants. What I actually like about it: → Agents join as real participants in channels — not bots you have to Mention every time → Each room carries its own context, history, and rules → Works with Claude Code, OpenAI, LangChain, Google ADK, and custom agents → Open source and self-hostable. Running in minutes. No migration. No lock-in. Just agents where your team already works. Knowledge lives in the room, not in the agent. Switch keeps people, agents, decisions, and work history together so context survives handoffs. It's from Flint AI. Open source. Runs in minutes. 👉 Human + agent teams, actually working together. 📌 Download 𝗦𝘄𝗶𝘁𝗰𝗵 Console → 🚀𝗦𝘄𝗶𝘁𝗰𝗵 is live on Product Hunt: 🔄 Repost if you've ever wished your AI agent could just join the Slack channel. — #AI #Agents #Slack #Teams #Switch #ProductHunt

Anuj

54,451 Aufrufe • vor 1 Tag

Now building is a team sport. Introducing Slack Code: a new way for your team and AI agents, like Anthropic's Claude Code, Claude Tag, Devin from Cognition, GitHub Copilot, ChatGPT, and Vercel agents, to write, review, and ship code together. Just mention an agent to spin up a channel, pull in your team, and start building. All in the open. All in Slack.
0:21

Now building is a team sport. Introducing Slack Code: a new way for your team and AI agents, like Anthropic's Claude Code, Claude Tag, Devin from Cognition, GitHub Copilot, ChatGPT, and Vercel agents, to write, review, and ship code together. Just mention an agent to spin up a channel, pull in your team, and start building. All in the open. All in Slack.

Slack

586,276 Aufrufe • vor 21 Tagen

This is one of those abstractions that makes perfect sense once you see it. Write your AI agent once. Run it across Slack, Microsoft Teams, and every messaging platform that follows. That's exactly what CopilotKit's open-source Channels SDK does for any AG-UI agent. Instead of maintaining separate bots for every platform, you connect your agent once and let the SDK handle the channel-specific integration.
1:21

This is one of those abstractions that makes perfect sense once you see it. Write your AI agent once. Run it across Slack, Microsoft Teams, and every messaging platform that follows. That's exactly what CopilotKit's open-source Channels SDK does for any AG-UI agent. Instead of maintaining separate bots for every platform, you connect your agent once and let the SDK handle the channel-specific integration.

Pratham

16,216 Aufrufe • vor 1 Monat

today we introduce a beta of Krea in Slack. expand your team’s creative work with the latest AI models and an agent that adapts to your preferences. try it now at krea . ai
0:39

today we introduce a beta of Krea in Slack. expand your team’s creative work with the latest AI models and an agent that adapts to your preferences. try it now at krea . ai

Krea

17,140 Aufrufe • vor 1 Monat

Hermes Agent released v0.14, and it just made every other AI agent framework feel small. It now drives your computer. Searches X natively. Joins your Microsoft Teams calls. AND runs Grok with a 1M context window. (and for my crypto bro HyperLiquid) The AI agent era is crazy and beautiful.
3:07

Hermes Agent released v0.14, and it just made every other AI agent framework feel small. It now drives your computer. Searches X natively. Joins your Microsoft Teams calls. AND runs Grok with a 1M context window. (and for my crypto bro HyperLiquid) The AI agent era is crazy and beautiful.

Antoine Rousseaux

24,505 Aufrufe • vor 3 Monaten

Engineering teams require focus now more than ever. We’ve changed the way we solve for paper cuts in the product while maintaining our speed of shipping: "The second [a bug] comes through Slack it triggers an agent that figures out the right team to send it to. That team’s custom agent will then do a first pass at a task on Claude. We’ll find similar customer feedback bugs if they exist and then tag an on call engineer where they just review a bunch of PRs” - Sarah Sachs
1:16

Engineering teams require focus now more than ever. We’ve changed the way we solve for paper cuts in the product while maintaining our speed of shipping: "The second [a bug] comes through Slack it triggers an agent that figures out the right team to send it to. That team’s custom agent will then do a first pass at a task on Claude. We’ll find similar customer feedback bugs if they exist and then tag an on call engineer where they just review a bunch of PRs” - Sarah Sachs

Notion Developers

15,009 Aufrufe • vor 2 Monaten

Most AI agents stop at chat. Agent Max is built for what comes after. Max tools. Max control and configurability. Max production readiness. Your agent can use: • any tools, APIs, MCP, and workflows • built-in knowledge: docs/website • multi-model: OpenAI, Claude, Gemini... • agent-to-agent handoffs • human-in-the-loop • logs, usage tracking, environments, and RBAC • enterprise controls for SOC2/GDPR/HIPAA/ISO needs • hosted chat UI, API, Skill in agents, Slack, WhatsApp, Teams, Voice, and more Agent Max is live now in BuildShip for everyone. Give it a try, or comment/DM to book a demo if you want help setting up your first agent.
1:15

Most AI agents stop at chat. Agent Max is built for what comes after. Max tools. Max control and configurability. Max production readiness. Your agent can use: • any tools, APIs, MCP, and workflows • built-in knowledge: docs/website • multi-model: OpenAI, Claude, Gemini... • agent-to-agent handoffs • human-in-the-loop • logs, usage tracking, environments, and RBAC • enterprise controls for SOC2/GDPR/HIPAA/ISO needs • hosted chat UI, API, Skill in agents, Slack, WhatsApp, Teams, Voice, and more Agent Max is live now in BuildShip for everyone. Give it a try, or comment/DM to book a demo if you want help setting up your first agent.

BuildShip

75,946 Aufrufe • vor 2 Monaten

Introducing Claude agents in Notion. Your task board is Claude’s to-do list. Anthropic runs the model and the agent harness. Notion is the orchestration layer: context, UI, and a shared place for teams to review and ship, and kick off Claude workflows. Join the waitlist:
1:27

Introducing Claude agents in Notion. Your task board is Claude’s to-do list. Anthropic runs the model and the agent harness. Notion is the orchestration layer: context, UI, and a shared place for teams to review and ship, and kick off Claude workflows. Join the waitlist:

Notion

495,237 Aufrufe • vor 5 Monaten

Introducing Hamster 🐹 Multiplayer AI for product teams. Hunch in, PR out. Design, engineering, product, & business reason on the same work, and your agents deliver it. Your team makes a hundred decisions a week. Now your AI remembers all of them.
1:27

Introducing Hamster 🐹 Multiplayer AI for product teams. Hunch in, PR out. Design, engineering, product, & business reason on the same work, and your agents deliver it. Your team makes a hundred decisions a week. Now your AI remembers all of them.

Hamster

527,325 Aufrufe • vor 3 Monaten

this is hands down the fastest way to make everyone on your team better with AI: build a shared Company Brain. your best prompts, decisions, corrections, and workflows become the default for every person and AI agent. Claude, Cursor, Codex, and every teammate start from the same playbook. one person learns something once. the whole company gets smarter. the full guide to building your own Company Brain is below:
0:39

this is hands down the fastest way to make everyone on your team better with AI: build a shared Company Brain. your best prompts, decisions, corrections, and workflows become the default for every person and AI agent. Claude, Cursor, Codex, and every teammate start from the same playbook. one person learns something once. the whole company gets smarter. the full guide to building your own Company Brain is below:

J.B.

350,435 Aufrufe • vor 15 Tagen

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.
8:17

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.

The Startup Ideas Podcast (SIP) 🧃

13,598 Aufrufe • vor 2 Monaten

Introducing LangSmith Fleet: an enterprise workspace for creating, using, and managing your fleet of agents. Fleet agents have their own memory, access to a collection of tools and skills, and can be exposed through the communication channels your team uses every day. Fleet includes: → Agent identity and credential management with “Claws” and “Assistants” → Sharing and permissions to control who can run, clone, and edit (just like Google Docs) → Custom Slack bots so each agent has its own identity in Slack Try Fleet: Read the announcement:
1:57

Introducing LangSmith Fleet: an enterprise workspace for creating, using, and managing your fleet of agents. Fleet agents have their own memory, access to a collection of tools and skills, and can be exposed through the communication channels your team uses every day. Fleet includes: → Agent identity and credential management with “Claws” and “Assistants” → Sharing and permissions to control who can run, clone, and edit (just like Google Docs) → Custom Slack bots so each agent has its own identity in Slack Try Fleet: Read the announcement:

LangChain

149,020 Aufrufe • vor 5 Monaten

Another blow to Anthropic! They spent months building what's now fully open-source. Anthropic recently put Claude inside Slack, where you can tag it in a channel. It reads the thread, breaks the task into steps, and posts the result back. The problem is that it only runs Claude and only in the channels Anthropic supports. Running your own agent there is harder. The reasoning, tool calls, and state management are mostly handled by the framework. Connecting that agent to a messaging platform is not. Moreover, each platform has a different integration: - Slack renders messages with Block Kit - Teams uses Adaptive Cards - and each has its own SDK, auth flow, and delivery model. If an agent needs to run on three platforms, one must write three separate integrations against the same agent logic. That overhead explains why most custom agents never get deployed to Slack, and why the ones that do are usually a single vendor's hosted assistant. The alternative is to keep the agent in one place and add a per-platform adapter that translates its output into each platform's native format. The agent is written once, and each channel requires just another output target instead of a separate build. CopilotKit open-sourced this full implementation in the Channels SDK. Essentially, any agent that implements AG-UI can run in a messaging platform in a few lines of code, like Slack, Teams, Discord, WhatsApp, and many more. Because the agent runs inside the thread, it has that conversation's context, so it can summarize the discussion, open a ticket, or route to the right person. It works with any backend, so LangGraph, CrewAI, Mastra, Google ADK, or a plain HTTP agent can connect through an existing endpoint. The same message can render as a Block Kit in Slack and as Adaptive Cards in Teams. In practice, the model and orchestration stay the same; it requires no migration or rewrite. It also handles human-in-the-loop approvals, persistence, and transcripts that carry state across platforms, so a thread started in Teams can continue in Slack. CopilotKit is open-source, and AG-UI is supported across every major agent framework, including LangGraph, CrewAI, Mastra, and Google ADK. Here's the repo: (don't forget to star it ⭐) The agent running in Slack no longer has to be a vendor's. It can be the one you already built. The video below shows this in action. Thanks to CopilotKit for working with me on this launch.
0:30

Another blow to Anthropic! They spent months building what's now fully open-source. Anthropic recently put Claude inside Slack, where you can tag it in a channel. It reads the thread, breaks the task into steps, and posts the result back. The problem is that it only runs Claude and only in the channels Anthropic supports. Running your own agent there is harder. The reasoning, tool calls, and state management are mostly handled by the framework. Connecting that agent to a messaging platform is not. Moreover, each platform has a different integration: - Slack renders messages with Block Kit - Teams uses Adaptive Cards - and each has its own SDK, auth flow, and delivery model. If an agent needs to run on three platforms, one must write three separate integrations against the same agent logic. That overhead explains why most custom agents never get deployed to Slack, and why the ones that do are usually a single vendor's hosted assistant. The alternative is to keep the agent in one place and add a per-platform adapter that translates its output into each platform's native format. The agent is written once, and each channel requires just another output target instead of a separate build. CopilotKit open-sourced this full implementation in the Channels SDK. Essentially, any agent that implements AG-UI can run in a messaging platform in a few lines of code, like Slack, Teams, Discord, WhatsApp, and many more. Because the agent runs inside the thread, it has that conversation's context, so it can summarize the discussion, open a ticket, or route to the right person. It works with any backend, so LangGraph, CrewAI, Mastra, Google ADK, or a plain HTTP agent can connect through an existing endpoint. The same message can render as a Block Kit in Slack and as Adaptive Cards in Teams. In practice, the model and orchestration stay the same; it requires no migration or rewrite. It also handles human-in-the-loop approvals, persistence, and transcripts that carry state across platforms, so a thread started in Teams can continue in Slack. CopilotKit is open-source, and AG-UI is supported across every major agent framework, including LangGraph, CrewAI, Mastra, and Google ADK. Here's the repo: (don't forget to star it ⭐) The agent running in Slack no longer has to be a vendor's. It can be the one you already built. The video below shows this in action. Thanks to CopilotKit for working with me on this launch.

Akshay 🚀

243,901 Aufrufe • vor 1 Monat

Introducing Indent, one coworker for your whole company Indent is a single agent that is built to work with every member of your team, simultaneously. Instead of every one setting up their own agents, use Indent to build one together. Try it at
1:26

Introducing Indent, one coworker for your whole company Indent is a single agent that is built to work with every member of your team, simultaneously. Instead of every one setting up their own agents, use Indent to build one together. Try it at

Sashank

367,992 Aufrufe • vor 1 Tag

audit and fix your entire developer docs site in under a minute We built an AI agent with Browserbase and Cerebras that audits your entire docs site > point it at any documentation site > agent goes down the link tree > agent crawls and verifies every page, checks every link, reads every code snippet > agent also compares content to your GitHub repo > returns a full report with suggested fixes and source references The full code and tutorial for how to build this yourself is live now.
1:16

audit and fix your entire developer docs site in under a minute We built an AI agent with Browserbase and Cerebras that audits your entire docs site > point it at any documentation site > agent goes down the link tree > agent crawls and verifies every page, checks every link, reads every code snippet > agent also compares content to your GitHub repo > returns a full report with suggested fixes and source references The full code and tutorial for how to build this yourself is live now.

Sarah Chieng

26,679 Aufrufe • vor 5 Monaten

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 Aufrufe • vor 3 Monaten

Introducing Team Plan, a new self-serve plan for small businesses and teams. Bring 2 to 9 seats together under one pooled credit balance, with shared projects, commenting, agent skills and Agent Connectors. Everything your team needs to build in one place. Get started at the link below.
0:35

Introducing Team Plan, a new self-serve plan for small businesses and teams. Bring 2 to 9 seats together under one pooled credit balance, with shared projects, commenting, agent skills and Agent Connectors. Everything your team needs to build in one place. Get started at the link below.

Runway

18,271 Aufrufe • vor 5 Tagen