Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

The next big thing is Asynchronous Coding Agents. Such Agents change our role as engineers from Conductor (directing one agent at a time) to Orchestrator (defining tasks for a "fleet" of agents working in parallel), for very well-defined tasks with human review. GitHub's Copilot Agent, as covered at #githubuniverse,...

addyosmani's profile picture

Addy Osmani

389,702 subscribers

17,433 görüntüleme • 8 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

Introducing multi-agent orchestration in Oz, with support for Claude Code, Codex and the Warp Agent. Use /orchestrate to delegate complex tasks across a team of agents, locally or in the cloud.
2:17

Introducing multi-agent orchestration in Oz, with support for Claude Code, Codex and the Warp Agent. Use /orchestrate to delegate complex tasks across a team of agents, locally or in the cloud.

Warp

1,192,646 görüntüleme • 1 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

Introducing Helmor The open-source, local-first answer to Conductor. A more refined, faster GUI for orchestrating coding agents. No cloud. One-click import from Conductor. AI made coding faster. Helmor is about finishing the rest of the loop: orchestration, workspaces, review, testing, and merge. We believe the next generation of GUI agent orchestration should be built in the open — by the community.
0:53

Introducing Helmor The open-source, local-first answer to Conductor. A more refined, faster GUI for orchestrating coding agents. No cloud. One-click import from Conductor. AI made coding faster. Helmor is about finishing the rest of the loop: orchestration, workspaces, review, testing, and merge. We believe the next generation of GUI agent orchestration should be built in the open — by the community.

Caspian 東澔

121,013 görüntüleme • 2 ay önce

Cursor for Design? This Claude Code UI workflow is insane And many vibe coders not aware of it: 1. Claude Code can assign parallel tasks to sub agents 2. Integrate with git worktree to create sandbox env This means you can get Claude Code generate 10 design at the same time, fork & iterate 🔁 Design is an explorative process, by leveraging sub agent + parallel task capabilities, many interesting product UX can be built; Also turned this workflow into an open-source IDE extension here:
16:38

Cursor for Design? This Claude Code UI workflow is insane And many vibe coders not aware of it: 1. Claude Code can assign parallel tasks to sub agents 2. Integrate with git worktree to create sandbox env This means you can get Claude Code generate 10 design at the same time, fork & iterate 🔁 Design is an explorative process, by leveraging sub agent + parallel task capabilities, many interesting product UX can be built; Also turned this workflow into an open-source IDE extension here:

Jason Zhou

40,635 görüntüleme • 1 yıl önce

🧲 Meet Magnet — the AI workspace for agentic coding. Build software with Claude Code, Cursor, Codex & co. → Write a ticket → Magnet assembles context → Fires to Claude Code, Deep Research, and other agent sessions in parallel Git worktree sandboxes → PRs appear → Use agents to help you spec, research, and decompose tasks Let your agents cook!
2:12

🧲 Meet Magnet — the AI workspace for agentic coding. Build software with Claude Code, Cursor, Codex & co. → Write a ticket → Magnet assembles context → Fires to Claude Code, Deep Research, and other agent sessions in parallel Git worktree sandboxes → PRs appear → Use agents to help you spec, research, and decompose tasks Let your agents cook!

Nicolae Rusan

16,608 görüntüleme • 11 ay önce

Meet Agent Bake-Off: blind side by side tests for coding agents like Claude Code, Cursor , Amp , Factory , Codex, & more. We've been building the largest real world benchmarks for coding agents, and we're excited share an early preview of our open community tooling.
1:37

Meet Agent Bake-Off: blind side by side tests for coding agents like Claude Code, Cursor , Amp , Factory , Codex, & more. We've been building the largest real world benchmarks for coding agents, and we're excited share an early preview of our open community tooling.

brexton

18,173 görüntüleme • 8 ay önce

I am hooked on Dynamic Workflows! The idea of generating harnesses on the fly is so compelling that I reverse-engineered it for my agent orchestrator. And then I built a monitoring dashboard (as an HTML artifact) to track tasks, metrics, and reports. I can now use and monitor dynamic workflows in my agent orchestrator with coding agents like Claude Code, Codex, Pi, and even my own custom-built DAIR.AI agent. This is clearly the future of working with agents to accomplish complex, long-running tasks. Some use cases I'm having success with: - Branching deep research tasks (with verification) - Parallel deep research tasks - Session mining of all my agent sessions - Bug hunting - Triaging - Fact-checking - LLM councils - AI simulations - Data synthesis - Evals generation ... and many others Dynamic workflows, like agent skills, feel like an important primitive to not only get the most out of agents but also incorporate dynamic behaviors and important components like cooperation and verification. There is so much exploration ground here. The exciting part is that this is not limited to coding tasks; it extends to business use cases and many other technical domains like science and research.
0:25

I am hooked on Dynamic Workflows! The idea of generating harnesses on the fly is so compelling that I reverse-engineered it for my agent orchestrator. And then I built a monitoring dashboard (as an HTML artifact) to track tasks, metrics, and reports. I can now use and monitor dynamic workflows in my agent orchestrator with coding agents like Claude Code, Codex, Pi, and even my own custom-built DAIR.AI agent. This is clearly the future of working with agents to accomplish complex, long-running tasks. Some use cases I'm having success with: - Branching deep research tasks (with verification) - Parallel deep research tasks - Session mining of all my agent sessions - Bug hunting - Triaging - Fact-checking - LLM councils - AI simulations - Data synthesis - Evals generation ... and many others Dynamic workflows, like agent skills, feel like an important primitive to not only get the most out of agents but also incorporate dynamic behaviors and important components like cooperation and verification. There is so much exploration ground here. The exciting part is that this is not limited to coding tasks; it extends to business use cases and many other technical domains like science and research.

elvis

102,035 görüntüleme • 1 ay önce

Bash is all you need! Which is why I'm introducing my holiday project: just-bash just-bash is a pretty complete implementation of bash in TypeScript designed to be used as a bash tool by AI agents. Because it turns out agents love exploring data via shell scripts, even beyond coding. It comes with grep, sed, awk and the 99th percentile features that an agent like Claude Code or Cursor would use. In fact, Claude Code can use it for secure bash execution. In the package - A bash-tool for AI SDK - A binary for use by yourself or your coding agents - An overlay filesystem to feed files to your agent securely - A Vercel Sandbox compatible API, so you can quickly upgrade to a real VM if you need to run binaries - An example AI agent that explores the just-bash code base using just-bash - I imported the Oils shell bash compatibility suite and just-bash passes a very good chunk What is interesting about this codebase: It was essentially entirely written by Opus 4.5. Coding agents love bash and they are good at reproducing it. They are also great at text-book recursive descent parsers and AST tweet-walk interpreters. That said, it is, like, a lot of code and I didn't read it all 😅. This is very much a hack, but it also seems to be _really_ useful. I haven't really found anything agents want to use that it doesn't support and it's fast and secure (caveats apply). It doesn't have write access to your computer and the filesystem is given a root that the agent cannot escape from. Find it at Related: Our recent blog post how we migrated our data analysis agent to bash tools and achieved incredible quality improvements The video shows the example agent investigating the just-bash code base
1:47

Bash is all you need! Which is why I'm introducing my holiday project: just-bash just-bash is a pretty complete implementation of bash in TypeScript designed to be used as a bash tool by AI agents. Because it turns out agents love exploring data via shell scripts, even beyond coding. It comes with grep, sed, awk and the 99th percentile features that an agent like Claude Code or Cursor would use. In fact, Claude Code can use it for secure bash execution. In the package - A bash-tool for AI SDK - A binary for use by yourself or your coding agents - An overlay filesystem to feed files to your agent securely - A Vercel Sandbox compatible API, so you can quickly upgrade to a real VM if you need to run binaries - An example AI agent that explores the just-bash code base using just-bash - I imported the Oils shell bash compatibility suite and just-bash passes a very good chunk What is interesting about this codebase: It was essentially entirely written by Opus 4.5. Coding agents love bash and they are good at reproducing it. They are also great at text-book recursive descent parsers and AST tweet-walk interpreters. That said, it is, like, a lot of code and I didn't read it all 😅. This is very much a hack, but it also seems to be _really_ useful. I haven't really found anything agents want to use that it doesn't support and it's fast and secure (caveats apply). It doesn't have write access to your computer and the filesystem is given a root that the agent cannot escape from. Find it at Related: Our recent blog post how we migrated our data analysis agent to bash tools and achieved incredible quality improvements The video shows the example agent investigating the just-bash code base

Malte Ubl

124,713 görüntüleme • 6 ay önce

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering
0:56

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

Om Patel

159,134 görüntüleme • 3 ay önce

UI Skills are now easier for agents. Introducing UI Skills CLI. ask Codex, Cursor, Claude Code, or any agent to use the CLI, like: "use `npx ui-skills start` to fix the motion in this dialog" it finds the best design-engineering skill for the job and uses it as context
0:20

UI Skills are now easier for agents. Introducing UI Skills CLI. ask Codex, Cursor, Claude Code, or any agent to use the CLI, like: "use `npx ui-skills start` to fix the motion in this dialog" it finds the best design-engineering skill for the job and uses it as context

Ibelick

59,045 görüntüleme • 24 gün önce

How many AI agents work at your company? We now have over 3,258 agents working alongside 1,300 humans. The crazy part is these agents were created by EVERY EMPLOYEE at our company... sales reps, marketers, customer support, product, eng. Literally EVERYONE. BUT I'm most surprised by the adoption and value that MANAGERS are getting from agents. I used to think that every IC would become a manager of agents. Now I think that managers will very likely manage WAY more agents than their ICs combined. And managers' agents will manage their ICs' agents - overseeing them for human-in-the-loop interactions. When creating agents, we use 100% context from all of your activity, files edited, tasks and projects worked on, hierarchy, skills, and role information. We build a user-based context model to make agents as relatable as possible to the specific human that we're building for. This means they truly understand the nuances of the work and what "great" looks like - because great is very much in the eye of the beholder. Great is by definition, subjective. This is also why the human ENGAGEMENT loops are SO vital to agent value. The iteration AFTER the agent is onboarded is where the MAGIC happens. This is just like a manager managing an IC in real life... you're giving feedback. In this case, though, agents learn INSTANTLY, and they retain the knowledge perfectly and indefinitely. Even though I've been pushing AI for years now to everyone in our company, this was the first time we had truly end-to-end AI adoption and retention. This kind of AI adoption is wild. But the value we're realizing is truly INSANE. Super Agents outnumber our humans nearly 3 to 1. What if you could 3X your workforce overnight? Watch this video to see how 👇
0:59

How many AI agents work at your company? We now have over 3,258 agents working alongside 1,300 humans. The crazy part is these agents were created by EVERY EMPLOYEE at our company... sales reps, marketers, customer support, product, eng. Literally EVERYONE. BUT I'm most surprised by the adoption and value that MANAGERS are getting from agents. I used to think that every IC would become a manager of agents. Now I think that managers will very likely manage WAY more agents than their ICs combined. And managers' agents will manage their ICs' agents - overseeing them for human-in-the-loop interactions. When creating agents, we use 100% context from all of your activity, files edited, tasks and projects worked on, hierarchy, skills, and role information. We build a user-based context model to make agents as relatable as possible to the specific human that we're building for. This means they truly understand the nuances of the work and what "great" looks like - because great is very much in the eye of the beholder. Great is by definition, subjective. This is also why the human ENGAGEMENT loops are SO vital to agent value. The iteration AFTER the agent is onboarded is where the MAGIC happens. This is just like a manager managing an IC in real life... you're giving feedback. In this case, though, agents learn INSTANTLY, and they retain the knowledge perfectly and indefinitely. Even though I've been pushing AI for years now to everyone in our company, this was the first time we had truly end-to-end AI adoption and retention. This kind of AI adoption is wild. But the value we're realizing is truly INSANE. Super Agents outnumber our humans nearly 3 to 1. What if you could 3X your workforce overnight? Watch this video to see how 👇

Zeb Evans

425,244 görüntüleme • 5 ay önce

new codex app first impressions! - pros: reliably coding in swift 🤍, a nice UI for kicking off concurrent threads/alerts, clearly there is a lot to unpack across automations/skills - asks: would love to see more killer use cases for automations, perhaps broken down by product type (iOS, web, electron); had some wrangling on chat context & a feature I expected to be more straightforward overall: I am bought in that a clean/beautiful UI for coordinating many agents (some with long running tasks) is powerful; I sense there's a lot more to unlock with time. I still want the ability to quickly switch between codex and claude code, as they seem to excel in different (+ complementary) dev tasks
7:58

new codex app first impressions! - pros: reliably coding in swift 🤍, a nice UI for kicking off concurrent threads/alerts, clearly there is a lot to unpack across automations/skills - asks: would love to see more killer use cases for automations, perhaps broken down by product type (iOS, web, electron); had some wrangling on chat context & a feature I expected to be more straightforward overall: I am bought in that a clean/beautiful UI for coordinating many agents (some with long running tasks) is powerful; I sense there's a lot more to unlock with time. I still want the ability to quickly switch between codex and claude code, as they seem to excel in different (+ complementary) dev tasks

ashe

13,440 görüntüleme • 5 ay önce

Temporal CEO Samar Birwadker says GitHub was designed for humans, but is now at the mercy of agents. "Agents are starting to get more and more long-lived, more asynchronous, and more mission-critical." "For example, if you pick coding agents alone, is something like GitHub was designed for humans collaborate and create [pull requests] right now." "Now a lot of code is being generated by these agents, and they're the ones creating these PRs essentially, and even code review process is being automated by other agents." "So now this entire system backend, which is being built for human consumption, is now at the mercy of these agents kind of using it for their own coordination and collaboration."
3:30

Temporal CEO Samar Birwadker says GitHub was designed for humans, but is now at the mercy of agents. "Agents are starting to get more and more long-lived, more asynchronous, and more mission-critical." "For example, if you pick coding agents alone, is something like GitHub was designed for humans collaborate and create [pull requests] right now." "Now a lot of code is being generated by these agents, and they're the ones creating these PRs essentially, and even code review process is being automated by other agents." "So now this entire system backend, which is being built for human consumption, is now at the mercy of these agents kind of using it for their own coordination and collaboration."

MTS

26,902 görüntüleme • 2 ay önce

AI agents are becoming increasingly capable of taking actions beyond the chat window and interacting with tools in the real world, such as web browsers. We explored this capability by having an AI agent present one of our interactive web-based demos. In this video, it's presenting our election interference demo. This agent is a Cursor coding agent and is equipped with tools to read and interact with the browser (using Playwright) and perform text-to-speech (with ElevenLabs), in addition to the standard Cursor tools.
3:23

AI agents are becoming increasingly capable of taking actions beyond the chat window and interacting with tools in the real world, such as web browsers. We explored this capability by having an AI agent present one of our interactive web-based demos. In this video, it's presenting our election interference demo. This agent is a Cursor coding agent and is equipped with tools to read and interact with the browser (using Playwright) and perform text-to-speech (with ElevenLabs), in addition to the standard Cursor tools.

CivAI

18,428 görüntüleme • 7 ay önce

Codex team is back in the kitchen with a really nice quality of life upgrade for subagents. With the advent of custom roles, they have also upgraded the TUI experience in two really meaningful ways. > All agents now get a name for better readability > Additionally, the agent role is declared. > Subagent name, role, and status are now color coded. > Subagent rendering was also optimized for readability > /agents slash command shows all agents, even 2+ layers deep. And here's the biggest and most important change. Subagent injection. Before, sometimes the orchestration agent would continue work and lose track of the work of a subagent. Now, when a subagent is blocked or completed, it injects a message back up the chain to ensure that the parent sees the message. This is a really big improvement overall, and leads to much more reliable inter-agent communication, reliability, and DX. In this example, I used the parent agent to spin up a worker agent, which then spawned two more "Spark" agents a second layer deep. I was able to easily tell them apart, switch between the threads, and see exactly what they were prompted. All of this will be available in update 0.105.0 I don't know who JIF is at OpenAI, but they are truly a legend.
0:35

Codex team is back in the kitchen with a really nice quality of life upgrade for subagents. With the advent of custom roles, they have also upgraded the TUI experience in two really meaningful ways. > All agents now get a name for better readability > Additionally, the agent role is declared. > Subagent name, role, and status are now color coded. > Subagent rendering was also optimized for readability > /agents slash command shows all agents, even 2+ layers deep. And here's the biggest and most important change. Subagent injection. Before, sometimes the orchestration agent would continue work and lose track of the work of a subagent. Now, when a subagent is blocked or completed, it injects a message back up the chain to ensure that the parent sees the message. This is a really big improvement overall, and leads to much more reliable inter-agent communication, reliability, and DX. In this example, I used the parent agent to spin up a worker agent, which then spawned two more "Spark" agents a second layer deep. I was able to easily tell them apart, switch between the threads, and see exactly what they were prompted. All of this will be available in update 0.105.0 I don't know who JIF is at OpenAI, but they are truly a legend.

am.will

78,267 görüntüleme • 4 ay önce

✨New demo: what if vibe coding felt more visual? Brian Lovin Mary Rose Cook and I did a game jam using Notion as our "IDE": launching Cursor agents from a task board, and making a custom image for each task 😎 The demo shows 3 ideas for the future of agents: 1) Agents should collaborate across apps. Each app has its focus--Notion AI is good at drafting specs and organizing tasks; Cursor is good at coding. So let them specialize! Today we're launching a new integration where Notion AI can kick off Cursor Cloud Agents to do coding tasks. The Cursor API accepts natural language prompts, so I think of this as "cross-app sub-agents" -- it's kinda cute how it resembles humans hiring outside contractors 😊 BTW: the parallelism of cloud agents is incredibly freeing for creativity, but it also creates a new problem: sooo much work to keep track of! Which brings us to the next idea... 2) Agent orchestration is a data visualization problem. A powerful frame for designing agent UIs is to think of the chat transcripts as the "raw data" and ask: what visual projections might help people make sense of this data at scale? We need to engage our human GPUs -- our visual processing -- to understand what the computer GPUs are doing for us! One thing we can do is use AI to populate traditional UIs like progress bars and status updates. But there are also new possibilities now... For example: when you have a lot going on, it can be hard to identify tasks just by text titles. So we tried generating an AI image for each task -- turns out this helps a lot by giving it a unique visual identity! And of course, it also just makes it super fun to build with friends 😃 Speaking of friends... 3) The future of coding is collaborative. Sometimes it feels like IC engineers are being reduced to middle managers: shuffling information between the team's context and the coding agents that they individually manage. The solution: bring all the people and agents into one shared space, with shared context and visibility! In the video you can get a glimpse of how this feels. Mary, Brian and I record ourselves chatting about ideas, and then we use AI to turn that conversation into a list of tasks on a shared board. As the ideas get built in parallel, we can all monitor progress and review the work together, nothing is siloed. My main takeaway from this game jam was: damn, creativity with friends, at the speed of conversation, is incredibly fun. --- Our goal here is to let anyone use Notion as a fun and creative "software factory" to build software together with your team. Give the Cursor integration a shot and let us know what you think! (AI Image gen in Notion isn't GA yet, but coming soon and already out to some users) And let me know if you'd want a template or more detailed instructions on the setup we showed in this demo...
12:37

✨New demo: what if vibe coding felt more visual? Brian Lovin Mary Rose Cook and I did a game jam using Notion as our "IDE": launching Cursor agents from a task board, and making a custom image for each task 😎 The demo shows 3 ideas for the future of agents: 1) Agents should collaborate across apps. Each app has its focus--Notion AI is good at drafting specs and organizing tasks; Cursor is good at coding. So let them specialize! Today we're launching a new integration where Notion AI can kick off Cursor Cloud Agents to do coding tasks. The Cursor API accepts natural language prompts, so I think of this as "cross-app sub-agents" -- it's kinda cute how it resembles humans hiring outside contractors 😊 BTW: the parallelism of cloud agents is incredibly freeing for creativity, but it also creates a new problem: sooo much work to keep track of! Which brings us to the next idea... 2) Agent orchestration is a data visualization problem. A powerful frame for designing agent UIs is to think of the chat transcripts as the "raw data" and ask: what visual projections might help people make sense of this data at scale? We need to engage our human GPUs -- our visual processing -- to understand what the computer GPUs are doing for us! One thing we can do is use AI to populate traditional UIs like progress bars and status updates. But there are also new possibilities now... For example: when you have a lot going on, it can be hard to identify tasks just by text titles. So we tried generating an AI image for each task -- turns out this helps a lot by giving it a unique visual identity! And of course, it also just makes it super fun to build with friends 😃 Speaking of friends... 3) The future of coding is collaborative. Sometimes it feels like IC engineers are being reduced to middle managers: shuffling information between the team's context and the coding agents that they individually manage. The solution: bring all the people and agents into one shared space, with shared context and visibility! In the video you can get a glimpse of how this feels. Mary, Brian and I record ourselves chatting about ideas, and then we use AI to turn that conversation into a list of tasks on a shared board. As the ideas get built in parallel, we can all monitor progress and review the work together, nothing is siloed. My main takeaway from this game jam was: damn, creativity with friends, at the speed of conversation, is incredibly fun. --- Our goal here is to let anyone use Notion as a fun and creative "software factory" to build software together with your team. Give the Cursor integration a shot and let us know what you think! (AI Image gen in Notion isn't GA yet, but coming soon and already out to some users) And let me know if you'd want a template or more detailed instructions on the setup we showed in this demo...

Geoffrey Litt

88,919 görüntüleme • 4 ay önce

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

493,537 görüntüleme • 3 ay önce

I have built a Windows x64 sampling profiler for native code+C# to be used by coding agents. Why? Because it is irresponsible to let computers write code but give them no tools to evaluate the performance of their code. Stop guessing, start measuring. -> How does it work? Just point your agent to the profiler and let them measure and optimize. Or record a trace yourself and let the agent interpret the results for you. Works with Claude Code, Codex, pi, etc. The profiler also has a couple of neat features by itself like giving you estimates for how much time your code is spending on memory stalls and annotating disassembly with inlining information. Take a look and try it for free!
12:40

I have built a Windows x64 sampling profiler for native code+C# to be used by coding agents. Why? Because it is irresponsible to let computers write code but give them no tools to evaluate the performance of their code. Stop guessing, start measuring. -> How does it work? Just point your agent to the profiler and let them measure and optimize. Or record a trace yourself and let the agent interpret the results for you. Works with Claude Code, Codex, pi, etc. The profiler also has a couple of neat features by itself like giving you estimates for how much time your code is spending on memory stalls and annotating disassembly with inlining information. Take a look and try it for free!

Sebastian Schöner

12,969 görüntüleme • 2 ay önce

Announcing Builder 2.0 We raised $67M to build collaborative coding for Claude and Codex - Start tasks from a local branch, Slack or Jira - Real-time collab between humans and agents - 100s of parallel agents code, test, review Reply "Builder" and I'll DM you 500 agent credits
0:52

Announcing Builder 2.0 We raised $67M to build collaborative coding for Claude and Codex - Start tasks from a local branch, Slack or Jira - Real-time collab between humans and agents - 100s of parallel agents code, test, review Reply "Builder" and I'll DM you 500 agent credits

Steve (Builder.io)

90,015,973 görüntüleme • 3 ay önce

I wanted to share a quick demo of what we've been working on with our ai agent cloud. This enables fast deployment of agents that have access to a suite of tools, and was designed with agent interoperability in mind. This demo shows how you can go from nothing to an AI twitter agent in a couple minutes. This is what we are using internally to manage deployments, so we will consistently upgrading its capabilities. The next goals are to enable simple TEE deployments for agents, and focus on building out feature for agent interoperability to simplify agent to agent collaboration.
4:16

I wanted to share a quick demo of what we've been working on with our ai agent cloud. This enables fast deployment of agents that have access to a suite of tools, and was designed with agent interoperability in mind. This demo shows how you can go from nothing to an AI twitter agent in a couple minutes. This is what we are using internally to manage deployments, so we will consistently upgrading its capabilities. The next goals are to enable simple TEE deployments for agents, and focus on building out feature for agent interoperability to simplify agent to agent collaboration.

Johnny

27,176 görüntüleme • 1 yıl önce