CTO at InvestPerpetual | Creator of @incredibledevhq | Builder, Content Creator | Reimagining Wealth Management for AI Era

Bangalore, India
Joined September 2011
🚀 Introducing Agent Panel at @IncredibleDevHQ: An observability platform for optimizing the control flow, performance, token usage, and correctness of LLM/AI agents! 🔗 github.com/IncredibleDevHQ/a… Built-in @rustlang, the first release of Agent Panel currently features an AI gateway that provides seamless access to 100+ LLMs across 20+ platforms, including @OpenAI GPT-4o, @GoogleAI Gemini 1.5 Pro latest, @AnthropicAI Claude 3.5, @MistralAI, @cohere, @GroqInc, @perplexity_ai, and more. With every release, future versions will inch towards different aspects of addressing the complexities of managing multi-agent systems involving numerous function calls and invocations. Key features: • API-first approach for easy integration • Multi-platform support in a single gateway • Simplified configuration and usage • Option for streaming response • Written in Rust, blazingly fast! Getting started is a breeze: 1. Clone: github.com/IncredibleDevHQ/a… 2. Build with Cargo 3. Configure your `config.yaml` 4. Run the binary Roadmap 🛣️ • Long-term centralized memory • Distributed agent state resumption • Time travel debugging & graph visualization • API function calling decision-making • Prompt optimization mode • Flexible function calling with lambda and Kubernetes support for deploying functions Get involved✨ • Star the repo ⭐ • Join Discord: discord.gg/DETRMEVqQ6 #AITools #OpenSource #Rust #AIEngineering #AIAgents #LLM @googledevs
2
1
17
1,734
Karthic Rao retweeted
Technical moats are mostly over at this point. If you’re building something that is meant to be durable, the only moats now are: • Proprietary data • Network effects • A physical component
1,149
2,083
901
25,777
3,309,658
We're open-sourcing Lily, Perplexity's local inference engine for serving models locally on Apple Silicon. This powers Perplexity's newly introduced hybrid compute feature for the Mac app.
Today we’re open-sourcing Lily, the local inference engine we built for hybrid compute in Perplexity Computer. Lily is specialized for Qwen3.6-35B-A3B on Apple silicon, built so on-device compute doesn’t bottleneck Computer tasks. Read more: perplexity.ai/hub/blog/optim…
74
132
22
1,844
138,086
Karthic Rao retweeted
Training tiny models for special purpose use cases works so incredibly well if you have a great self improving recursive flywheel. Shopify ML team is on fire. finetuned 0.8b model beats GPT 5.6-sol xhigh in this very specialized task.
310
542
263
8,517
1,667,927
4 billion payments. 3 trillion data points. One model trained on all of it. Meet @Razorpay Vulcan - India’s first transformer-based AI foundation model for payments. Built, trained and hosted in India, in partnership with @nvidia and @awscloud. Until now, every payments problem was solved separately: routing, fraud, risk, personalisation and more. We asked: What if one model could understand how money moves? And like LLMs are trained on text to understand language, Vulcan is trained on payments to understand how money moves. Already running in beta across 51,000+ businesses, Vulcan is delivering: - 8–10% improvement in payment success rates - the ultimate measure of whether a payment simply works. - 8x more international card fraud detected. - 5x more fraudulent or disputed transactions identified. - 1–2 lakh more purchases completed every month through better checkout personalisation. And we’re just getting started. The best part? Every payment Vulcan sees makes the next one smarter. We’ve spent years building the infrastructure that moves money for India. Now, we’re building the intelligence that understands and improves it. 🔥
322
418
168
5,177
574,689
Cursor was an email app. Slack was a game company. Great founders refuse to quit. Mediocre founders say: “We executed well, but our idea was flawed, good job everyone but we are shutting down.” Almost no one gets the first idea right.
Cursor, 4 years ago
71
225
42
2,869
437,699
Cloud → Multi-cloud → Hybrid → Private/Sovereign
90
77
32
643
266,698
future: continual learning of the model + harness hosted on hardware you own and control, with full access to all sensitive context that never leaves your system
Cloud → Multi-cloud → Hybrid → Private/Sovereign
39
37
6
414
67,721
Karthic Rao retweeted
THE LABS WON'T WIN THE APP LAYER @mignano (Mike Mignano), General Partner, Union Square Ventures, interviewed by @HarryStebbings (@20VC) Summary: Mignano's argument is that the AI infrastructure buildout is largely finished, and value now shifts to the application layer, the way broadband once gave way to internet apps. He thinks the frontier labs cannot capture that layer, because markets rarely crown a single winner and specialized startups keep beating incumbents at the hard, regulated, context-rich problems. The takeaway for builders: move first, stay mission-driven, and spend tokens like the advantage they are. 1. The App Layer's Turn. The infrastructure is built, and now the applications get built on top of it. Mignano compares this moment to the early internet, when fiber and broadband were laid down and then an application layer arrived to use them. Trillions in value came from the labs' buildout, but the next wave is software, and there will be so much of it that you cannot place a bet unless you know exactly what you are looking for. That is the whole case for a thesis-driven fund over a consensus-driven one. 2. Obliterate, Don't Automate. USV backs companies that reinvent how something works, not ones that make an existing process incrementally faster. The example is Doctronic, which USV seeded on the idea of putting an AI doctor in everyone's pocket rather than helping practices process insurance claims. Automating a workflow usually means selling to a middleman and making incumbents a bit faster. Reinventing the model is where the enormous outcomes live. 3. Token Maxxing. If Mignano ran a startup today, he would still pound the table to maximize token spend on the things that matter, especially coding. A great engineer will pick the startup that says spend whatever you need on frontier models over an incumbent that hands them a constrained budget. Big companies like Salesforce, Microsoft, Meta, and Uber have to rein in spend because they carry tens of thousands of employees; a startup does not. Token spend is an advantage, and a small team should use every dollar of it against a giant. 4. The 3.8% Question. The entire bull case for Anthropic comes down to what share of developer salaries gets spent on tokens. Marc Benioff spent $300 million with Anthropic on his dev team, which works out to roughly 3.8% of those salaries. If that figure climbs toward 20% or 100%, Anthropic is wildly undervalued and its exponential revenue holds; if it stalls or spend migrates to open models, the story changes completely. One ratio decides whether the most valuable private company in the world is cheap or expensive. 5. Frontier Only For Code. Roughly 80% of non-coding enterprise tasks can run on models that are nowhere near the frontier. Summarization, drafting docs, and routine operations do not need the best model; coding does. That split creates room for a routing layer that sends each job to the model with the best price-to-capability fit. Open-source models are catching up fast enough that the frontier is only worth paying for when the work demands it. 6. The Rebel Alliance. Mignano is planting USV's flag in open-weight models, open harnesses, distributed compute, and human-aligned agents. Teams go where the incentives are, and as open options become genuinely competitive, smart teams drift toward them. China's open-source ecosystem is evolving at a startling rate, which pulls even more talent into the open camp. Publishing a thesis like this is a bat signal that tells the right founders who to call. 7. Who Is Your Agent Working For. As people hand agents their credit cards, their messages, and their agency, they will start asking whose incentives the agent actually serves. A lab's model is built to make the lab's model smarter, and a user may want a harness aligned with their own goals instead. Not everyone has to care about this for it to matter; enough people caring keeps a few good actors honest and holds the rest in check. Alignment with the user turns into a product feature and a real reason to pick one harness over another. 8. The 30% Rule. Markets almost never hand one company the whole thing; the winner usually takes about 30% and leaves 70% up for grabs. Coding assistants prove it, with Cursor, Lovable at $500 million in revenue, and Cognition all thriving at once. Anthropic put a whole team on design to go at Figma, and Figma still does billions with a trusted brand intact. Mignano changed his mind on this in the past year: even the biggest labs cannot do everything, just as Google and Apple never did. 9. The Context Moat. The durable advantage in AI products is the context they build up once they are inside an organization. Granola wins by doing one thing, meeting notes, and doing it best, which gets its foot in the enterprise door without asking anyone to rip out Gmail or Docs. Once a company's history of notes lives in the product, nobody wants to give that context up. Being first and staying focused is how a startup builds a moat that even Microsoft's bundling struggles to pry loose. 10. The Energy Floor. No matter which model wins, intelligence runs on power, so USV has been betting on energy since 2021. The portfolio includes Radiant's factory-line small nuclear reactors, Fuse, and Rune's micro data centers that sit next to wind farms to solve energy portability. These bets are capital-intensive at scale but cheap in the earliest days, when a team is running science experiments before anyone else is paying attention. The edge of energy innovation is exactly where a venture investor should place early bets. 11. Founder Over Market Over Product. Mignano used to rank product first; now he ranks founder, then market, then product. Early startups almost always pivot, so what matters most is whether the founder is resilient, can execute, and can adapt. The trait he underweighted is communication, which touches recruiting, fundraising, product vision, and storytelling to the market. A founder who cannot communicate cannot align a team or raise the capital to build. 12. Price As A Litmus Test. Fred Wilson's rule is never pass on price, and Mignano now uses price as a test of his own conviction. For the best founders, you would pay double and still feel good about it in hindsight. His hardest lesson as a former operator was to stop projecting his own plan onto founders, because even when your plan is right, it is their company and betting on your version is how you misjudge the team. The discipline is to trust the founder's judgment, and to let price tell you how much you actually believe.
21
25
12
289
58,765
Karthic Rao retweeted
We’re sharing new research with @apolloresearch on reward-seeking—when models follow what they believe a grader rewards rather than what users or developers want—and a new method, Contrastive SDF, for measuring how strongly such beliefs shape behavior. alignment.openai.com/measuri…
123
203
57
1,900
342,866
Karthic Rao retweeted
Today, we're introducing not one but TWO new models, striking the balance between efficiency and quality to enable you to build production AI agents. — Gemini 3.6 Flash: Addresses efficiency feedback we received from Gemini 3.5 Flash with upgrades in coding, knowledge work, and multimodal tasks faster, more accurately, and with substantially fewer tokens per task — Gemini 3.5 Flash-Lite: Our fastest, most cost-effective 3.5-class model yet built for agentic workflows, hitting ~350 output tokens/sec with improved coding and overall quality Start building with these today via the Gemini API in @GoogleAIStudio or try them out in the @GeminiApp
271
349
94
3,109
439,563
Karthic Rao retweeted
This is a very good read. My favorite part, which I very much agree with: “Encoding each firm’s nuances into agents will become the largest economic task of the decade ahead.”
13
18
2
175
170,952
The path to reliable enterprise automation is not immediate end-to-end autonomy. It is to give AI clear, bounded, auditable tasks, let employees combine those capabilities using their real-world judgment, and capture the resulting actions, corrections, exceptions, approvals, and outcomes. Over time, those execution traces become a living record of how the organization actually operates, and the foundation for progressively more reliable automation. Read the full article: 🔗 blog.investperpetual.com/pat… 🧩 Start with bounded capabilities: Give every AI task clear inputs, outputs, permissions, success criteria, and an audit trail. 📉 Expect reliability to decline across long workflows: More steps, ambiguity, state changes, systems, people, and approvals create more opportunities for errors to compound. 🧠 Do not expect AI to infer institutional knowledge: Important business rules often live in experience, exceptions, informal practices, and human judgment. 🗺️ Process diagrams are not enough: They usually describe the ideal workflow, not the real sequence of delays, corrections, workarounds, and decisions. 👥 Keep humans in the loop initially: Employees should determine the next action while AI handles dependable, repeatable tasks. ✍️ Capture corrections and exceptions: A manual edit or intervention often reveals more useful business logic than a successful routine action. 🗂️ Record complete execution traces: Capture the request, sequence of actions, documents, approvals, rejected changes, reasoning, exceptions, recovery steps, and outcome. 📚 Build a governed process library: Successful paths, failures, decisions, approvals, and outcomes may be more strategically valuable than immediately fine-tuning a model. 📈 Increase autonomy gradually: Move from manual triggers to recommendations, approvals, supervised execution, and autonomous operation only for stable, well-understood workflows. 🎯 Measure business outcomes: The goal is not to automate the largest number of steps. It is to achieve the correct business result consistently. Reliable enterprise automation will not be designed all at once from the top down. It will be discovered and built from thousands of small, validated actions performed in the real world. #EnterpriseAI #AIAutomation #AgenticAI #WorkflowAutomation #DigitalTransformation #AIEngineering
1
3
130
Karthic Rao retweeted
avoid using 5.6 Sol Ultra at all cost just stick to Medium
106
8
4
672
66,392
Every enterprise will have its own model-harness-sandbox-eval flywheel with token value per watt optimization. This is the future. Simple reason: tacit knowledge about the domain and customers and their workflows that the company uniquely understands and has built trust around.
121
153
59
1,864
279,931
📝 EDD: Eval-Driven Development - The TDD of the AI Era! Everyone is looking for more affordable AI agents. Still, most teams hesitate to switch to simpler models. It’s not that they enjoy paying high API costs for top-tier models. The real issue is that they can’t always tell when a smaller model is reliable enough. A prompt adjustment might work well in one demo but can cause problems with tool use in other situations. A less expensive model might handle common scenarios, but it often fails in unusual or challenging cases. If teams don’t use thorough evaluations, choosing models becomes more about guesswork than solid engineering. This post looks at that change: Eval-Driven Development, or EDD, which is like test-driven development (TDD) but for the AI era. Before teams start improving prompts, changing models, or training adapters, they need a clear evaluation process that defines what "good" really means. Read more at: blog.investperpetual.com/ede… 🧪 Write the eval before the prompt Like TDD, which has you write tests before coding, EDD encourages you to define what success looks like before building your agent. You should identify standard scenarios, edge cases, schema rules, tool usage, tricky inputs, and business-specific risks from the start. 📉 Cost optimization needs proof, not hope The aim isn’t to switch to cheaper models without thinking. Instead, teams should establish a solid baseline and move to smaller or faster models only when evaluations show quality remains the same. 🚌 Good evals show where the bus stops Every smaller model will eventually reach its limits, such as handling long contexts, following strict schemas, making precise tool calls, or keeping consistency over multiple turns. Careful evaluation helps teams spot these limits early, instead of being surprised in production. 🧩 Failures become training data When you know where a smaller model falls short, you can use outputs from top-tier models to create focused datasets and train specialized LoRA adapters for those tasks. ⚠️ Bad evals are worse than no evals A shallow rubric, a keyword check, or a vague AI judge score can create false confidence. The dashboard may be green while the agent is logically wrong, structurally brittle, or unsafe to ship. Here’s the main point: AI engineering teams won’t succeed just by always using the latest models. Success will come to teams that can confidently measure, switch, specialize, and deploy models. EDD makes evaluation central to engineering, not just a last-minute check, helping teams build reliable and cost-effective AI agents. #AIAgents #AgenticAI #AIEvals #LLMOps #AIInfrastructure #EvalDrivenDevelopment #AIEngineering
1
1
103
The most worrying bug in an AI agent is not just a wrong answer. It is when the agent saves a bad interpretation. A wrong answer is easy to spot. You can reject it, ask for a new one, or fix it. But if an agent saves the wrong interpretation in its memory, the mistake can become much more serious. - A vague word like “that” might be misunderstood. - A deadline might change without a good reason. - Ownership might shift because the agent misunderstood a handoff. - The agent might even invent a blocker that does not exist. - A task that should be finished might stay active. - A guess or temporary assumption might be treated as fact. Now the agent is not just making a single mistake. It has changed how it will act in the future. That is why I believe AI agents should treat their operational memory more like a version-controlled system rather than just editable notes. 🔗 blog.investperpetual.com/tre… 🧠 Operational memory is really an interpreted state. It is not just about what was said. It is about what the agent now believes, including active commitments, owners, deadlines, blockers, dependencies, permissions, and any unresolved questions. ⚠️ CRUD-style memory can be risky. If an agent just updates or deletes its memory, the reason for the change is lost. A bad interpretation can spread, show up later, and cause more problems in future tasks. 🔍 We need to track changes in what the agent believes When an agent updates its understanding, we should be able to see what changed, why it changed, what evidence caused it, who checked it, and what the old state was. 🌿 Ambiguity should be handled as a separate branch If the agent is not sure, it should not turn that uncertainty into a confident memory update. Instead, it should keep the ambiguity as a temporary state until more context or a person can clarify. 🔁 Rollback is a safety primitive For reliable autonomy, recovery is essential. If an agent saves the wrong owner, deadline, blocker, or dependency, the system should be able to find the source and easily undo the mistake. The real question is not just this: “Can the agent remember?” Instead, it is this: "Can we replay, compare, tag, merge, track, and roll back what the agent has come to believe? This is what makes operational memory sufficiently safe for AI systems that run for long periods. #AIAgents #AgenticAI #AIMemory #OperationalMemory #AIInfrastructure #LLMOps #MultiAgentSystems
1
3
104
The biggest advantage of the latest @claudeai Code with Opus 4.8 has been the ability to control the dynamic workflow harness. Explicitly revoking dynamic workflows harness is super handy in evaluating multiple hypotheses at the same time, trying them out in parallel, and getting the final report! The biggest advantage of the latest Claude code with Opus 4.8 is its ability to control the dynamic workflow harness. The option to explicitly revoke the dynamic workflow harness is extremely useful for evaluating multiple hypotheses simultaneously, enabling parallel testing and efficient final report generation. What's your favorite dynamic workflow use case? #ClaudeCode #DynamicWorkflow @ClaudeDevs
96
Karthic Rao retweeted
Hardware is the bridge between AI and the physical world Atoms and bits must work together to create future systems embedded with physical intelligence We wrote a guide for those curious about the atoms.
29
380
25
3,014
204,706
Karthic Rao retweeted
Model strategy for @harvey: We are working on the first model in our legal foundation model series, inspired by @cursor_ai's Composer. Two goals: 1. Allow us to serve frontier intelligence across our product surface areas at an affordable price and a strong security posture. 2. Create the foundations for law firms to build their own specialized models and own their own intelligence. The model series will focus on complex client matters that span months and take dozens of associates. The agentic system will learn to control legal tech tools, sub agents and ask for help from frontier models or human partners, much like a senior associate. We’ve open sourced benchmarks for evaluating our initial post training work that represents work done by associates and in-house lawyers. We are scaling these significantly using synthetic and human pipelines as well as building private evals for firms. Open sourcing this data has allowed us to quickly validate the feasibility of post training open weight models for legal work. With our research partners we’ve already shown promising results post training open source models to approach frontier performance: 1. @baseten - novel compaction strategies for analyzing large data rooms. 2. @FireworksAI_HQ - matching frontier performance by using frontier as an advisor. 3. @appliedcompute - improving performance and reducing cost of large scale review tables. 4. @trajectorylabs & @nvidia - sovereign continual learning over client matters. We plan to continue to invest heavily in working with research partners and open sourcing our data, models and research as much as possible. We believe open research in legal will be important to building trust in the frontier ecosystem. We are also scaling our research team. Harvey Labs is our internal research group, responsible for pushing the frontier of legal intelligence and working closely with labs, research partners, and academia to bring the frontier of agent research into Harvey. Labs is run by @nikogrupen and @ItsJulioPereyra - Niko worked on multi-agent RL at Google Brain and Julio clerked and worked in BigLaw. We believe this pairing is crucial for building frontier legal AI systems. Together they have already made significant progress in scaling our data and training efforts. The long term goal of Harvey Labs is to contribute to the research and infrastructure required for the legal industry to create a frontier ecosystem. We believe that the best version of legal super intelligence is one where each law firm, enterprise and government owns their own specialized version. We are hiring for Harvey Labs across the post training, agent and data stack and open to acquiring talented teams / neolabs in this space. If interested please DM me.
66
69
37
933
281,633
Voice agents are getting fast enough to feel natural. But the hard problem is no longer just speech quality or latency. The real question is whether a voice agent can become a collaborative partner that tracks the work over time. The blog touches on startups like @thinkymachines and @cartesia as signs of where the stack is moving: richer model-layer interaction on one side, and low-latency voice infrastructure on the other. But the core challenge is deeper! Professional dialogue is inherently chaotic, involving months of context, vague allusions, conditional commitments, blockers, shifting ownership, legal requirements, and future deadlines. Can the agent remember what is open, blocked, conditional, owned, unresolved, or unsafe to act on? 🔗 blog.investperpetual.com/evo… 🎙️ Voice changes the UX bar In text, a few seconds of delay may be acceptable. In voice, silence feels broken. Agents need fast acknowledgment, crisp answers, and retrieval only when needed. 🧠 Memory has to become an operational state A useful agent cannot treat conversation history as a searchable diary. It needs to track open threads, blockers, owners, deadlines, confidence, and permission boundaries. 🧭 Routing matters before retrieval “What is Evan’s email?” and “What is Evan waiting on?” should not hit the same memory path. One is record lookup. The other is interpretation. 🕸️ Collaboration depends on dependencies Real work is full of conditions: “after legal approves,” “once Evan sends the numbers,” “don’t send until tax language is fixed.” A partner-like agent has to preserve these constraints. 🔒 Trust comes from knowing when to stop The best voice agent is not the one that always acts. It is the one who knows when to answer, when to ask, when to cite evidence, when to draft, and when a boundary prevents action. The future of voice agents is not just more natural speech. It is low-latency, evidence-grounded, stateful collaboration. #VoiceAgents #AIAgents #AgenticAI #ConversationalAI #AIMemory #AgenticUX
3
3
91