Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I ran one of my own React dashboards through Replay before treating it as ready to ship. It looked fine to me. Replay QA found a notifications button that looked completely functional but did nothing when clicked, accessibility issues across the UI, and a workflow where completing a task...

KaiteeShiks's profile picture

Kaitee

60,443 subscribers

57,558 Aufrufe • vor 1 Monat •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

The harder part of QA on a team isn't always finding the bug. It's getting the finding in front of the right person with enough context to actually fix it. I tested Replay on ClientFlow, a React client-delivery dashboard I built. Replay caught an issue in the review workflow where approving work caused the status indicator to jump out of view. But the part I wanted to test was what happens next. With Replay for Teams, the QA findings are shared with the project, and teammates can be brought directly into the Bug or Test Run context instead of passing screenshots and explanations around. Find it → share the context → get it to the right person. That feels much closer to how QA should work when more than one person is shipping. Check out Replay for Teams on Product Hunt: Replay
0:40

The harder part of QA on a team isn't always finding the bug. It's getting the finding in front of the right person with enough context to actually fix it. I tested Replay on ClientFlow, a React client-delivery dashboard I built. Replay caught an issue in the review workflow where approving work caused the status indicator to jump out of view. But the part I wanted to test was what happens next. With Replay for Teams, the QA findings are shared with the project, and teammates can be brought directly into the Bug or Test Run context instead of passing screenshots and explanations around. Find it → share the context → get it to the right person. That feels much closer to how QA should work when more than one person is shipping. Check out Replay for Teams on Product Hunt: Replay

Iris Quinn

60,483 Aufrufe • vor 1 Monat

Most apps look “done” in the editor. But what actually happens when a real user clicks through the app? I connected my PropertyBazaar project to Replay and ran Replay QA on it. It found a real issue with my newsletter form, no onSubmit handler, no subscription request, and no proper app-level feedback. What I liked is that Replay QA didn't just flag the bug. It showed the reproduction steps, evidence, root cause, and debugging context. And it goes beyond a one-time QA run: → Run QA on localhost while you're still building → Connect GitHub and run checks on PRs before merging → Share findings with teammates and Mention them → Send confirmed bugs to your existing issue tracker So instead of finding problems after shipping, you can catch what you missed while you're still building and reviewing changes. I recorded the workflow using my own project 👇 Check it out on Product Hunt:
1:45

Most apps look “done” in the editor. But what actually happens when a real user clicks through the app? I connected my PropertyBazaar project to Replay and ran Replay QA on it. It found a real issue with my newsletter form, no onSubmit handler, no subscription request, and no proper app-level feedback. What I liked is that Replay QA didn't just flag the bug. It showed the reproduction steps, evidence, root cause, and debugging context. And it goes beyond a one-time QA run: → Run QA on localhost while you're still building → Connect GitHub and run checks on PRs before merging → Share findings with teammates and Mention them → Send confirmed bugs to your existing issue tracker So instead of finding problems after shipping, you can catch what you missed while you're still building and reviewing changes. I recorded the workflow using my own project 👇 Check it out on Product Hunt:

Shraddha Bharuka

56,228 Aufrufe • vor 1 Monat

My AI app looked ready to ship. Replay QA proved otherwise. Before launching, I connected the GitHub repo to Replay QA, let it run through the app like a real user, and within a few minutes it surfaced issues I would've never noticed by manually clicking around. What I liked most wasn't just finding bugs. It showed exactly what happened in the browser, explained the likely root cause, and gave enough context to fix the issue without guessing. Instead of running a one-time check, I connected the repo so Replay QA can keep testing every time I push changes or open a PR. No Playwright setup. No complicated pipeline configuration. Just a practical QA gate before users ever find the problems. If you're building with Cursor, Claude Code, Codex, Lovable, Bolt, Replit, or any AI coding workflow, this is worth adding before your next launch. Replay
0:57

My AI app looked ready to ship. Replay QA proved otherwise. Before launching, I connected the GitHub repo to Replay QA, let it run through the app like a real user, and within a few minutes it surfaced issues I would've never noticed by manually clicking around. What I liked most wasn't just finding bugs. It showed exactly what happened in the browser, explained the likely root cause, and gave enough context to fix the issue without guessing. Instead of running a one-time check, I connected the repo so Replay QA can keep testing every time I push changes or open a PR. No Playwright setup. No complicated pipeline configuration. Just a practical QA gate before users ever find the problems. If you're building with Cursor, Claude Code, Codex, Lovable, Bolt, Replit, or any AI coding workflow, this is worth adding before your next launch. Replay

Kaitee

64,294 Aufrufe • vor 2 Monaten

Out of all the things we've shipped recently, this one is my favorite. Instant feedback from any type of user... → Create a persona that matches your real users and buyers. → An AI agent takes on that persona. → Point it at any url or prototype. → Get feedback in minutes. This is what the Reforge team built and launched today with Synthetic Users. It's way more than bug reports, but actual strategic product feedback. → A First Timer notices your onboarding language is confusing → A Skeptical Buyer questions whether your pricing page builds enough trust → A Power User finds friction in your core workflow that your team stopped noticing months ago Every finding links to a session replay so you can see exactly where things broke down. This isn't a replacement for talking to real users. It's an acceleration layer. Run synthetic studies to catch issues fast, then reserve human research for the decisions that matter most. This is critical as AI accelerates the amount of product teams are shipping. If you don't also develop ways to validate faster, you'll just ship tons of product debt. Lots of features that few customers use but create massive costs.
1:53

Out of all the things we've shipped recently, this one is my favorite. Instant feedback from any type of user... → Create a persona that matches your real users and buyers. → An AI agent takes on that persona. → Point it at any url or prototype. → Get feedback in minutes. This is what the Reforge team built and launched today with Synthetic Users. It's way more than bug reports, but actual strategic product feedback. → A First Timer notices your onboarding language is confusing → A Skeptical Buyer questions whether your pricing page builds enough trust → A Power User finds friction in your core workflow that your team stopped noticing months ago Every finding links to a session replay so you can see exactly where things broke down. This isn't a replacement for talking to real users. It's an acceleration layer. Run synthetic studies to catch issues fast, then reserve human research for the decisions that matter most. This is critical as AI accelerates the amount of product teams are shipping. If you don't also develop ways to validate faster, you'll just ship tons of product debt. Lots of features that few customers use but create massive costs.

Brian Balfour

19,919 Aufrufe • vor 8 Monaten

🎉 Upgrades to replay: You can replay the ENTIRE day's executions in a single click. Calendar > Explore day > Click play > Watch and learn. Your *entire* day - replayed in front of you :) TradesViz's sim, replay, backtesting, anlaysis & AI will be focused on 100% performance improvement. No fluff. No BS features. If you are looking for a professional analytics platform, this is it.
1:18

🎉 Upgrades to replay: You can replay the ENTIRE day's executions in a single click. Calendar > Explore day > Click play > Watch and learn. Your *entire* day - replayed in front of you :) TradesViz's sim, replay, backtesting, anlaysis & AI will be focused on 100% performance improvement. No fluff. No BS features. If you are looking for a professional analytics platform, this is it.

TradesViz | Trading Performance Analysis

12,071 Aufrufe • vor 2 Monaten

Most SEO teams aren't losing because of poor content. They're losing because they don't know what content is missing. I recently used Kuse to analyze a website against its competitors and uncover content opportunities that would have taken hours to find manually. The workflow helped: - Compare a site against competing websites - Surface content gaps across important topics - Identify missing pages and content opportunities - Reveal areas where competitors have stronger coverage - Organize findings into a clear report What normally requires jumping between multiple tools, spreadsheets, and browser tabs became a structured workflow that ran automatically. The interesting part wasn't just the analysis. It was how easy it was to adapt the workflow. Kuse provides workflow templates that can be customized for different use cases, so instead of building automations from scratch, you can start with an existing workflow and tailor it to your needs. And because Kuse connects with thousands of popular tools, the insights can flow directly into the systems your team already uses. AI workflows are most valuable when they help teams spend less time collecting information and more time acting on it. This was a good example of that. If competitor research, SEO analysis, or repetitive reporting is part of your workflow, Kuse is worth exploring. Check it out:
1:08

Most SEO teams aren't losing because of poor content. They're losing because they don't know what content is missing. I recently used Kuse to analyze a website against its competitors and uncover content opportunities that would have taken hours to find manually. The workflow helped: - Compare a site against competing websites - Surface content gaps across important topics - Identify missing pages and content opportunities - Reveal areas where competitors have stronger coverage - Organize findings into a clear report What normally requires jumping between multiple tools, spreadsheets, and browser tabs became a structured workflow that ran automatically. The interesting part wasn't just the analysis. It was how easy it was to adapt the workflow. Kuse provides workflow templates that can be customized for different use cases, so instead of building automations from scratch, you can start with an existing workflow and tailor it to your needs. And because Kuse connects with thousands of popular tools, the insights can flow directly into the systems your team already uses. AI workflows are most valuable when they help teams spend less time collecting information and more time acting on it. This was a good example of that. If competitor research, SEO analysis, or repetitive reporting is part of your workflow, Kuse is worth exploring. Check it out:

Utkarsh Sharma

26,361 Aufrufe • vor 4 Monaten

“i’ve been told that you've tried spending less time on your phone recently, which i believe is a very hard thing to do. what made you do it? and did it actually work?” 🆑: yeah, i am achieving that. then there's a balance to find, because it's also true that as soon as you are... you kind of feel a little bit disconnected on what's going around because today everybody is with a phone, and so there's a balance to find. i did two or three months, i think, without ever touching my phone apart from whatsapp when i was receiving messages and calls, and that was maybe a little bit extreme. so now maybe i'm trying to find a balance between the two because it's good to be up to date with what's going on around the world and to stay in touch with friends and funny moments. there's also lots of funny moments on social media and it part also of social interaction with friends and family. so there's a balance to find, but it is also true that it's a place where sometimes it can be a little bit toxic when you are in a position where people can kind of judge and say anything very, very easily. and they have the right to do so, but as a human being, you can also be affected by looking at those things. so it's a balance to find. i don't know if i found the perfect one, but for now it works for me, which is the most important.
1:22

“i’ve been told that you've tried spending less time on your phone recently, which i believe is a very hard thing to do. what made you do it? and did it actually work?” 🆑: yeah, i am achieving that. then there's a balance to find, because it's also true that as soon as you are... you kind of feel a little bit disconnected on what's going around because today everybody is with a phone, and so there's a balance to find. i did two or three months, i think, without ever touching my phone apart from whatsapp when i was receiving messages and calls, and that was maybe a little bit extreme. so now maybe i'm trying to find a balance between the two because it's good to be up to date with what's going on around the world and to stay in touch with friends and funny moments. there's also lots of funny moments on social media and it part also of social interaction with friends and family. so there's a balance to find, but it is also true that it's a place where sometimes it can be a little bit toxic when you are in a position where people can kind of judge and say anything very, very easily. and they have the right to do so, but as a human being, you can also be affected by looking at those things. so it's a balance to find. i don't know if i found the perfect one, but for now it works for me, which is the most important.

clara

16,542 Aufrufe • vor 3 Monaten

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch
35:25

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

194,698 Aufrufe • vor 6 Monaten

Carlos to Dazn about Liam and the penalty “The liam incident has cost me 10 points today, a possible p5 for the team, is the 4th or 5th time it has happened this season” “You can imagine my frustration, there are pilots which you can drive on parallel on a curve.. a race move i've done for years with checo, fernando, gasly, verstappen, leclerc, piastri.. for some reason we has contact with liam, is not the first time someone on the grid has had contact with liam, it is what it is" "The penalty is incomprehensible, i saw the replay and now i'm going to the stewards so someone can explain to me, as this not only concerns me but it concerts the sport” “The driver from the outside is just a passenger to what the driver in the inside decides to do, leaving you no room and on top of that touching you and on top of that the driver on the outside gets a 10s penalty?? is unheard of and it doesn't make sense” #DutchGP
2:27

Carlos to Dazn about Liam and the penalty “The liam incident has cost me 10 points today, a possible p5 for the team, is the 4th or 5th time it has happened this season” “You can imagine my frustration, there are pilots which you can drive on parallel on a curve.. a race move i've done for years with checo, fernando, gasly, verstappen, leclerc, piastri.. for some reason we has contact with liam, is not the first time someone on the grid has had contact with liam, it is what it is" "The penalty is incomprehensible, i saw the replay and now i'm going to the stewards so someone can explain to me, as this not only concerns me but it concerts the sport” “The driver from the outside is just a passenger to what the driver in the inside decides to do, leaving you no room and on top of that touching you and on top of that the driver on the outside gets a 10s penalty?? is unheard of and it doesn't make sense” #DutchGP

ari

240,386 Aufrufe • vor 1 Jahr

I asked Luke Kornet about his memories from stretches where he was a DNP for many games in a row, and what his message is to the young guys who find themselves in that position now: “It's just a lot of peace to come to life of accepting the position that you're in and then just doing the best with that, versus trying to fight it and want to be in a different one.” “You can spend a lot of time worrying about things that you can't really control. But when you just take the opportunity that you have and do the best with that, you can have days like today where a lot of guys came in and were able to contribute. You can have peace about knowing that you did your job well, just as you did the day before, the day after. It might just look a different way every time. I feel like that's what I've been taught through my life. That's the only thing attitude that you can have that you can actually do something with – versus trying to control things that are outside of what you can control.”
2:15

I asked Luke Kornet about his memories from stretches where he was a DNP for many games in a row, and what his message is to the young guys who find themselves in that position now: “It's just a lot of peace to come to life of accepting the position that you're in and then just doing the best with that, versus trying to fight it and want to be in a different one.” “You can spend a lot of time worrying about things that you can't really control. But when you just take the opportunity that you have and do the best with that, you can have days like today where a lot of guys came in and were able to contribute. You can have peace about knowing that you did your job well, just as you did the day before, the day after. It might just look a different way every time. I feel like that's what I've been taught through my life. That's the only thing attitude that you can have that you can actually do something with – versus trying to control things that are outside of what you can control.”

Noa Dalzell 🏀

48,992 Aufrufe • vor 1 Jahr

We can finally say it! is launching today! We spent a year building the data substrate for the agent economy, one MCP that allows your agents to query the world as a DB, so you can skip the data and focus on building what matters! Cala
1:36

We can finally say it! is launching today! We spent a year building the data substrate for the agent economy, one MCP that allows your agents to query the world as a DB, so you can skip the data and focus on building what matters! Cala

Elisenda Bou-Balust

18,688 Aufrufe • vor 5 Monaten

Every automation expert has shipped a workflow, then found out it broke when the client did. APIs time out. Credentials expire. A node gets a value it wasn't built for. The question was never "will it fail," it's "how fast do I find out." So I built a self-fixing system for n8n. When any workflow fails, Claude Code reads the broken workflow, finds the root cause, and sends me a Slack message with 4 buttons: → Auto Fix: Claude applies the fix it proposed, validates it, and saves → Replay: direct links to re-run a workflow that just hit a temporary glitch → Custom Fix: a form where I type the change in plain English and Claude applies it → Decline: logs the error, changes nothing THE STACK - n8n Error Trigger to catch every failure - Claude Code with the n8n-mcp server for full workflow access - ngrok to connect n8n cloud to my machine - Slack as the approval layer The result: workflows that diagnose and repair themselves while I sleep, with me still approving every change before it goes live. Watch the full video here: The complete PDF guide are linked in the video description, ready to download. You can also drop a comment and I'll send them over. If this is useful, a like, follow, and subscribe goes a long way. Follow for more on building production AI automation. #n8n #Automation #AIAgents #ClaudeAI #BuildInPublic
7:55

Every automation expert has shipped a workflow, then found out it broke when the client did. APIs time out. Credentials expire. A node gets a value it wasn't built for. The question was never "will it fail," it's "how fast do I find out." So I built a self-fixing system for n8n. When any workflow fails, Claude Code reads the broken workflow, finds the root cause, and sends me a Slack message with 4 buttons: → Auto Fix: Claude applies the fix it proposed, validates it, and saves → Replay: direct links to re-run a workflow that just hit a temporary glitch → Custom Fix: a form where I type the change in plain English and Claude applies it → Decline: logs the error, changes nothing THE STACK - n8n Error Trigger to catch every failure - Claude Code with the n8n-mcp server for full workflow access - ngrok to connect n8n cloud to my machine - Slack as the approval layer The result: workflows that diagnose and repair themselves while I sleep, with me still approving every change before it goes live. Watch the full video here: The complete PDF guide are linked in the video description, ready to download. You can also drop a comment and I'll send them over. If this is useful, a like, follow, and subscribe goes a long way. Follow for more on building production AI automation. #n8n #Automation #AIAgents #ClaudeAI #BuildInPublic

Gbenga Akindolani |AI Engineer | Automation Expert

46,436 Aufrufe • vor 4 Monaten

I am more surprised that the ruling on the field in #NOvsBAL was touchdown vs instant replay standing with the on-field ruling. After looking at all the angles in replay, I can't see the football cross the goal line. Plays at the goal line are incredibly hard to overturn because of the obstruction of bodies and the lack of a clear and obvious shot that shows the runner down with the ball visibly short. There is also a clear facemask on Shough, but that aspect of the play is not able to be changed via replay. Incredibly difficult and frustrating play to weigh in on from the booth. This ruling stands regardless of what the ruling on the field is IMO.
1:05

I am more surprised that the ruling on the field in #NOvsBAL was touchdown vs instant replay standing with the on-field ruling. After looking at all the angles in replay, I can't see the football cross the goal line. Plays at the goal line are incredibly hard to overturn because of the obstruction of bodies and the lack of a clear and obvious shot that shows the runner down with the ball visibly short. There is also a clear facemask on Shough, but that aspect of the play is not able to be changed via replay. Incredibly difficult and frustrating play to weigh in on from the booth. This ruling stands regardless of what the ruling on the field is IMO.

Gene Steratore

199,340 Aufrufe • vor 20 Tagen

TradingView can't replay the order book. It can't even rewind. Today, we are releasing Market Replay. In the clip, we replayed yesterday's CPI print release tick by tick. They replay the chart. We replay the market. It allows you to jump back in time and replay every candle, every order book tick, every liquidation, exactly as it happened. Pick any moment from years back. Scrub it like a video. What you will see is exactly what a live trader saw at that second. Here's what's inside: • The full order book, replayed. Rebuilt second by second at tick resolution: walls stacking, getting pulled, getting swept. • A real scrubber. Drag anywhere, both directions, instantly. Pause, step, or play at ten speeds from 0.25x to 30x. • Honest playback. Speed changes how fast you watch, never what happened. • Live data is gated out during replay. Replay is the only thing painting the chart. • 71 indicators replay in sync: CVD, open interest, funding, liquidations, footprint, volume delta, TPO, session profiles, VWAP, long/short ratios, ETF flows, dominance. • Your own scripts replay too, including ones built on orderbook and orderflow data. • Watch candles form: a 4h candle builds update by update, and at tick resolution second by second, with the book moving behind it. • Depth and liquidity readouts show the book as it stood at that moment, not now. • Years of candle and indicator history. Jump with the calendar or click any candle. Add an indicator mid-replay and it joins the timeline.
0:43

TradingView can't replay the order book. It can't even rewind. Today, we are releasing Market Replay. In the clip, we replayed yesterday's CPI print release tick by tick. They replay the chart. We replay the market. It allows you to jump back in time and replay every candle, every order book tick, every liquidation, exactly as it happened. Pick any moment from years back. Scrub it like a video. What you will see is exactly what a live trader saw at that second. Here's what's inside: • The full order book, replayed. Rebuilt second by second at tick resolution: walls stacking, getting pulled, getting swept. • A real scrubber. Drag anywhere, both directions, instantly. Pause, step, or play at ten speeds from 0.25x to 30x. • Honest playback. Speed changes how fast you watch, never what happened. • Live data is gated out during replay. Replay is the only thing painting the chart. • 71 indicators replay in sync: CVD, open interest, funding, liquidations, footprint, volume delta, TPO, session profiles, VWAP, long/short ratios, ETF flows, dominance. • Your own scripts replay too, including ones built on orderbook and orderflow data. • Watch candles form: a 4h candle builds update by update, and at tick resolution second by second, with the book moving behind it. • Depth and liquidity readouts show the book as it stood at that moment, not now. • Years of candle and indicator history. Jump with the calendar or click any candle. Add an indicator mid-replay and it joins the timeline.

OpenMarket

13,630 Aufrufe • vor 2 Monaten

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.
0:22

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

This happened during the Cubs vs Rangers game. A grounder to first and the first baseman throws home to get the out at home plate. Catcher applies the tag, the runner is called safe. Replay clearly shows the runner is out. The Cubs challenge the call and are confident it is going to be overturned. After replay, the runner is called safe! 🤯 How can the replay booth who has every angle in the book at their disposal (not that you needed more than one) botch this call after the umpire just botched it? Do people lose their jobs over this? Have you seen a more terrible call ever in the replay challenge era?
0:36

This happened during the Cubs vs Rangers game. A grounder to first and the first baseman throws home to get the out at home plate. Catcher applies the tag, the runner is called safe. Replay clearly shows the runner is out. The Cubs challenge the call and are confident it is going to be overturned. After replay, the runner is called safe! 🤯 How can the replay booth who has every angle in the book at their disposal (not that you needed more than one) botch this call after the umpire just botched it? Do people lose their jobs over this? Have you seen a more terrible call ever in the replay challenge era?

👉M-Û-R-Č-H👈

2,657,000 Aufrufe • vor 5 Monaten

Pete Carroll says winning championships was never actually the point “It isn’t about winning the championship. It’s not about that. As soon as you win it, it’s over with. It’s in your back pocket. You’ve already done that.” “That’s not the motivator. The motivator is to be the best you can possibly be. That’s ongoing. It never ends. I’m not a big goals guy.” “Goals, you achieve them. To me, I want ongoing, never-ending aspirations of being great at what you’re doing. There is no one game that is the only game. There is no one accomplishment that’s the only accomplishment.” “Can you come back again? Is that really who you are? Is that worth fighting for?” “Can you be true to yourself? Can you really be yourself under all circumstances? No matter what happens, when you get your ass whipped in the freaking Super Bowl, when you had two in a row and you’re two seconds from doing it again, can you come back after that moment and still be who you are?” “That was what the challenge was to me. As hard as that looked, as hard as it felt, and as hard as it was on all the people around me, I took it like this: ‘Okay, you knew this was going to happen sometime.’ ‘Are you going to be the real deal or not?’”
2:21

Pete Carroll says winning championships was never actually the point “It isn’t about winning the championship. It’s not about that. As soon as you win it, it’s over with. It’s in your back pocket. You’ve already done that.” “That’s not the motivator. The motivator is to be the best you can possibly be. That’s ongoing. It never ends. I’m not a big goals guy.” “Goals, you achieve them. To me, I want ongoing, never-ending aspirations of being great at what you’re doing. There is no one game that is the only game. There is no one accomplishment that’s the only accomplishment.” “Can you come back again? Is that really who you are? Is that worth fighting for?” “Can you be true to yourself? Can you really be yourself under all circumstances? No matter what happens, when you get your ass whipped in the freaking Super Bowl, when you had two in a row and you’re two seconds from doing it again, can you come back after that moment and still be who you are?” “That was what the challenge was to me. As hard as that looked, as hard as it felt, and as hard as it was on all the people around me, I took it like this: ‘Okay, you knew this was going to happen sometime.’ ‘Are you going to be the real deal or not?’”

Josh Chambers

414,083 Aufrufe • vor 28 Tagen

This obvious and conclusive evidence which did not overturn the wrong call is getting out of hand in MLB. Detroit Tigers manager A.J. Hinch was ejected after the Tigers lost their challenge on an out call at third base. Just get rid of replay then if you have people in the replay booth that cannot tell an obvious safe or out call. What is MLB even doing? There’s no reason, other than the umpires protecting themselves, for a call like this not to be corrected after review. How do you get it wrong with a replay? Do you think baseball should keep replay or just trash it all together and go back to human error with the umpires and the call is the call?
1:13

This obvious and conclusive evidence which did not overturn the wrong call is getting out of hand in MLB. Detroit Tigers manager A.J. Hinch was ejected after the Tigers lost their challenge on an out call at third base. Just get rid of replay then if you have people in the replay booth that cannot tell an obvious safe or out call. What is MLB even doing? There’s no reason, other than the umpires protecting themselves, for a call like this not to be corrected after review. How do you get it wrong with a replay? Do you think baseball should keep replay or just trash it all together and go back to human error with the umpires and the call is the call?

👉M-Û-R-Č-H👈

72,889 Aufrufe • vor 4 Monaten

I have never build any Chrome Extension in my life. But with AI I was able to build a small extension that I always wanted to build in 1 minute. Prompt to Claude Code: Implement a Chrome extension where when I am on or show an icon for each tweet on my twitter feed to add it to "read me later" list which is maintained on browser storage. The extension should show a button in the top bar and when I click it it should display list of those tweets as one-liners with a button as "Done". When I clicked "Done" that tweet should be removed from the list. Result: 🤩👇
0:31

I have never build any Chrome Extension in my life. But with AI I was able to build a small extension that I always wanted to build in 1 minute. Prompt to Claude Code: Implement a Chrome extension where when I am on or show an icon for each tweet on my twitter feed to add it to "read me later" list which is maintained on browser storage. The extension should show a button in the top bar and when I click it it should display list of those tweets as one-liners with a button as "Done". When I clicked "Done" that tweet should be removed from the list. Result: 🤩👇

Siva

36,612 Aufrufe • vor 7 Monaten

"I always tell those with whom I run this country, that many things are done only in words, feasibility studies, and in meetings. These are things that people go through when it is necessary. But however much you can be good at doing them if it doesn’t lead to tangible changes that impact the lives of people, it is as if you did nothing. There is what we call execution, putting things into action and achieving results because that is your goal in the first place. Those results are what help people; that is what speeds our progress and improves our living standards." President Kagame | Swearing-in of New Minister of Infrastructure. To watch the full speech
1:28

"I always tell those with whom I run this country, that many things are done only in words, feasibility studies, and in meetings. These are things that people go through when it is necessary. But however much you can be good at doing them if it doesn’t lead to tangible changes that impact the lives of people, it is as if you did nothing. There is what we call execution, putting things into action and achieving results because that is your goal in the first place. Those results are what help people; that is what speeds our progress and improves our living standards." President Kagame | Swearing-in of New Minister of Infrastructure. To watch the full speech

Presidency | Rwanda

86,690 Aufrufe • vor 3 Jahren