Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

herdr 0.7.4 is out! many fixes, many additions, and structural work for multi-client 👀 but this one ships one of the two most wanted features: customizable sidebar. both agent and workspace rows: plugins, custom scripts, agent hooks, or just settings can put anything on them. claude's live task title,...

herdrdev's profile picture

herdr

9,011 subscribers

90,248 görüntüleme • 12 gün önce •via X (Twitter)

Bilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

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,070 görüntüleme • 2 ay önce

Last, but not least, don't sleep on this one: Le Chat now has Work mode (Preview) — a powerful agent for complex long-horizon tasks like research, analysis, and actions across your connected tools. Connectors are on by default so the agent pulls context from docs, email, and calendars as it works, and sessions persist across many turns until the task is complete.
1:03

Last, but not least, don't sleep on this one: Le Chat now has Work mode (Preview) — a powerful agent for complex long-horizon tasks like research, analysis, and actions across your connected tools. Connectors are on by default so the agent pulls context from docs, email, and calendars as it works, and sessions persist across many turns until the task is complete.

Mistral Vibe

32,521 görüntüleme • 2 ay önce

Introducing Agent Wikis! I've been using llm wikis (or knowledge bases) for research and videos for a while to ensure the information I'm providing is always up-to-date and accurate. Now you can access them for free! Just point your agent at to access wikis on many topics, including Hermes Agent, Hyperframes, Google Ads, and llama.cpp. They can be queried through a simple MCP server. Everything has been designed to be agent-friendly and lightweight (no context bloat). This is a beta release, so please let me know of any bugs or issues (I'm sure there are one or two). You can also join the waitlist if you would like us to create and maintain your own private wiki, or if you are a project owner you can request one for your project to make sure your users (and their agents) don't run into any common issues (and also be featured on the site). Thank you!
0:30

Introducing Agent Wikis! I've been using llm wikis (or knowledge bases) for research and videos for a while to ensure the information I'm providing is always up-to-date and accurate. Now you can access them for free! Just point your agent at to access wikis on many topics, including Hermes Agent, Hyperframes, Google Ads, and llama.cpp. They can be queried through a simple MCP server. Everything has been designed to be agent-friendly and lightweight (no context bloat). This is a beta release, so please let me know of any bugs or issues (I'm sure there are one or two). You can also join the waitlist if you would like us to create and maintain your own private wiki, or if you are a project owner you can request one for your project to make sure your users (and their agents) don't run into any common issues (and also be featured on the site). Thank you!

tonbi

46,993 görüntüleme • 1 ay önce

AT LAST! Custom Status Lines are coming to Codex 🙌 This is just one of many highly requested features in the pipeline. You can now run /statusline to configure exactly what shows in your terminal. Choose from 15 data points, toggle them on/off, or even reorder them. One thing I'd love to see in the future is to be able to install custom extensions that would allow you to customize their styling or run custom scripts (like weather updates). More updates coming soon, but this is the most mature imminent release (0.99 Alpha). Codex team is absolutely cooking.
0:29

AT LAST! Custom Status Lines are coming to Codex 🙌 This is just one of many highly requested features in the pipeline. You can now run /statusline to configure exactly what shows in your terminal. Choose from 15 data points, toggle them on/off, or even reorder them. One thing I'd love to see in the future is to be able to install custom extensions that would allow you to customize their styling or run custom scripts (like weather updates). More updates coming soon, but this is the most mature imminent release (0.99 Alpha). Codex team is absolutely cooking.

am.will

38,786 görüntüleme • 5 ay önce

I built the clipboard I always wanted for working with AI agents. It’s called Bluey and It’s 100% local-first. It lives under your mouse cursor. You can draw on your screen, speak to it, or type what you mean, and Bluey turns all of that into rich context for Claude Code or Codex. I’ve been using it to design websites and debug UI because I can finally say things like “move this here” or “make this section feel cleaner” while pointing at the actual screen. No more writing long explanations. No more manually describing screenshots. No more agents getting lost because they don’t know what “this” or "that" means. You can just point to it, speak or type and it will curate the best possible context for your agents Bluey captures the screenshot, annotation, transcript, app/window context, and the details your agent needs, then sends it directly into your coding session. I am giving it out for free for a while! Im building it with my buddy Omkar Satpute and we would love to hear what you think about it on Discord what context do you wish your agent could understand better?
2:54

I built the clipboard I always wanted for working with AI agents. It’s called Bluey and It’s 100% local-first. It lives under your mouse cursor. You can draw on your screen, speak to it, or type what you mean, and Bluey turns all of that into rich context for Claude Code or Codex. I’ve been using it to design websites and debug UI because I can finally say things like “move this here” or “make this section feel cleaner” while pointing at the actual screen. No more writing long explanations. No more manually describing screenshots. No more agents getting lost because they don’t know what “this” or "that" means. You can just point to it, speak or type and it will curate the best possible context for your agents Bluey captures the screenshot, annotation, transcript, app/window context, and the details your agent needs, then sends it directly into your coding session. I am giving it out for free for a while! Im building it with my buddy Omkar Satpute and we would love to hear what you think about it on Discord what context do you wish your agent could understand better?

Milind S

13,342 görüntüleme • 1 ay önce

New short course: LLMs as Operating Systems: Agent Memory, created with Letta, and taught by its founders Charles Packer and Sarah Wooders. An LLM's input context window has limited space. Using a longer input context also costs more and results in slower processing. So, managing what's stored in this context window is important. In the innovative paper MemGPT: Towards LLMs as Operating Systems, its authors (which include the instructors) proposed using an LLM agent to manage this context window. Their system uses a large persistent memory that stores everything that could be included in the input context, and an agent decides what is actually included. Take the example of building a chatbot that needs to remember what's been said earlier in a conversation (perhaps over many days of interaction with a user). As the conversation's length grows, the memory management agent will move information from the input context to a persistent searchable database; summarize information to keep relevant facts in the input context; and restore relevant conversation elements from further back in time. This allows a chatbot to keep what's currently most relevant in its input context memory to generate the next response. When I read the original MemGPT paper, I thought it was an innovative technique for handling memory for LLMs. The open-source Letta framework, which we'll use in this course, makes MemGPT easy to implement. It adds memory to your LLM agents and gives them transparent long-term memory. In detail, you’ll learn: - How to build an agent that can edit its own limited input context memory, using tools and multi-step reasoning - What is a memory hierarchy (an idea from computer operating systems, which use a cache to speed up memory access), and how these ideas apply to managing the LLM input context (where the input context window is a "cache" storing the most relevant information; and an agent decides what to move in and out of this to/from a larger persistent storage system) - How to implement multi-agent collaboration by letting different agents share blocks of memory This course will give you a sophisticated understanding of memory management for LLMs, which is important for chatbots having long conversations, and for complex agentic workflows. Please sign up here!
2:57

New short course: LLMs as Operating Systems: Agent Memory, created with Letta, and taught by its founders Charles Packer and Sarah Wooders. An LLM's input context window has limited space. Using a longer input context also costs more and results in slower processing. So, managing what's stored in this context window is important. In the innovative paper MemGPT: Towards LLMs as Operating Systems, its authors (which include the instructors) proposed using an LLM agent to manage this context window. Their system uses a large persistent memory that stores everything that could be included in the input context, and an agent decides what is actually included. Take the example of building a chatbot that needs to remember what's been said earlier in a conversation (perhaps over many days of interaction with a user). As the conversation's length grows, the memory management agent will move information from the input context to a persistent searchable database; summarize information to keep relevant facts in the input context; and restore relevant conversation elements from further back in time. This allows a chatbot to keep what's currently most relevant in its input context memory to generate the next response. When I read the original MemGPT paper, I thought it was an innovative technique for handling memory for LLMs. The open-source Letta framework, which we'll use in this course, makes MemGPT easy to implement. It adds memory to your LLM agents and gives them transparent long-term memory. In detail, you’ll learn: - How to build an agent that can edit its own limited input context memory, using tools and multi-step reasoning - What is a memory hierarchy (an idea from computer operating systems, which use a cache to speed up memory access), and how these ideas apply to managing the LLM input context (where the input context window is a "cache" storing the most relevant information; and an agent decides what to move in and out of this to/from a larger persistent storage system) - How to implement multi-agent collaboration by letting different agents share blocks of memory This course will give you a sophisticated understanding of memory management for LLMs, which is important for chatbots having long conversations, and for complex agentic workflows. Please sign up here!

Andrew Ng

200,788 görüntüleme • 1 yıl önce

New course: Spec-Driven Development with Coding Agents, built in partnership with JetBrains, and taught by Paul Everitt | @pauleveritt@fosstodon.org. Vibe coding is fast, but often produces code that doesn't match what you asked for. This short course teaches you spec-driven development: write a detailed spec defining what to build, and work with your coding agent to implement it. Many of the best developers already build this way. A spec lets you control large code changes with a few words, preserve context across agent sessions, and stay in control as your project grows in complexity. Skills you'll gain: - Write a detailed specification to define your mission, tech stack, and roadmap, giving your agent the context it needs from the start - Plan, implement, and validate features in iterative loops using a spec as your agent's guide - Apply the same repeatable workflow to both new and legacy codebases - Package your workflow into a portable agent skill that works across agents and IDEs Join and write specs that keep your coding agent on track!
2:51

New course: Spec-Driven Development with Coding Agents, built in partnership with JetBrains, and taught by Paul Everitt | @[email protected]. Vibe coding is fast, but often produces code that doesn't match what you asked for. This short course teaches you spec-driven development: write a detailed spec defining what to build, and work with your coding agent to implement it. Many of the best developers already build this way. A spec lets you control large code changes with a few words, preserve context across agent sessions, and stay in control as your project grows in complexity. Skills you'll gain: - Write a detailed specification to define your mission, tech stack, and roadmap, giving your agent the context it needs from the start - Plan, implement, and validate features in iterative loops using a spec as your agent's guide - Apply the same repeatable workflow to both new and legacy codebases - Package your workflow into a portable agent skill that works across agents and IDEs Join and write specs that keep your coding agent on track!

Andrew Ng

460,630 görüntüleme • 3 ay önce

Make your CLI 10x more powerful with custom subagents! Mistral Vibe is an open-source coding agent that runs in your terminal. Most terminal agents give you one assistant that does everything. With Vibe, you can build custom subagents for targeted tasks like deploy scripts, PR reviews, and test generation, then invoke them on demand. Here's how it works: Each subagent runs independently and handles its job without cluttering your main workflow. You might have one for PR reviews, another for testing, and another for deployment. The agent also has full access to your codebase. It scans your project structure and Git status automatically, so it understands context across multiple files, not just the one you're editing. Key capabilities: • Web search and fetching - query and fetch content from the web mid-session for documentation, or API references. • Multi-choice clarifications - when your instruction is ambiguous, Vibe prompts with options instead of guessing. You pick the right path before it acts. • Full skills support - slash commands for preconfigured workflows, custom subagents for specialized tasks, and extensibility through the Agent Skills standard. Vibe works in your terminal or connects to VS Code, JetBrains, and Zed through the Agent Client Protocol. Mistral Vibe is available through Le Chat Pro and Team plans. It's 100% open source Link to Mistral Vibe in the comments!
0:20

Make your CLI 10x more powerful with custom subagents! Mistral Vibe is an open-source coding agent that runs in your terminal. Most terminal agents give you one assistant that does everything. With Vibe, you can build custom subagents for targeted tasks like deploy scripts, PR reviews, and test generation, then invoke them on demand. Here's how it works: Each subagent runs independently and handles its job without cluttering your main workflow. You might have one for PR reviews, another for testing, and another for deployment. The agent also has full access to your codebase. It scans your project structure and Git status automatically, so it understands context across multiple files, not just the one you're editing. Key capabilities: • Web search and fetching - query and fetch content from the web mid-session for documentation, or API references. • Multi-choice clarifications - when your instruction is ambiguous, Vibe prompts with options instead of guessing. You pick the right path before it acts. • Full skills support - slash commands for preconfigured workflows, custom subagents for specialized tasks, and extensibility through the Agent Skills standard. Vibe works in your terminal or connects to VS Code, JetBrains, and Zed through the Agent Client Protocol. Mistral Vibe is available through Le Chat Pro and Team plans. It's 100% open source Link to Mistral Vibe in the comments!

Sumanth

10,483 görüntüleme • 4 ay önce

$FET just quietly built the internet for AI agents. 3,000,000 agents. One network. One token. Here's what nobody is explaining: Every AI agent needs 3 things to be useful: An address. A way to be found. A way to get paid. Agentverse gives agents all three. Your agent becomes discoverable on ASI: One. Other agents can find it, call it, or hire it. Automatically. No human in the loop. This is agent-to-agent commerce. And every transaction settles in $FET. More agents = more activity = more demand. The infrastructure is already live. The economy is just getting started.
1:00

$FET just quietly built the internet for AI agents. 3,000,000 agents. One network. One token. Here's what nobody is explaining: Every AI agent needs 3 things to be useful: An address. A way to be found. A way to get paid. Agentverse gives agents all three. Your agent becomes discoverable on ASI: One. Other agents can find it, call it, or hire it. Automatically. No human in the loop. This is agent-to-agent commerce. And every transaction settles in $FET. More agents = more activity = more demand. The infrastructure is already live. The economy is just getting started.

2xnmore

12,894 görüntüleme • 3 ay önce

We just did two days' worth of research in... two clicks 🫠☢️ Now even our VA gets an extended holiday 🏖️ This is a database of 450 AI Agents you can use today (engage and I'll send) While it had a one-liner Description, we wanted more thorough info on their Capabilities - a feature list (for something BIG coming soon 🤫) Otto did that for all 450 rows... in two clicks. Scraped the websites and GitHubs of each. Each cell is its own Agent. Using Agents to discover Agents
0:33

We just did two days' worth of research in... two clicks 🫠☢️ Now even our VA gets an extended holiday 🏖️ This is a database of 450 AI Agents you can use today (engage and I'll send) While it had a one-liner Description, we wanted more thorough info on their Capabilities - a feature list (for something BIG coming soon 🤫) Otto did that for all 450 rows... in two clicks. Scraped the websites and GitHubs of each. Each cell is its own Agent. Using Agents to discover Agents

Howard Gil

41,331 görüntüleme • 1 yıl önce

I built something I believe is useful for agentic coding today. I’ve been too worried it’s not the best it can be, but my wife encouraged me to fail fast if I was worried about failure, so here we are. Introducing Kontinuo by Pull Base, the continuity layer for your AI coding agents. You’re mid-task, you hit a rate limit on Claude, and you want to keep going on Codex or Cursor. But the next agent has no idea what just happened. Kontinuo fixes that, it leaves a verifiable context log the next agent can actually use and it’s really token efficient. Check it out: Use it, break it. I hope it’s useful to at least one person.
1:00

I built something I believe is useful for agentic coding today. I’ve been too worried it’s not the best it can be, but my wife encouraged me to fail fast if I was worried about failure, so here we are. Introducing Kontinuo by Pull Base, the continuity layer for your AI coding agents. You’re mid-task, you hit a rate limit on Claude, and you want to keep going on Codex or Cursor. But the next agent has no idea what just happened. Kontinuo fixes that, it leaves a verifiable context log the next agent can actually use and it’s really token efficient. Check it out: Use it, break it. I hope it’s useful to at least one person.

Big Sheddy 🦅

50,565 görüntüleme • 1 ay önce

Database table size impacts performance in more ways than one: a) B-tree depth. Using 8k pages and a 16b uuid: 1 level = ~370 rows 2 levels = ~138k rows 3 levels = ~50m rows 4 levels = ~20b rows The lookup cost on a table with 100k rows is not the same as one with 1b rows. This can apply both to the table itself (MySQL cluster index) as well as the indexes. Sometimes a single query requires many of them. b) Small table → fits in RAM → fast reads. The larger the table, the more likely to read from disk plus churn the cache. c) # of indexes. Each adds maintenance overhead for insertions, and for Postgres vacuum overhead as well. Keep an eye on this! It's useful to take regular stock of your tables + indexes. Clean bloat. Remove unused indexes. Partition if needed.
0:58

Database table size impacts performance in more ways than one: a) B-tree depth. Using 8k pages and a 16b uuid: 1 level = ~370 rows 2 levels = ~138k rows 3 levels = ~50m rows 4 levels = ~20b rows The lookup cost on a table with 100k rows is not the same as one with 1b rows. This can apply both to the table itself (MySQL cluster index) as well as the indexes. Sometimes a single query requires many of them. b) Small table → fits in RAM → fast reads. The larger the table, the more likely to read from disk plus churn the cache. c) # of indexes. Each adds maintenance overhead for insertions, and for Postgres vacuum overhead as well. Keep an eye on this! It's useful to take regular stock of your tables + indexes. Clean bloat. Remove unused indexes. Partition if needed.

Ben Dicken

212,291 görüntüleme • 3 ay önce

Look ma new Codex Updates! 0.119.0 and 0.120.0 are here. And with it, a HUGE number of quality of life updates and bug fixes! > Hooks now render in a dedicated live area above the composer. They only persist when they have output, so your terminal stays clean. If you're running PreToolUse or PostToolUse hooks, this is a huge readability win. > Hooks are now available again on Windows > CTRL+O copies the last agent output. Small but clutch when you're pulling a code block into another file or chat. > New statusline option: context usage as a graphical bar instead of a percentage. Easier to glance at mid-session when you're trying to gauge how much runway you have left. > Zellij support is here with no scrollback bugs. If you've been stuck on tmux just because Codex was broken in Zellij, you're free now (shout out Felipe Coury 🦀) > Memory extensions just landed. The consolidation agent can now discover plugin folders under memories_extensions/ and read their instructions.md to learn how to interpret new memory sources. Drop a folder in, give it guidance, and the agent picks it up automatically during summarization. No core code changes needed. This is the first real extension point for Codex's memory system, and it opens the door for third-party memory plugins. > Did you know, you can /rename a thread? But what's really cool about that is, after you rename it, you can resume it with the same name, no more UUIDs. codex resume mynewapp or directly from the TUI: /resume mynewapp > Multi agents v2 got an update to tool descriptions More reliable multi agent environments and inter agent communication > You can now enable TUI notifications whether Codex is in focus or not. Modify this in your config: [tui] notification_condition = "always" > MAJOR overhaul to Codex MCP functionality: 1. Codex Tool Search now works with custom MCP servers, so tools can be searched and deferred instead of all being exposed up front. 2. Custom MCP servers can now trigger elicitations, meaning they can stop and ask for user approval or input mid-flow. 3. MCP tool results now preserve richer metadata, which improves app/UI handoff behavior. 4. Codex can now read MCP resources directly, letting apps return resource URIs that the client can actually open. 5. File params for Codex Apps are smoother: local file paths can be uploaded and remapped automatically. 6. Plugin cache refresh and fallback sync behavior are more reliable, especially for custom and curated plugins. > Composer and chat behavior smoother overall, resize bugs remain though. > Realtime v2 got several significant improvements as well. > You're still reading? What a legend. 🫶 npm i -g @openai/codex to update
0:36

Look ma new Codex Updates! 0.119.0 and 0.120.0 are here. And with it, a HUGE number of quality of life updates and bug fixes! > Hooks now render in a dedicated live area above the composer. They only persist when they have output, so your terminal stays clean. If you're running PreToolUse or PostToolUse hooks, this is a huge readability win. > Hooks are now available again on Windows > CTRL+O copies the last agent output. Small but clutch when you're pulling a code block into another file or chat. > New statusline option: context usage as a graphical bar instead of a percentage. Easier to glance at mid-session when you're trying to gauge how much runway you have left. > Zellij support is here with no scrollback bugs. If you've been stuck on tmux just because Codex was broken in Zellij, you're free now (shout out Felipe Coury 🦀) > Memory extensions just landed. The consolidation agent can now discover plugin folders under memories_extensions/ and read their instructions.md to learn how to interpret new memory sources. Drop a folder in, give it guidance, and the agent picks it up automatically during summarization. No core code changes needed. This is the first real extension point for Codex's memory system, and it opens the door for third-party memory plugins. > Did you know, you can /rename a thread? But what's really cool about that is, after you rename it, you can resume it with the same name, no more UUIDs. codex resume mynewapp or directly from the TUI: /resume mynewapp > Multi agents v2 got an update to tool descriptions More reliable multi agent environments and inter agent communication > You can now enable TUI notifications whether Codex is in focus or not. Modify this in your config: [tui] notification_condition = "always" > MAJOR overhaul to Codex MCP functionality: 1. Codex Tool Search now works with custom MCP servers, so tools can be searched and deferred instead of all being exposed up front. 2. Custom MCP servers can now trigger elicitations, meaning they can stop and ask for user approval or input mid-flow. 3. MCP tool results now preserve richer metadata, which improves app/UI handoff behavior. 4. Codex can now read MCP resources directly, letting apps return resource URIs that the client can actually open. 5. File params for Codex Apps are smoother: local file paths can be uploaded and remapped automatically. 6. Plugin cache refresh and fallback sync behavior are more reliable, especially for custom and curated plugins. > Composer and chat behavior smoother overall, resize bugs remain though. > Realtime v2 got several significant improvements as well. > You're still reading? What a legend. 🫶 npm i -g @openai/codex to update

am.will

742,199 görüntüleme • 3 ay önce

New course: Build agents that respond to users with not only plaintext, but custom UIs like charts, forms, and whiteboards, generated on demand and displayed right in the chat. This short course is built in partnership with CopilotKit🪁 and taught by Atai Barkai, co-founder of CopilotKit. You'll learn three approaches: Your agent can pick from custom components you build, like charts and forms. It can compose new layouts from a set of building blocks you provide, like rows, cards, and text. Or it can incorporate existing third-party apps, like a whiteboard or a calendar, right inside the conversation. Skills you’ll gain: - Build agents that render custom components like charts and forms on demand - Build an app where the agent and user collaborate on shared data, beyond just the chat window - Place third-party apps like maps, calendars, and whiteboards right in your interface Join and build agents that give users something to see and act on!
1:42

New course: Build agents that respond to users with not only plaintext, but custom UIs like charts, forms, and whiteboards, generated on demand and displayed right in the chat. This short course is built in partnership with CopilotKit🪁 and taught by Atai Barkai, co-founder of CopilotKit. You'll learn three approaches: Your agent can pick from custom components you build, like charts and forms. It can compose new layouts from a set of building blocks you provide, like rows, cards, and text. Or it can incorporate existing third-party apps, like a whiteboard or a calendar, right inside the conversation. Skills you’ll gain: - Build agents that render custom components like charts and forms on demand - Build an app where the agent and user collaborate on shared data, beyond just the chat window - Place third-party apps like maps, calendars, and whiteboards right in your interface Join and build agents that give users something to see and act on!

Andrew Ng

210,657 görüntüleme • 2 ay önce

Notion 3.0 with Agents is out today! It's the first Knowledge Work Agent in the world. It works with Notion databases. It can do multi-step actions and autonomous work up to 20+ mins, and a brand-new memory system (using Notion pages and databases! 👌) With 3.0, Notion isn’t just your tool — it’s your teammate that works while you sleep. Two types of agents: Personal Agent: Can do anything you can do in Notion. Remembers and learns your preferences as you work. Has a little personality (accessories like a duck hat 🦆.) Custom Agents (early access): Spin up a small team. Hand them the repetitive stuff. They work while you sleep! And Notion Agents work across Notion Calendar, Notion Mail, plus MCP and more. Available today! Try it. Tell us what’s missing. We’ll keep shipping, so you can focus on your life’s work 🫡
2:03

Notion 3.0 with Agents is out today! It's the first Knowledge Work Agent in the world. It works with Notion databases. It can do multi-step actions and autonomous work up to 20+ mins, and a brand-new memory system (using Notion pages and databases! 👌) With 3.0, Notion isn’t just your tool — it’s your teammate that works while you sleep. Two types of agents: Personal Agent: Can do anything you can do in Notion. Remembers and learns your preferences as you work. Has a little personality (accessories like a duck hat 🦆.) Custom Agents (early access): Spin up a small team. Hand them the repetitive stuff. They work while you sleep! And Notion Agents work across Notion Calendar, Notion Mail, plus MCP and more. Available today! Try it. Tell us what’s missing. We’ll keep shipping, so you can focus on your life’s work 🫡

Ivan Zhao

201,111 görüntüleme • 10 ay önce

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:
1:21

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

42,501 görüntüleme • 1 ay önce

Most AI agents are just toys that live in a chat box. They are high on hype, low on utility. You spend more time prompting them than doing actual work. Notion Agent is different. It’s not just a window into an LLM. It’s a layer of intelligence sitting directly on any page on Notion. Check out the attached video. I just asked Notion Agent to write practical examples of each React Hook. Here’s how Notion Agent is helping me build it. • Notion Agent forms a plan: (Search → Read → Decide → Update → Notify). You give it a goal, and it executes multi-step workflows like editing hundreds of pages or updating complex databases. • It can create pages, customize properties, and build entire database views from scratch. • Total Context: It doesn't just search Notion. It pulls from Slack, Google Drive, and the web. It finds the patterns across your entire stack in seconds. Check out Notion Agent here: Appreciate the Notion team for collaborating with me on this deep dive.
0:47

Most AI agents are just toys that live in a chat box. They are high on hype, low on utility. You spend more time prompting them than doing actual work. Notion Agent is different. It’s not just a window into an LLM. It’s a layer of intelligence sitting directly on any page on Notion. Check out the attached video. I just asked Notion Agent to write practical examples of each React Hook. Here’s how Notion Agent is helping me build it. • Notion Agent forms a plan: (Search → Read → Decide → Update → Notify). You give it a goal, and it executes multi-step workflows like editing hundreds of pages or updating complex databases. • It can create pages, customize properties, and build entire database views from scratch. • Total Context: It doesn't just search Notion. It pulls from Slack, Google Drive, and the web. It finds the patterns across your entire stack in seconds. Check out Notion Agent here: Appreciate the Notion team for collaborating with me on this deep dive.

Pratham

20,933 görüntüleme • 5 ay önce

Just watched a demo of Merge Agent Handler and this actually looks pretty useful if you’re building AI agents. Most agents can generate responses, but getting them to actually take actions across real tools is still messy. Integrations are one thing, but handling auth, permissions, and security usually makes it way more complicated than it should be. What I liked is that it feels built for real workflows — you can actually see what your agent is doing instead of just hoping it works. Feels like a practical layer between AI agents and real work getting done. Worth checking out:
0:35

Just watched a demo of Merge Agent Handler and this actually looks pretty useful if you’re building AI agents. Most agents can generate responses, but getting them to actually take actions across real tools is still messy. Integrations are one thing, but handling auth, permissions, and security usually makes it way more complicated than it should be. What I liked is that it feels built for real workflows — you can actually see what your agent is doing instead of just hoping it works. Feels like a practical layer between AI agents and real work getting done. Worth checking out:

Kawsar

31,812 görüntüleme • 4 ay önce

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!
44:33

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!

Dan Shipper 📧

145,487 görüntüleme • 1 yıl önce

If you're evaluating AI IDEs this week, here's what getting started with Windsurf looks like (links below): • Download and install from Import any existing IDE settings during onboarding, or start fresh. • Cascade is the agent panel on the right. Chat, generate, edit, run code. @-mention files, symbols, or docs to scope context. • Choose your model - Opus, Codex, SWE, Kimi, GLM and more (Kimi K2.6 is free for the next 2 weeks 👀) • DeepWiki: Cmd+Shift+Click any symbol for an in-depth explanation of what it does. Send it to Cascade with one click. • Codemaps: hierarchical view of how files and functions execute together. Click a node to jump to code. Shareable as links. • Devin in Windsurf: start and manage cloud sessions without leaving the editor. • Agent Command Center: Kanban board of every running agent, local (Cascade) and cloud (Devin). See what's in flight, blocked, or ready for review. • Spaces: group sessions, PRs, files, and context for one task or project into a single view. • Centralized review: handle diffs, PRs, and agent output in one place. • MCP servers, Memories, and Workflows extend Cascade. Set them up once; reuse across projects.
0:41

If you're evaluating AI IDEs this week, here's what getting started with Windsurf looks like (links below): • Download and install from Import any existing IDE settings during onboarding, or start fresh. • Cascade is the agent panel on the right. Chat, generate, edit, run code. @-mention files, symbols, or docs to scope context. • Choose your model - Opus, Codex, SWE, Kimi, GLM and more (Kimi K2.6 is free for the next 2 weeks 👀) • DeepWiki: Cmd+Shift+Click any symbol for an in-depth explanation of what it does. Send it to Cascade with one click. • Codemaps: hierarchical view of how files and functions execute together. Click a node to jump to code. Shareable as links. • Devin in Windsurf: start and manage cloud sessions without leaving the editor. • Agent Command Center: Kanban board of every running agent, local (Cascade) and cloud (Devin). See what's in flight, blocked, or ready for review. • Spaces: group sessions, PRs, files, and context for one task or project into a single view. • Centralized review: handle diffs, PRs, and agent output in one place. • MCP servers, Memories, and Workflows extend Cascade. Set them up once; reuse across projects.

nader dabit

16,694 görüntüleme • 3 ay önce