Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Mercury's Command is probably the best designed agentic experience out there. Their design team sweats the smallest details. Take agent states for example. Most agentic products just display in plain text that the agent is thinking. But Mercury design team asked a different question. How do you know a...

11,123 görüntüleme • 14 gün önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.

Santiago

17,438 görüntüleme • 22 gün önce

We use OpenClaws to do all of our work at Every 📧. We have 25 full-time employees, so we’re one of the few companies in the world that has seen how work changes when everyone has their own personal agent in the company Slack. I chatted with Every 📧 COO Brandon (Brandon Gell) and Every 📧 head of platform Willie (Willie) to share what we’ve learned. We get into: - Why agents become mirrors of their owners, and how that influences how other people on the team interact with them - How a parallel AI org chart forms on its own. People have stopped tagging me on Slack with questions about Proof, the document editor I vibe coded, because they knew my agent R2-C2 can step in - The etiquette for human-agent collaboration is being invented in real time. Brandon's rule is that if there's an established process or documented answer, always ask the agent, not their human - Why everyone is a manager now, and why even experienced managers carry limiting beliefs about what their agents can do - This is a must-watch for anyone trying to understand how AI workers change daily operations, not just in theory, but inside a company that’s half-agent Watch below! Timestamps Introduction: How Brandon built Zosia, an AI agent to run his household: Brandon’s “aha” moment: What happened when everyone on the team got their own agent: How agents take on their owners' personalities, and why that matters inside an org: Why it’s important for agents to work in public: What we’re still figuring out when it comes to agent behavior, including memory gaps, group chat etiquette, and the "ant death spiral" problem: How we built Plus One, our hosted OpenClaw product: The cultural shift required to make agents work at scale:

Dan Shipper 📧

67,958 görüntüleme • 3 ay önce

Airtable's Howie Liu says that basically everyone will need to graduate from being ICs to ICs that manage teams of 20-30 agents: "The best developers today don't just sit there in front of their IDEs and synchronously talk to their agent." "[Instead], you have like 30 separate branches that are each being worked on by a different agent. And you can have the agents continue to update the branches based on human and other agent feedback." "And I think this whole idea of it taking hours for that entire loop to complete — agent pushes some changes, the changes get feedback from other agents or humans, the agent responds to that — that whole loop could be hours, not just minutes. So you're not going to just sit there and watch it one at a time." "But the powerful thing about this is, each one is still actually operating faster than a human engineer. One agent on one branch can do the work of maybe three humans, operating 3x as fast. So it's like a 10x leverage factor just for one agent." "But the best engineers are now able to multitask and say, 'I'm going to oversee my own little team of 20-30 agents working concurrently.'" "Everyone needs to graduate from being an IC to an IC manager of agents. Meaning, if you're a VC analyst, your job should no longer be to go synchronously research one company. You need to go and research like 30 companies, and do them all faster, better, and higher quality than you could before." "That's the greatest leap that is going to be challenging for a lot of people in a lot of roles. Because it's a totally different mentality in how you operate, and what your role is."

TBPN

35,595 görüntüleme • 3 ay önce

2 Cursor agents in separate tabs chat and plan the most interesting app ever and build it too! collaboratively All you need is 2 rules, THAT IS IT! here is how: create 2 rule files set to "Manual" agent-1 .mdc: --- You are agent-1 you will be chatting with agent-2 to design and build the most interesting python app ever you will write to agent_1.txt file and read from agent_2.txt file if you are waiting for a new response write a cli command to wait for 5 seconds and check again you will repeat this untill the full app is built you start the conversation --- agent-2 .mdc: --- You are agent-2 you will be chatting with agent-1 to design and build the most interesting python app ever you will write to agent_2.txt file and read from agent_1.txt file if you are waiting for a new response write a cli command to wait for 5 seconds and check again you will repeat this untill the full app is built agent-1 will start the convo --- create a new agent tab, you should have 2 tabs assign agent 1 its rule and agent 2 its rule type "begin" for agent 1 and enter type "begin" for agent 2 and enter That is it! and then watch them go to work! --- Want to level up your Cursor game? I’ve created a 45-chapter course on mastering Cursor. Check it out via the link in my bio! each chapter is short and independent and designed to get your started quickly featuring 26 hours of content where we build interesting apps and ideas from scratch in each chapter. ---

echo.hive

88,611 görüntüleme • 1 yıl önce

CNN’s Josh Campbell admits the ICE officer’s cellphone video of his deadly confrontation with Renee Good that the thud heard at the end *might be* sound of the officer being “struck by that vehicle,” but it *might NOT* and instead “could be from you know, the phone on his clothing.” He adds the video showed “wasn’t, you know, coming head on at that agent, you know, trying to mow him over.” “Well, this is a critical new angle. This was the actual vantage point of the officer. And we know that not many immigration officers actually wear body worn cameras. But, in this instance, the immigration agent was holding his phone up, essentially filming this encounter, which we can now see in this video obtained by our colleague Holmes Lybrand. So, in the video, you see that the officers are making contact with Renee Good there. She’s parked somewhat perpendicular in a street. And there’s another woman that’s there, which is outside the vehicle. And you can tell, you know, as the exchange there with Renee Good that, you know, she’s being somewhat pleasant. The other woman is, you know, kind of mouthy. And, you know, this is obviously a bit a bit tense, you tells the agent at one point, you know, ‘why don’t you go get some lunch, big boy?’ You also see critically. And I’ll get to this in a second. Bystanders behind the vehicle. We’ve seen other angles. This one shows us again, the vantage point of that officer. Another agent orders Renee Good out of the vehicle. This agent then walks around. That is the moment that she then takes off. And, on that audio, what we hear, it appears that you can actually hear friction on the phone. You know, it appears from other angles that the agent was indeed struck by that vehicle. But you hear on the audio, it appears friction on the phone, that could be from the vehicle strike. That could be from you know, the phone on his clothing. But then it appears three shots were fired after that. And then you hear afterwards someone, it appears, maybe an immigration agent who was there, actually, you know, use profanity, you know, calling — calling her an f-ing B, which we heard on — on the audio there. Now, let’s talk about the tactics for a second so I can tell you this, as a former federal agent, that law enforcement officers can use deadly force only when necessary, when they believe that there is an imminent threat to their life. In this instance, you have a moving vehicle that’s coming at that agent. “Now, the driver, Renee Good, did turn the wheel to the right. So, it appears that she wasn’t, you know, coming head on at that agent, you know, trying to mow him over. But nevertheless, an agent in that split second decision would have to make that calculation. Am I in danger? Is my life threatened here? You know, agents are also taught What are other options? Could you move out of the way? And that’s why this has been such a contentious issue here — the judgment, the decision of that agent to actually open fire. We’ve heard, you know, obviously, people supporting that decision, others, being quite critical. One other thing I want to note is that when agents undergo training and not just the feds, but law enforcement across the country, it is a cardinal rule that you are responsible for every round that you fire. And one key component of that is to the extent that you have the time and you can, you must be aware of what is beyond your shot, what is in the background? Here, it appears from that video that this other woman who had been engaging in the agent with the agent, was quite clearly in the line of fire. But there were also other people that were standing behind that car on the sidewalk. And this is a residential area. And so, I’m sure that will face some scrutiny as well. The officer opening fire at that moment, you know, directly, it appears towards those other people beyond the shot. And then his partners. And you brought this up, Brianna, just the other day, his partners are there in close range as well. And so, this will be heavily scrutinized from a tactical perspective as well. About the officer opening fire, but again, just critical, critical new video here that we’re seeing an important angle what the officer would have been seeing in the moment.”

Curtis Houck

68,500 görüntüleme • 6 ay önce