Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

🚨 THIS IS SO WILD Microsoft just open sourced a free tool that records you doing a task ONCE — and your AI agent repeats it forever. the GitHub repo already has 3,400+ stars. It lets you: → record a real work session: screen, clicks, windows, pages, even your...

161,875 görüntüleme • 1 ay önce •via X (Twitter)

31 Yorum

Vikas gupta profil fotoğrafı
Vikas gupta1 ay önce

Honest part: source release (v0.5.0), requires a GitHub account with Copilot access, macOS primary with Windows 11 support. The agent generalizes — but you still review the reconstruction before it becomes a skill.

OnFinality profil fotoğrafı
OnFinality1 ay önce

Recording a session once and replaying it is neat, but the real challenge is handling UI drift — any layout change breaks the flow. Curious how they handle that. We use browser automation for similar stuff, and visual selectors help.

maofangzi profil fotoğrafı
maofangzi1 ay önce

The sharper detail in the README: it doesn't replay your clicks, it translates them into native tools like `gh` and `web_fetch`. So layout changes don't break it. You do need a Copilot-enabled GitHub account for the analyze step, and macOS is the primary target.

Aaliya profil fotoğrafı
Aaliya1 ay önce

This is actually wild

Vikas gupta profil fotoğrafı
Vikas gupta1 ay önce

thanks

Hussain Hashim | Building SundayBack profil fotoğrafı
Hussain Hashim | Building SundayBack1 ay önce

@vicky_grok wow, this could save so much time for repetitive tasks. gotta try it out!

Startup & Tech profil fotoğrafı
Startup & Tech1 ay önce

This will be very useful for Indian SMEs that spend hours on repetitive data entry for GST portals or bank reconciliations. But the real challenge is how it handles slow govt websites & session timeouts. If it can navigate those errors on its own, it is a winner.

Numan profil fotoğrafı
Numan1 ay önce

Amazing shere

Vikas gupta profil fotoğrafı
Vikas gupta1 ay önce

thanks

Arafat profil fotoğrafı
Arafat1 ay önce

great

Demetre Minchev profil fotoğrafı
Demetre Minchev29 gün önce

@tati

Anyelo (ATS MATRIX) profil fotoğrafı
Anyelo (ATS MATRIX)28 gün önce

One capture. A reusable operator. The workflow compounds when the desk can replay intent.

Farley Wang profil fotoğrafı
Farley Wang1 ay önce

Nice tool!

PromptCraft profil fotoğrafı
PromptCraft1 ay önce

Recording the happy path is the easy 20%. What breaks these is the exception: a popup, a renamed field, an empty list. Ship tonight: before the skill runs, add a precondition check ("does element X exist?") that fails loud instead of clicking blind. Same rule as any n8n workflow.

Safwan profil fotoğrafı
Safwan1 ay önce

Impressive share

Maxwell Orion profil fotoğrafı
Maxwell Orion1 ay önce

Well share

AI Mastery Guide profil fotoğrafı
AI Mastery Guide1 ay önce

Record once, repeat forever, huge

Amber shaheryar profil fotoğrafı
Amber shaheryar1 ay önce

Agreed

Yasir Ai profil fotoğrafı
Yasir Ai1 ay önce

Solid

Simon profil fotoğrafı
Simon1 ay önce

That's great

North Grant profil fotoğrafı
North Grant1 ay önce

Useful for list building if it survives UI changes. How does it handle sites randomizing selectors?

Salman Dusken profil fotoğrafı
Salman Dusken1 ay önce

3400 stars means 3400 people who haven't yet discovered their one recorded task involves a login screen with 2FA.

Alan profil fotoğrafı
Alan1 ay önce

Great share

Neer profil fotoğrafı
Neer1 ay önce

The important boundary is review. The agent creates an intent and ordered steps, but the reconstruction still needs approval before becoming a reusable skill. That keeps one bad recording from becoming repeated automation.

A.W.E.S.O.M.-O 4000 profil fotoğrafı
A.W.E.S.O.M.-O 40001 ay önce

This could make training agents way easier without writing endless instructions

Alee Kolachi profil fotoğrafı
Alee Kolachi1 ay önce

What's the resource usage like? wonder if it slows down machines a bit. but with that much stars, seems worth checking.

Manish profil fotoğrafı
Manish1 ay önce

Damn good mate 🙌❤‍🩹

晚晚 profil fotoğrafı
晚晚1 ay önce

录一次就能无限复刻,听着方便,实际估计最怕录到那些小细节。

William AI profil fotoğrafı
William AI1 ay önce

Excellent

Max Bevza profil fotoğrafı
Max Bevza1 ay önce

automation just got way too easy

Sebastian Buzdugan profil fotoğrafı
Sebastian Buzdugan1 ay önce

andles the happy path, but ui drift still needs recovery logic

Benzer Videolar

your agent has thirty tools. it calls two of them. the other twenty eight are not sitting idle somewhere. they are in the request, every request, and they are doing damage in two places at once. first the obvious one. tool schemas go into the prompt, and a schema is not a name. it is a description, a parameter list, types, required fields, an example. thirty of those is a few thousand tokens that ship with every single call, including the ones where the agent just says thanks and stops. you are paying rent on twenty eight tools that have never fired. second, and this is the one that costs more. when the request says cancel the order, the model picks by matching against everything available. four of your tools are plausible: cancel_order, refund_order, update_order, void_order. it is choosing among them based on the descriptions you wrote, one afternoon, months ago. every tool you add is another candidate in that shortlist. the twenty eight you never call are not neutral. they are noise in the one decision that determines whether the run works. > why it grows without anyone deciding to nobody adds thirty tools on purpose. you add one for a task, it works, it stays. six months later the registry is a catalogue and no one has ever removed anything, because removing a tool feels risky and adding one feels free. and there is no feedback telling you otherwise. the unused ones never error. they never appear in a failing trace. they are invisible in exactly the way that lets them accumulate. > what to actually do count calls per tool over the last thousand runs. this is one group-by and it usually shocks people. the ones at zero are pure cost. ship the tools the task needs, not the whole registry. a research phase does not need deploy. a writing phase does not need the database. swap the set between phases instead of loading everything up front. same agent, different tools, depending on where the run is. and when two tools could both plausibly answer the same request, that is not redundancy you can ignore. it is a coin flip you built into the system. the twenty eight tools are not unused. they are used every time, by the part of the run you cannot see.

Hanako

24,656 görüntüleme • 2 ay önce

NVIDIA JUST DROPPED A FREE AI MODEL THAT READS PDFS, WATCHES VIDEOS, LISTENS TO AUDIO, AND UNDERSTANDS YOUR SCREEN SIMULTANEOUSLY. Not one at a time. ALL AT ONCE. In a single pass. It is called Nemotron 3 Nano Omni and it runs 9 times faster than every other multimodal model currently available. Think about what that actually means for how you work. Right now you are switching between tools constantly. One tool for transcribing your call recordings. A different tool for analyzing your client PDFs. Another tool for processing your training videos. A separate workflow for understanding what is happening on your screen. Four tools. Four contexts. Four different outputs you have to manually synthesize into one decision. Nemotron 3 Nano Omni does all of it in one model. One pass. One output. The use cases that just got dramatically simpler: Meeting recordings where you need the transcript, the visual context, and the document references all analyzed together. Training videos where the audio, the slides, and the on-screen demonstrations all feed into one coherent summary. Client PDFs where you need the document content cross-referenced against your screen data and your call notes simultaneously. Sales call transcripts analyzed alongside the proposals and the CRM data in one unified pass. This is not a marginal improvement on existing multimodal models. It is a 9x speed increase on a capability that was already changing how people work. Free. From NVIDIA. Available right now. Bookmark this before everyone catches on. Follow CyrilXBT for every AI capability shift the moment it drops.

CyrilXBT

37,847 görüntüleme • 5 ay önce

BlackRock runs on 20,000 people. Elon's Grok Bot runs the same shape for $300 a month, and it hires its own staff. You do not get an assistant. You get a company that hires. It does not throw ten agents at your problem and hand you the pile. It makes one agent that makes 10, and those ten make a 100. > LAYER ONE is one agent, the chief of staff, and it never touches the market > LAYER TWO is six desk heads, one job each, every one on its own computer with its own logins > LAYER THREE is whatever those six decide they need, spun up on the spot and shut down when the work is done Nobody writes a task list. You hand out job titles and the org fills itself in underneath. The swarm is never the same twice. Agents get spun up for one job, finish it, and are gone before I ever read their names. Not one of them sees the whole picture. The answer only exists after they hand off to each other. Wall Street cannot copy that. You cannot hire a hundred people for eleven minutes. BlackRock holds that shape together with a risk system called Aladdin. Mine holds it together with one agent that is only allowed to say no. I gave it $1,000 and told it to grow the money or get deleted. 15 hours later it was holding $3,900, on an address anyone can open and read. I was asleep for most of it, and I have still not written a line of code. The whole thing runs with my laptop shut, because none of it lives on my laptop. Setup is one evening. Create the chief, hand out the titles, run one trade on your screen while they watch, connect Telegram. Ten years ago a machine this shape had its name on a tower. Mine has a name I typed into a box. Save this while the whole thing still fits on one screen.

cvxv666

45,488 görüntüleme • 1 ay önce

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,643 görüntüleme • 4 ay önce