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

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

На главную

Codex 0.107.0 is here, and with it: FORKS🍴 This minor update includes the ability to fork your current chat history directly with custom multi agents with just a quick prompt. "Fork this session using n subagent(s)" This unlocks some interesting use-cases where you can launch multiple agents that retain...

LLMJunky's profile picture

am.will

8,658 subscribers

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

ОбразованиеНаука и технологии
LIVE

Anya Rossi• Live Now

Private livecam show

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

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

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

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

This is so cool. In the next Codex update, multi agents will get a massive flexibility upgrade. "Hey Codex, when you implement this plan, I want you to delegate all the lower complexity tasks to GPT 5.3 Spark subagents" Instead of needing to create 100 different custom agent roles for different situations, you can just prompt your agent to spawn whatever model or reasoning level you want. With only natural language. No config files. No pre-defined roles. Just tell the orchestrator what to use and it listens.
0:41

This is so cool. In the next Codex update, multi agents will get a massive flexibility upgrade. "Hey Codex, when you implement this plan, I want you to delegate all the lower complexity tasks to GPT 5.3 Spark subagents" Instead of needing to create 100 different custom agent roles for different situations, you can just prompt your agent to spawn whatever model or reasoning level you want. With only natural language. No config files. No pre-defined roles. Just tell the orchestrator what to use and it listens.

am.will

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

Cursor now natively supports git worktrees. You can run multiple agents in parallel, each with their own isolated copy of the codebase. This is great for comparing models or running the same model multiple times and picking the best result.
0:42

Cursor now natively supports git worktrees. You can run multiple agents in parallel, each with their own isolated copy of the codebase. This is great for comparing models or running the same model multiple times and picking the best result.

Lee Robinson

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

This is incredibly useful for those using Claude Code! I have two computers, and sharing your Claude Code sessions is almost impossible without this. I often start working on something on my desktop, and then want to continue working on the same session (same context, conversation, etc.) on my laptop. The folks at Depot built an integration that solves this problem: You can now start a session on one computer and resume it anywhere else in the world! You can even share it with other team members so they can also contribute to it. Here is an article showing you how the Depot team uses this feature with Claude Code to automate their GitHub Actions Runner updates: Thanks to the team for the effort in building this integration and collaborating with me on this post.
4:29

This is incredibly useful for those using Claude Code! I have two computers, and sharing your Claude Code sessions is almost impossible without this. I often start working on something on my desktop, and then want to continue working on the same session (same context, conversation, etc.) on my laptop. The folks at Depot built an integration that solves this problem: You can now start a session on one computer and resume it anywhere else in the world! You can even share it with other team members so they can also contribute to it. Here is an article showing you how the Depot team uses this feature with Claude Code to automate their GitHub Actions Runner updates: Thanks to the team for the effort in building this integration and collaborating with me on this post.

Santiago

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

I asked Garry Tan how to use meta prompting to get better at AI: "My partners at YC Jared Friedman and Pete Koomen showed me how to do this. You can take almost anything that you do all the time and just drop it into a context window. And then say, “Here’s a bunch of inputs and outputs." And maybe you also add a bunch of notes. And then you tell it, “Write me a prompt that can act as an agent that takes this input and makes this output over here.” You can do this for almost any type of knowledge work. And you can even introspect. "What are things you notice that I did to convert this from the input to the output?”. And then you can just start using the prompt. Initially, it’s going to suck. Because it’s just not that smart yet. But what’s funny is now, I also use it to Iterate my writing. You can be very direct, "I would never say that", "Don’t say it like this", or "Oh, you used the long word there, use the short word". Just speak to it conversationally. And then when you're happy with the output, you can use that new output to make a new prompt. "Based on this conversation, give me a better initial prompt that incorporates all the things we talked about." And you can do this with literally everything. And in theory, there’s so much it applies to that people do day-to-day. You could use it for tweets. You could use it for editing podcasts. You can use it for pretty much everything. I have a folder of prompts that I use all the time. My YouTube prompt is on v27 or something. I'll go through this process with all the different max models. I'll use GPT 5.2 Pro. I’ll use Grok. I'll use Claude. Then, I’ll take all the outputs from all the models and put them into Claude and say "Here’s my prompt, here’s the output from four LLMs, including yourself. Rate each response and tell me what the pros and cons of each approach are." And I usually say "give it to me in numbered form". And then you can agree with one, disagree with two, tell it three is this or that. And then after that, you say given all of this, synthesize it."
4:16

I asked Garry Tan how to use meta prompting to get better at AI: "My partners at YC Jared Friedman and Pete Koomen showed me how to do this. You can take almost anything that you do all the time and just drop it into a context window. And then say, “Here’s a bunch of inputs and outputs." And maybe you also add a bunch of notes. And then you tell it, “Write me a prompt that can act as an agent that takes this input and makes this output over here.” You can do this for almost any type of knowledge work. And you can even introspect. "What are things you notice that I did to convert this from the input to the output?”. And then you can just start using the prompt. Initially, it’s going to suck. Because it’s just not that smart yet. But what’s funny is now, I also use it to Iterate my writing. You can be very direct, "I would never say that", "Don’t say it like this", or "Oh, you used the long word there, use the short word". Just speak to it conversationally. And then when you're happy with the output, you can use that new output to make a new prompt. "Based on this conversation, give me a better initial prompt that incorporates all the things we talked about." And you can do this with literally everything. And in theory, there’s so much it applies to that people do day-to-day. You could use it for tweets. You could use it for editing podcasts. You can use it for pretty much everything. I have a folder of prompts that I use all the time. My YouTube prompt is on v27 or something. I'll go through this process with all the different max models. I'll use GPT 5.2 Pro. I’ll use Grok. I'll use Claude. Then, I’ll take all the outputs from all the models and put them into Claude and say "Here’s my prompt, here’s the output from four LLMs, including yourself. Rate each response and tell me what the pros and cons of each approach are." And I usually say "give it to me in numbered form". And then you can agree with one, disagree with two, tell it three is this or that. And then after that, you say given all of this, synthesize it."

The Peel

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

Agent apps don’t win on the model, they win on the harness. But creating that harness is painful. Terminal Use is hosting infrastructure for background agents built for iterating: fork filesystems and try multiple agents in parallel. The platform is CLI-first, which allows your coding agents like Claude Code & Codex to help you debug, hypothesize improvements, and analyze outputs. Congrats on the launch Vivek Raja, Stavros Filosidis, and Filip Balucha!
1:27

Agent apps don’t win on the model, they win on the harness. But creating that harness is painful. Terminal Use is hosting infrastructure for background agents built for iterating: fork filesystems and try multiple agents in parallel. The platform is CLI-first, which allows your coding agents like Claude Code & Codex to help you debug, hypothesize improvements, and analyze outputs. Congrats on the launch Vivek Raja, Stavros Filosidis, and Filip Balucha!

Y Combinator

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

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:
2:49

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

Andrew Ng

105,343 просмотров • 1 год назад

I never use planning mode in Codex. GPT 5.5 loves to research, so I just have a conversation and reach a pseudo-plan in chat. Then, I let it implement, maybe with a /fork beforehand to keep that plan as a revisit-able point. Probably the biggest switch coming from Claude Code
1:12

I never use planning mode in Codex. GPT 5.5 loves to research, so I just have a conversation and reach a pseudo-plan in chat. Then, I let it implement, maybe with a /fork beforehand to keep that plan as a revisit-able point. Probably the biggest switch coming from Claude Code

Ben Holmes

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

x402 is finally catching fire, but how do you actually build with it? In this video you'll learn how to build custom x402 agents in just 5 minutes. 🔥 The app is Open Source and gets you started with both a client and a merchant agent, everything you need to build your own agents. I show you how to extend it to sell EBooks for 1USDC.
7:48

x402 is finally catching fire, but how do you actually build with it? In this video you'll learn how to build custom x402 agents in just 5 minutes. 🔥 The app is Open Source and gets you started with both a client and a merchant agent, everything you need to build your own agents. I show you how to extend it to sell EBooks for 1USDC.

nader dabit

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

Reducto CLI is the best way for agents to interact with document data in any workflow, and I’m really excited to see the range of use cases that are possible with this. It uses our frontier models for anything from parsing to editing, and can help automate full workflows like building spreadsheets or reports with really ugly cases. Raunak’s demo is a great example of what this unlocks
1:46

Reducto CLI is the best way for agents to interact with document data in any workflow, and I’m really excited to see the range of use cases that are possible with this. It uses our frontier models for anything from parsing to editing, and can help automate full workflows like building spreadsheets or reports with really ugly cases. Raunak’s demo is a great example of what this unlocks

Adit

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

I just built an entire app in 7 minutes using Codex Spark. EveryMCP: a universal MCP server installer that configures 15+ coding agents from a single CLI command. 12 Codex Spark subagents. All running in parallel. At the same time. The project itself isn't complicated, but just imagine what this looks like when you scale the complexity. My setup: • Codex 5.3 High to plan • Codex 5.3 Medium to orchestrate • 12 Codex Spark agents (xhigh) to implement in one shot Spark isn't competing with the big models. It's a different tool entirely. You orchestrate it. You run it in swarms. And it moves at a speed that wasn't possible before, even for the top 1% of AI coders. More complex workflows coming soon. Comment below if you want me to tell you how I did it.
4:29

I just built an entire app in 7 minutes using Codex Spark. EveryMCP: a universal MCP server installer that configures 15+ coding agents from a single CLI command. 12 Codex Spark subagents. All running in parallel. At the same time. The project itself isn't complicated, but just imagine what this looks like when you scale the complexity. My setup: • Codex 5.3 High to plan • Codex 5.3 Medium to orchestrate • 12 Codex Spark agents (xhigh) to implement in one shot Spark isn't competing with the big models. It's a different tool entirely. You orchestrate it. You run it in swarms. And it moves at a speed that wasn't possible before, even for the top 1% of AI coders. More complex workflows coming soon. Comment below if you want me to tell you how I did it.

am.will

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

This is a real Shopify store. A storefront you play like a game: walk around, step into shops, and buy real products with others shopping right next to you. Built this with v0 using the new native Shopify integration. Fork the template and build your own storefront game.
0:45

This is a real Shopify store. A storefront you play like a game: walk around, step into shops, and buy real products with others shopping right next to you. Built this with v0 using the new native Shopify integration. Fork the template and build your own storefront game.

Esteban Suárez

91,704 просмотров • 27 дней назад

Tomorrow, independent developer Super Testnet comes on the show to share why he's proposing a User-Rejected Soft Fork for BIP 110 — and explores the different ways a potential 'soft fork war' could play out around BIP 110 in August. This episode is chockfull of soft-fork history, with insights into how changes to consensus have historically been executed and how these processes could shift going forward.
0:33

Tomorrow, independent developer Super Testnet comes on the show to share why he's proposing a User-Rejected Soft Fork for BIP 110 — and explores the different ways a potential 'soft fork war' could play out around BIP 110 in August. This episode is chockfull of soft-fork history, with insights into how changes to consensus have historically been executed and how these processes could shift going forward.

Isabel Foxen Duke⚡️

17,045 просмотров • 25 дней назад

Introducing Clips - 100% free, open source, agent-native alternative to Loom Unlike Loom, agent's can fully understand Clips just from a URL. Every Clip comes with APIs and metadata for agents to explore their contents. Agents can "see and hear" anything in a Clip - not just transcripts, but everything visually in the video at any timestamp. Easily share bug reports, feedback, analyses, or anything else in a way that you can easily pass to agents to use to improve products, reports, or more. Also unlike Loom, you own the software, so no one can jack up prices on you suddenly like Loom did to us. Clips is made to be customized. The built-in agent can customize its own code, so you can personalize the app to your needs and workflows. This, in my opinion, is the future of software. Open-source, forkable, customizable with agents, to make your own personal version of anything. You can also import Looms just from a URL and upload videos as well. I got so sick of telling people "don't send me feedback as looms, I can't pass those to agents, I need text and images" that I had to just solve this once and for all. There's a free hosted version you can use too, or fork and self host yourself. Will link to both in the replies.
0:35

Introducing Clips - 100% free, open source, agent-native alternative to Loom Unlike Loom, agent's can fully understand Clips just from a URL. Every Clip comes with APIs and metadata for agents to explore their contents. Agents can "see and hear" anything in a Clip - not just transcripts, but everything visually in the video at any timestamp. Easily share bug reports, feedback, analyses, or anything else in a way that you can easily pass to agents to use to improve products, reports, or more. Also unlike Loom, you own the software, so no one can jack up prices on you suddenly like Loom did to us. Clips is made to be customized. The built-in agent can customize its own code, so you can personalize the app to your needs and workflows. This, in my opinion, is the future of software. Open-source, forkable, customizable with agents, to make your own personal version of anything. You can also import Looms just from a URL and upload videos as well. I got so sick of telling people "don't send me feedback as looms, I can't pass those to agents, I need text and images" that I had to just solve this once and for all. There's a free hosted version you can use too, or fork and self host yourself. Will link to both in the replies.

Steve (Builder.io)

228,242 просмотров • 18 дней назад

You can basically generate your own custom visual stories using Gemini with just a single prompt 'This is a fictional movie set in a fantasy world similar to The Lord of the Rings. Use this as a starting point and imagine the next sequence of scenes. Create a series of separate images, each depicting a distinct moment in the story, presented in a sequential order like a storyboard. Include quotes for each image to narrate the events happening within it. Ensure the flow between images is consistent and logical, with each one styled like a cinematic movie shot that advances the narrative. Maintain the same format and visual style across all images to keep them cohesive'
0:21

You can basically generate your own custom visual stories using Gemini with just a single prompt 'This is a fictional movie set in a fantasy world similar to The Lord of the Rings. Use this as a starting point and imagine the next sequence of scenes. Create a series of separate images, each depicting a distinct moment in the story, presented in a sequential order like a storyboard. Include quotes for each image to narrate the events happening within it. Ensure the flow between images is consistent and logical, with each one styled like a cinematic movie shot that advances the narrative. Maintain the same format and visual style across all images to keep them cohesive'

Cristian Peñas ░░░░░░░░

38,500 просмотров • 1 год назад

In this episode, Beyang and Thorsten discuss strategies for effective agentic coding, including the 101 of how it's different from coding with chat LLMs, the key constraint of the context window, how and where subagents can help, and the new oracle subagent which combines multiple LLMs. 00:38 Intros 03:20 How coding with agents is very different from coding with prior AI tools 10:31 Example: fix a simple issue 14:13 Example: debugging an issue with an MCP server 21:50 Example: unifying two build scripts 25:09 How the context window is a key constraint 31:01 Why it's best to focus on one thing at a time 33:09 Subagents and context windows 33:49 The codebase search subagent 38:33 General-purpose subagents 44:05 When to use subagents 46:44 The oracle subagent and o3 51:32 Multi-model agents
53:54

In this episode, Beyang and Thorsten discuss strategies for effective agentic coding, including the 101 of how it's different from coding with chat LLMs, the key constraint of the context window, how and where subagents can help, and the new oracle subagent which combines multiple LLMs. 00:38 Intros 03:20 How coding with agents is very different from coding with prior AI tools 10:31 Example: fix a simple issue 14:13 Example: debugging an issue with an MCP server 21:50 Example: unifying two build scripts 25:09 How the context window is a key constraint 31:01 Why it's best to focus on one thing at a time 33:09 Subagents and context windows 33:49 The codebase search subagent 38:33 General-purpose subagents 44:05 When to use subagents 46:44 The oracle subagent and o3 51:32 Multi-model agents

Amp — Research Preview

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

The @GitHub Copilot CLI lets you /fork conversations into different sessions you can toggle between. I've been using this lately to go down different roads with the same plan before I commit to one of them.
0:40

The @GitHub Copilot CLI lets you /fork conversations into different sessions you can toggle between. I've been using this lately to go down different roads with the same plan before I commit to one of them.

Burke Holland

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

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,752 просмотров • 1 год назад

WAKE UP AMERICA YOU ARE UNDER ATTACK ⛔️ Latest update on the WEF Maui, Lahaina Fires, Hawaii 🔥🚨 ‌ Legislation Passed in Hawaii RIGHT BEFORE & Lockheed Martin is one of the biggest donors of American Red Cross, who is also developing Weapons D.E.W's (Direct Energy Weapons) for Military ‌ “Because when I look at it, when you get into these things and you look at the history, you have so many stories which have been rewritten and then told the different thing. And then if we look at two things with the things with the governor, stuff with the governor and the things that was happening with the governor. ‌ Governor was passing bills just before this so that they can change the zoning. Think about this. They wanted to change the zoning before the event. Then the event occurs and then all of a sudden the people are going to lose their land or have their land taken from them from FEMA. And that's what FEMA does. FEMA comes in there so that they can try to say they're going to save you, just like the Red Cross. ‌ Baloney. And they're trying to say that they're going to help you when they're on the other side. If you look at the largest donator or one of the largest donators on the red Cross, it's Lockheed Martin. ‌ Lockheed Martin, THEY CREATE DEWs, DEWs (Direct Energy Weapons). So if you think about this, if the people who create the weapons are funding the people who come in after the destruction, then do you see what happens? It goes back and forth. And then in the meantime, a new story, a new fairy tale, a new history, whatever you want to say is written. ‌ We start to see this and they take over and then the history is completely lost and all the heritage is gone. The culture is gone. And they slowly keep doing this. AND THEYmVE DONE THIS SO MANY TIMES ‌ Just to see this, just to see just to to feel this through, you could feel the feel through the screen. You could feel it. You could see the pictures and know that something is so wrong ⚠️ ‌ #Hawaii #MauiFires #Lahaina
1:58

WAKE UP AMERICA YOU ARE UNDER ATTACK ⛔️ Latest update on the WEF Maui, Lahaina Fires, Hawaii 🔥🚨 ‌ Legislation Passed in Hawaii RIGHT BEFORE & Lockheed Martin is one of the biggest donors of American Red Cross, who is also developing Weapons D.E.W's (Direct Energy Weapons) for Military ‌ “Because when I look at it, when you get into these things and you look at the history, you have so many stories which have been rewritten and then told the different thing. And then if we look at two things with the things with the governor, stuff with the governor and the things that was happening with the governor. ‌ Governor was passing bills just before this so that they can change the zoning. Think about this. They wanted to change the zoning before the event. Then the event occurs and then all of a sudden the people are going to lose their land or have their land taken from them from FEMA. And that's what FEMA does. FEMA comes in there so that they can try to say they're going to save you, just like the Red Cross. ‌ Baloney. And they're trying to say that they're going to help you when they're on the other side. If you look at the largest donator or one of the largest donators on the red Cross, it's Lockheed Martin. ‌ Lockheed Martin, THEY CREATE DEWs, DEWs (Direct Energy Weapons). So if you think about this, if the people who create the weapons are funding the people who come in after the destruction, then do you see what happens? It goes back and forth. And then in the meantime, a new story, a new fairy tale, a new history, whatever you want to say is written. ‌ We start to see this and they take over and then the history is completely lost and all the heritage is gone. The culture is gone. And they slowly keep doing this. AND THEYmVE DONE THIS SO MANY TIMES ‌ Just to see this, just to see just to to feel this through, you could feel the feel through the screen. You could feel it. You could see the pictures and know that something is so wrong ⚠️ ‌ #Hawaii #MauiFires #Lahaina

Wall Street Apes

1,018,578 просмотров • 2 лет назад

Introducing the Clips chrome extension - the easiest way to send bug reports to agents with video, transcript, and browser debug info captured automatically. 100% free and open source. If you are like me and get tired of manually typing instructions to agents, attaching screenshots, pasting debug logs, and all of that, this might be your new favorite tool. With the Clips chrome extension, you can just click the Clips icon, hit record, and start talking. Visually demonstrate your issue, go through the flow, point out what’s broken. Clips will capture everything on your screen, plus network requests, browser logs, client errors, and all the details around them. And it redacts sensitive information. Then it gives you a link you can send to humans so they can play it and take a look. Or, more importantly, just give it to your agents by just pasting the URL to them. The link has special metadata for agents so just from the URL, the agent can pull all information from the clip automatically. No plugin or MCP server required. That means it can "see and hear" what’s in the video - read the transcript, grab snapshots at any timestamp, and inspect the logs and network requests that were shared with it. So whether you want to quickly demo an issue and send all that context to an agent, or get better bug reports from teammates, recording and sending Clips makes that super easy. Unlike expensive apps like Loom, this is all 100% free and open source. The framework that powers this, plus a bunch of other free applications, is open source too. You can just sign up and use it, or fork it and customize it to your needs. This, in my opinion, is the future of software. Rather than bloated SaaS that charges you a ton of money and still doesn’t even have the things you need, we get free open source canonical apps that you can fork and customize in any way you want. I'll link to all this stuff in the replies. If you try it, let me know your feedback.
1:27

Introducing the Clips chrome extension - the easiest way to send bug reports to agents with video, transcript, and browser debug info captured automatically. 100% free and open source. If you are like me and get tired of manually typing instructions to agents, attaching screenshots, pasting debug logs, and all of that, this might be your new favorite tool. With the Clips chrome extension, you can just click the Clips icon, hit record, and start talking. Visually demonstrate your issue, go through the flow, point out what’s broken. Clips will capture everything on your screen, plus network requests, browser logs, client errors, and all the details around them. And it redacts sensitive information. Then it gives you a link you can send to humans so they can play it and take a look. Or, more importantly, just give it to your agents by just pasting the URL to them. The link has special metadata for agents so just from the URL, the agent can pull all information from the clip automatically. No plugin or MCP server required. That means it can "see and hear" what’s in the video - read the transcript, grab snapshots at any timestamp, and inspect the logs and network requests that were shared with it. So whether you want to quickly demo an issue and send all that context to an agent, or get better bug reports from teammates, recording and sending Clips makes that super easy. Unlike expensive apps like Loom, this is all 100% free and open source. The framework that powers this, plus a bunch of other free applications, is open source too. You can just sign up and use it, or fork it and customize it to your needs. This, in my opinion, is the future of software. Rather than bloated SaaS that charges you a ton of money and still doesn’t even have the things you need, we get free open source canonical apps that you can fork and customize in any way you want. I'll link to all this stuff in the replies. If you try it, let me know your feedback.

Steve (Builder.io)

59,767 просмотров • 14 дней назад

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)
5:02

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)

elvis

14,874 просмотров • 3 дней назад