<p>Hey PH, Ishant from Daemon Labs.<br></p><p>I chose GPU compute over rent. At 20. In college. And I'd do it again.</p><p>While my batchmates were grinding interview prep, I was reading transformer papers at 2am in my hostel room. <br><br>No lab. No funding. Just a bet that AI was the most important thing happening in the world and I needed to be inside it, not watching.<br></p><p>We applied to Founders Inc's Canopy program. Got rejected. I didn't take it. DM'd partners on X. Showed up in their threads with real responses. Sent handwritten letters promising a specific deliverable by demo day. Hours before the program started, we were in.<br></p><p>Same year, my paper on procedural memory in language agents got into the ICLR 2026 MemAgents workshop. Building that benchmark made one thing obvious:<br></p><p>Agents aren't failing because they can't reason. They're failing because the execution layer is a complete disaster.</p><p>Silent crashes. Pixel-dependent clicks that break every software update. Zero structure in the failure signal. Every retry is a gamble. Every demo is a prayer.<br></p><p>That insight became Case. <br><br>A verified procedure runtime for the desktop apps your agent has to drive. Typed calls. Structured failures with retry flags and recovery docs instead of cryptic stack traces. Idempotency labels so retries don't compound bugs.</p><p>Today we're shipping two things:</p><ol><li><p><strong>case-sdk (open source)</strong>: the procedure runtime. Build your own procedures to operate any desktop software. → <a href="https://github.com/DaemonLabsInc/case-sdk" target="_blank" rel="nofollow noopener noreferrer">https://github.com/DaemonLabsInc/case-sdk</a></p></li><li><p><strong>case-api (managed)</strong>: plug-and-play access to our verified, battle-tested procedures. DaVinci Resolve today, more apps shipping soon.</p></li></ol><p>99.6% reliability measured across 51,000 real customer calls. A number you can actually ship to your own customers.<br></p><p>We started with DaVinci Resolve because that's where the pain is loudest. The whole desktop is next.<br></p><p>Everyone from PH gets 50 procedure runs per day, free, for 7 days.</p><p>If you're building agents that touch real software, what's the procedure that's killed your demo? 👇</p>
<p>Hey PH, Pulkit from Daemon Labs.</p><p></p><p>Built Case because we kept hitting the same wall with AI agents. The thinking part was great. The doing part was a mess.</p><p></p><p>A button shifts. A click doesn't register. The agent retries forever. And the workflow that ran clean yesterday just... doesn't today. You end up babysitting the thing instead of trusting it.</p><p></p><p>I didn't take the normal route into this. Spent most of my time deep in systems, infra, and applied AI, the unsexy stuff. And the more I poked at agents, the more obvious it got. The models are smart enough. They've been smart enough for a while. What's missing is everything underneath them actually working when it has to.</p><p></p><p>So we started building Case.</p><p></p><p>Instead of agents fumbling around the screen guessing where to click, Case runs procedures that are structured, typed, and check themselves as they go. They know what app version they're on. They don't break when something moves. They actually finish.</p><p></p><p>Early days. But it's the thing we kept wishing someone would build, so we're building it. 🚀</p>
<p>This sounds wonderful. I am going to try this right now. Congrats on the launch</p>
<p>Hey PH, Mayank from Daemon Labs.</p><p></p><p>With all the hype around computer-use agents and software automation, I started exploring the space myself. And almost everything I saw boiled down to agents taking screenshots and guessing what to click next.</p><p>That felt fundamentally wrong.</p><p></p><p>If a system is meant to automate software reliably, it shouldn’t just look at the screen. It should understand the software, know the available actions, and handle every workflow inside the app.</p><p></p><p>That led us to a simple idea:<br>software automation should run on procedures, not guesses.</p><p></p><p>Instead of treating every interaction like a vision problem, we started building structured procedures for software itself. Reliable flows that know how to operate an application, recover from failures, and execute deterministically.</p><p></p><p>That eventually became Case.</p>
