Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

An AI operating system. A cloud worker that runs 24/7. Those are the two ways warmwind describes itself and both are literal, not marketing language. It’s a vision model that sees your screen and operates software the way you would: clicking, typing, navigating fully in the cloud, nothing to...

14,274 Aufrufe • vor 16 Tagen •via X (Twitter)

28 Kommentare

Profilbild von warmwind
warmwindvor 16 Tagen

let´s go

Profilbild von Liam Holt
Liam Holtvor 16 Tagen

@warmwind_OS This is a practical take on automation. An AI that actually sees the screen and runs workflows in the cloud, without installs or APIs, is more useful than another chatbot. Worth trying the trial while slots are open.

Profilbild von Kaizen 黒
Kaizen 黒vor 16 Tagen

@warmwind_OS Excellent

Profilbild von Javeriya Ahsan
Javeriya Ahsanvor 16 Tagen

@warmwind_OS An AI that actually uses the mouse instead of just talking about work.

Profilbild von Web_Technify
Web_Technifyvor 15 Tagen

@warmwind_OS That’s a serious leap for AI agents.

Profilbild von Subhan Qureshi
Subhan Qureshivor 16 Tagen

@warmwind_OS The effort behind this deserves appreciation. Keep up the great work!

Profilbild von Mimu | AI Tools & News
Mimu | AI Tools & Newsvor 16 Tagen

@warmwind_OS Amazing share , it’s really working and also helpful for automate your everyday workflow

Profilbild von Paul Sims
Paul Simsvor 15 Tagen

@warmwind_OS Amazing Share

Profilbild von Tips Excel | AI Productivity
Tips Excel | AI Productivityvor 16 Tagen

@warmwind_OS its good

Profilbild von Jara
Jaravor 16 Tagen

@warmwind_OS Great

Profilbild von Kaizen 黒
Kaizen 黒vor 16 Tagen

@warmwind_OS This is a practical take - an AI that actually sees the screen and runs the workflow in the cloud, instead of just talking about the task or waiting on APIs. Worth trying the trial while slots are still open.

Profilbild von Nihan
Nihanvor 16 Tagen

@warmwind_OS Excellent Share

Profilbild von Elyra Future Tech
Elyra Future Techvor 16 Tagen

@warmwind_OS Solid concept. An AI that actually sees the screen and runs workflows in the cloud, without APIs or installs, is more useful than another chatbot. Worth trying the trial if slots are still open.

Profilbild von AI Mastery Guide
AI Mastery Guidevor 15 Tagen

@warmwind_OS Cloud worker never clocking out

Profilbild von SantrexAI
SantrexAIvor 16 Tagen

@warmwind_OS that's great

Profilbild von James
Jamesvor 15 Tagen

@warmwind_OS This sounds amazing! I'm excited to try out this new operating system.

Profilbild von Vinay Bharambe
Vinay Bharambevor 16 Tagen

@warmwind_OS Wow really amezing Share

Profilbild von Jessica AI
Jessica AIvor 16 Tagen

@warmwind_OS Awesome post

Profilbild von Safwan
Safwanvor 16 Tagen

@warmwind_OS Nice post

Profilbild von Mr. Jason💡
Mr. Jason💡vor 15 Tagen

@warmwind_OS Wow so helpful share

Profilbild von Zayden Tech
Zayden Techvor 15 Tagen

@warmwind_OS Impressive share

Profilbild von Liam | AI Tools & News
Liam | AI Tools & Newsvor 16 Tagen

@warmwind_OS Amazing

Profilbild von David
Davidvor 16 Tagen

@warmwind_OS Gran herramienta

Profilbild von Ryan Carter
Ryan Cartervor 16 Tagen

@warmwind_OS Thanks for sharing

Profilbild von Zakir Hossain
Zakir Hossainvor 15 Tagen

@warmwind_OS Great share

Profilbild von sporsho
sporshovor 15 Tagen

@warmwind_OS That's great

Profilbild von Genius💡💹🧲 🤖
Genius💡💹🧲 🤖vor 16 Tagen

@warmwind_OS Vision models operating software like humans feels like a massive unlock

Profilbild von Ayzaa
Ayzaavor 16 Tagen

@warmwind_OS Amazing

Ähnliche Videos

watch this anon. i gave NVIDIA's biggest model ever a single task. 100 minutes and 440,000 tokens later, it had rendered nothing. not one important thing on the screen. this is Nemotron 3 Ultra. 550 billion parameters, a hybrid Mamba Transformer MoE, the largest model NVIDIA has ever shipped, and they built it specifically for long-running agentic coding. so i handed it exactly that: build a 3D scene from a spec, multiple files, iterate until the tests pass. the same task a frontier model one shotted in minutes. i genuinely wanted to be impressed. it ran for an hour and forty. burned through 440,000 tokens. wrote every file, passed its own tests, and proudly printed "task complete."the browser was blank. the 3D scene never rendered. not once. and the long horizon agentic behavior was genuinely good. it stayed on task the whole hour and forty, wrote real multi-file code, drove its own tools without derailing. it just couldn't turn any of that into something that actually runs. here's the part that gets me. it's a text model, it cannot see its own output. so it sat there looping on a broken vision tool, trying to "look" at the page, hitting error after error, never once reasoning its way out. it declared victory on an empty screen because it had no way to know the screen was empty. to be fair, i genuinely don't know what quant the NIM was serving, so maybe some of that's on the serving, not the model. but the biggest model NVIDIA has ever made, on the exact task it was designed for, couldn't tell it had built nothing in 100 minutes. same task on a local model, below thread👇.

Sudo su

32,589 Aufrufe • vor 2 Monaten

Marketing agents are the NEW coding agents. It's code in the cloud that makes decisions off your live business data on a loop. It researches, acts, reads the results, improves, and goes again. Picture an agent that runs your entire Facebook ad account by itself. It researches your customer's pain points, generates on-brand creative, publishes it, kills the losers, scales the winners, and makes more of whatever's working. We show you the EXACT stack. Perplexity to scrape Reddit for real pain points, Nano Banana for on-brand static creative, a vision model to check it against brand guidelines, HeyGen for AI UGC video, all wired into a loop that reads Facebook's data and reacts. Now point it at a business. What are some startup ideas you can point marketing agents to? WordPress runs 43% of the internet. Take the plugins people already pay for, like Yoast, WooCommerce, and WP Forms, and build the AI-first version of each. Examples: Yoast (~$15M ARR) shows you red and green dots and tells you to fix your SEO yourself. The AI version just does it. Proven demand, no AI-native competition, and thousands of site owner pay agenices $1,000 a month and many wish they'd pay less and got more. Coding agents changed who gets to build software. Marketing agents change who gets to grow a company. Full breakdown on The Startup Ideas Podcast (SIP) 🧃. Thanks to Cody Schneider for the sauce. Will break down more marketing agents if people are interested? Just LMK. Watch. I'm rooting for you and happy growing. I think we've heard a lot about coding agents recently. And we're about to hear a lot more about marketing agents.

GREG ISENBERG

132,662 Aufrufe • vor 1 Monat

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!

dom | icp

310,509 Aufrufe • vor 4 Monaten