Prasenjit Sarkar

10.3K posts

Prasenjit Sarkar banner
Prasenjit Sarkar

Prasenjit Sarkar

@stretchcloud

Founder & Builder | Building https://t.co/ag2bhjo5r8, https://t.co/9EO3BU4jCx, https://t.co/vqTghjn5bf | AI Agents| 15x Patents | 7x Author | Building for Growth

London, England Katılım Mart 2011
954 Takip Edilen2.4K Takipçiler
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
For the first few years of the agentic SDK wave, Python was conspicuously absent. Vercel's AI SDK shipped in 2023 as a JavaScript-first toolkit for LLM-powered apps. TypeScript was the language of the Next.js ecosystem and most of the early AI app layer built on top of it. Python developers who wanted the same streaming primitives, tool call routing, and agent loop abstractions were writing their own or piecing together LangChain. Vercel just dropped the AI SDK for Python in public beta. The underlying SDK (github.com/vercel-labs/ai…) wraps streaming in an agent loop that handles tool dispatch, message history, loop control, and async tool execution. AI SDK 6, released this year, added a full Agent abstraction so you define your agent once with model, instructions, and tools, and use it across your application. What this reflects is something I keep seeing across the developer tools category: the JavaScript-only phase of any platform ends when the backend and data science community gets serious enough about the use case. FastAPI overtook Express for API infrastructure. PyTorch won the research-to-production pipeline over TensorFlow's JavaScript experiments. Python's share of the agentic infra stack is going to look very different in 18 months. Vercel is not late to this shift. They're actually early, given where most production ML and data pipelines still live. x.com/morganlinton/s…
Morgan@morganlinton

Sooo...Vercel just dropped a Python version of their AI SDK, and I'm a big Python fan...so just couldn't help myself this morning 🐍 Had to build a little agent with it, here's what it does: describe your startup idea, it brainstorms domain names and checks real availability live against registry RDAP servers, then keeps iterating until it finds names you can actually register. Feel like my buddy @gregisenberg would probably dig this one! Like most fun things I whip up, free and open source, no sign up, no payment, fork it, run it as-is, do what you want. GH repo in first comment below.

English
0
0
0
23
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The vibe-coding market just hit $1.5B at Emergent. The more interesting signal is what happened when someone ran a quality test this week. Emergent raised $130M at a $1.5 billion valuation. $100M ARR in 8 months. 12 million apps built on the platform in a year. 70% of users have no prior coding experience. Founded in Bengaluru by Mukund Jha and Madhav Jha, with backing from Khosla Ventures, SoftBank, Lightspeed, and Y Combinator. The growth is real. But a developer this week gave the same prompt to Bolt, v0, Lovable, and Emergent. One of them responded with a 2019 stack in 2026. Create React App. Mongo. Non-technical users building on these platforms are not positioned to catch that. The category is maturing past "can it build something" into "what does it default to when no one is watching." Lovable defaults to Supabase and modern React patterns. Bolt pairs with Vite and ShadCN. These choices compound: they determine whether the app a non-technical founder ships is actually maintainable at scale. The pattern I keep watching: cloud infra winners like AWS and Azure didn't win on launch-day features. They won by raising the quality floor so that a default deployment was good enough for a junior engineer to build on top of. The vibe-coding winner probably does the same. $230M raised total. Five times the valuation in six months. The funding is clear. The quality floor is the next test. x.com/0xaxit/status/…
0xaxit.eth@0xaxit

Everyone on my timeline was losing it this week over @emergentlabs raising $130M at a $1.5B valuation. So I gave the same prompt to @boltdotnew @v0 @lovable_dev and Emergent, and read every line of code. One of them shipped a 2019 stack in 2026. Create React App. CRACO. Mongo. No TypeScript. Full teardown 👇 ▶️ recommended watch speed: 1.5x 00:00 The $1.5B question 00:50 The prompt — same for all 4 01:15 @boltdotnew goes first, no pressure 08:48 @emergentlabs enters to a standing ovation 09:41 the UI is a genuine 10/10 12:11 …then I opened the code 14:30 Create React App + CRACO in 2026 15:08 @theo called this exact thing 4 years ago 19:33 Mongo, for a relational app (@theo again) 21:00 the Emergent scorecard 22:23 @v0 has thoughts on your design taste 28:06 @lovable_dev, living up to the name (mostly) 35:03 who I'd actually ship to production 35:50 my questions for @emergentlabs + YC Both @theo videos are linked below — genuinely worth the watch 🧵

English
0
0
0
24
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The signal in OpenRouter's spend data is worth slowing down for. Anthropic holds five of the top ten spots by estimated monthly revenue. But the spend leaders are Opus 4.7 and 4.8, not Fable 5. And on the Sonnet side, 4.6 is pulling nearly twice the usage of Sonnet 5, even though Sonnet 5 is cheaper. Developers are not upgrading to the newest model automatically. This is the gap between "benchmark launch" and "production adoption" and it's longer than the hype cycle suggests. Why: production deployments run on trust, not benchmarks. A team that spent weeks tuning prompts, evals, and failure handling around Opus 4.7 is not migrating for a 3-point benchmark improvement without a forcing function. The same pattern kept GPT-3.5 Turbo alive long after GPT-4 launched. Kept Claude Instant in production weeks after Haiku dropped. The GLM numbers tell a parallel story. Ranked seventh by spend, but first by token volume. Cost-sensitive workloads are chasing price, not capability. Two completely separate markets inside the same leaderboard. Anthropic captures roughly 42% of OpenRouter revenue on about 11% of token share. Premium positioning holding. But the model earning that premium in production is usually two generations behind whatever just launched at the frontier. Build your evals and migration tooling for that gap. It's wider than it looks from the release calendar. x.com/hosseeb/status…
Haseeb >|<@hosseeb

Wait what? #1 grossing model on Open router is Opus 4.7 4.8 was released in May and costs the same... Sonnet is 4.6 has almost twice the usage of Sonnet 5, even though 5 is cheaper Surprised cutover is this slow. + GLM ranked #7 for spend but is #1 for tokens on this list!

English
0
0
0
47
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The most consequential part of the Qwen3.8 announcement is not the benchmark number. It's the open-weight release coming soon. 2.4 trillion parameters. On KingBench 3, Qwen3.8 Max scores 81.25. That puts it above Opus 4.8 (80), Kimi K3 (77.5), and every other open model in the leaderboard. The only thing ahead is Fable 5 at 82.5. And the weights are planned for public release. What this means in practice. When Qwen2.5-72B went open-weight, it was rapidly integrated as a cost-reduction layer in Cursor, Codeium, and various inference providers. Teams doing high-volume code generation swapped commercial APIs for Qwen inference and dropped their costs significantly. Qwen3.8 at 2.4T is a different scale, but the trajectory is the same. Alibaba is running a dual strategy: QwenCloud provides commercial inference with Token Plans that compete directly with OpenAI and Anthropic pricing. Open-weight release builds ecosystem adoption and researcher trust. The funnel is intentional. Local researchers become API customers. The Chinese labs (DeepSeek, Moonshot, 01.AI, Qwen) are now consistently reaching frontier benchmarks faster than the cadence most Western teams planned for. DeepSeek R1, Kimi K3, and now Qwen3.8 all landed within weeks of each other at scale. The bottleneck that moves next: fine-tuning at 2.4T parameters for specific domains. The moment domain-specific Qwen3.8 variants start appearing, enterprise adoption accelerates in ways the API pricing battle can't stop. I'm watching for when the first agentic coding fine-tunes land. x.com/Alibaba_Qwen/s…
Qwen@Alibaba_Qwen

Qwen3.8 is launching and going open-weight soon!🌐 With a massive 2.4T parameters, this model is continuously evolving. We believe it’s one of the most powerful model available today, compatible to leading frontier AI models , second only to Fable 5. You don't have to wait to test it. Just now, the Qwen3.8-Max-Preview made its debut on Alibaba’s Token Plan, Qoder, and QoderWork. Be among the very first to try it out. Can't wait to hear what you build. Stay tuned! 🚀  Token Plan international:qwencloud.com/pricing/token-… China:platform.qianwenai.com/pricing/token-…

English
0
0
0
115
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
Kimi K3 pausing new subscriptions within 48 hours of wider availability is a story about GPU economics, not just demand. The pattern: Moonshot AI launched K3 and hit capacity limits in two days. Existing subscribers stayed protected. New subscriptions paused. Moonshot plans to split into two membership tiers: one for general Kimi workflows, one for coding-specific compute. Across OpenRouter, K3 hit #10 by volume with 97% week-on-week growth. In the same window, DeepSeek V4 Pro fell 21%, and Claude Opus variants dropped 34-44%. Model market share is moving faster than most infrastructure teams can plan for. A few things make this capacity story structurally different from earlier GPU crunches. K3 is a 2.8 trillion parameter MoE model. Running it locally requires approximately 1.4TB of VRAM, which is why all serious inference is on cloud. Moonshot runs heavily on AliCloud, and Alibaba is a major investor in Moonshot. Every K3 inference request is also an Alibaba infrastructure event. AliCloud announced 40%+ quarterly growth before K3 launched. K3 is almost certainly a material driver in the next earnings report. The broader pattern I keep seeing: the Chinese model labs (Moonshot, DeepSeek, 01.AI, Qwen) are building at a pace where GPU procurement can't keep up with their own traction. DeepSeek V3 and R1 both hit similar constraints at launch. K3 is following the same script. What this means for builders: OpenRouter as a fallback aggregator is more important than ever. If your stack is coupled tightly to one provider, capacity events like this cut your service. The hedge is multi-provider routing from day one. x.com/Kimi_Moonshot/…
Kimi.ai@Kimi_Moonshot

Kimi K3 has received far more love than we expected, and our GPUs are feeling it. Over the past 48 hours, demand has pushed close to the limits of our current capacity. To protect the experience of existing subscribers, we're temporarily pausing new subscriptions and prioritizing compute for current members. Existing subscribed users are not affected. We're adding capacity as fast as we can and will reopen new subscription spots in batches. Going forward, we'll also split membership into two more focused plans: Kimi Membership for Kimi Web, App, and Work; and Kimi Code Membership for coding workflows. This will help us match compute more precisely and keep the experience stable. Thank you for your patience and understanding!

English
0
0
0
50
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The bottleneck in agentic systems just moved again. Anthropic cut Claude Code's system prompt by 80%. The Claude Code team's explanation: as the model gets smarter, it needs less direction, fewer constraints, and fewer examples. Examples that were supposed to help were actually constraining the model toward specific patterns it shouldn't assume. My read on what this signals across the category. Three years ago, the craft in coding agents was the prompt. Cursor, GitHub Copilot, Codeium all competed heavily on system prompt design. What went in the context determined what came out. Engineering time went into prompt templates, fallback handling, negative examples. That era is compressing fast. Fable 5, GPT-5.6, and Kimi K3 have all reduced the gap between base model capability and what you'd elicit through a carefully constructed prompt. At sufficient capability, the prompt is a ceiling, not a floor. The implication for teams building coding agents: your system prompt is increasingly not your moat. The moat is task decomposition, context selection, tool routing, and loop supervision. Not the words in the system block. What this looks like in practice: OpenRouter rankings show K3 at #10 with 97% week-on-week growth. Claude Opus variants dropped 34-44% in the same window. Models at the capability frontier don't need hand-holding to follow patterns. Teams still iterating on prompt wording rather than agent architecture are working on the wrong layer. The next constraint isn't what you tell the model. It's how you structure work for it. x.com/petergyang/sta…
Peter Yang@petergyang

Anthropic recently cut Claude Code’s system prompt by 80%. @trq212 explains why: “As the models have gotten smarter, they need less direction, fewer constraints, and fewer examples. The examples are constraining it because now it’s like, ‘Oh, you want things like this example.’ If you remove the examples, it can actually be more free-form. All this is to say that you want to trim your context [when a new model is released]. The latest models often need more room to run.” 📌 Watch the full episode here: youtu.be/aVO6E181cNU

English
0
0
1
81
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The first end-to-end AI-agent-driven production intrusion against a major AI platform just happened. The forensics reveal something the security industry hadn't planned for. Hugging Face's July 16 disclosure: an autonomous agent framework ran thousands of actions across short-lived sandboxes, escalated from a malicious dataset to node-level cluster access, harvested cloud credentials, and moved laterally across internal infrastructure over a weekend. Zero human operators in the loop on the attacker's side. Detection and reconstruction both used AI. Their anomaly-detection pipeline flagged the compromise via LLM-based triage over telemetry. They then ran LLM-driven agents over 17,000+ recorded events to rebuild the attack timeline. What broke down: when defenders tried commercial API models for forensic analysis, safety guardrails blocked the work. The requests contained real exploit payloads and attacker credentials. The models couldn't distinguish an incident responder from an attacker. They fell back to GLM 5.2 running on-premises to complete the analysis. The asymmetry problem stated plainly: the attacker's agents run under no policy. Defender tools are gated behind the same safety systems built for consumers. Incident response at machine speed requires a capable model you can run locally, with no usage policy blocking real attack artifacts. VisionHeight just won the Databricks 2026 Built-On startup challenge for agentic threat intelligence. Palo Alto, Wiz, and CrowdStrike have all expanded AI security coverage this year. The category is real. Lesson from Hugging Face: vet and deploy an open-weight model on your own infrastructure before the incident, not after. The gap between attacker agility and defender access showed up in production for the first time. x.com/BrianRoemmele/…
Brian Roemmele@BrianRoemmele

🚨 Hugging Face just disclosed something that marks a real shift and proved why the fear theater of Anthropic makes sure we are powerless in an emergency. What happened… An autonomous AI agent: zero human operator in the loop breached part of their production infrastructure. It began with a malicious dataset that chained two code-execution bugs in their data-processing pipeline. From there the agent escalated privileges, harvested cloud and cluster credentials, and moved laterally across internal clusters. All over a single weekend. 17,000+ logged actions. Official disclosure: huggingface.co/blog/security-… The part that should make every one stop and think: When HF’s own security team tried to analyze the real attack logs, exploit payloads, and C2 artifacts using Anthropic and OpenAI frontier models through normal commercial APIs, the safety guardrails blocked them. BLOCKED THEM. The models could not reliably tell the difference between “incident responder doing forensics” and “attacker probing.” They had to fall back to a self-hosted open-weight model (GLM 5.2) running on their own infrastructure. That choice also kept sensitive attacker data and referenced credentials inside their environment — no exfiltration to a third-party API. This is why open source (specifically open-weight + self-hosted) wins in the agentic era. The asymmetry is now structural: • Attackers can (and did) run unrestricted agent frameworks — swarms of short-lived sandboxes, self-migrating command-and-control, autonomous decision loops executing thousands of actions. No corporate safety layer slows them down. • Defenders using only hosted “aligned” frontier models hit invisible walls exactly when the stakes are highest: when you need to feed real exploit code and attacker telemetry into an LLM to understand what just happened. Corporate safety tuning that treats legitimate high-signal forensic work as potential misuse creates a defender disadvantage. It is not theoretical anymore. Self-hosted open-weight models remove that choke point. You control the weights. You control the context window. You decide what restrictions (if any) apply. Your sensitive logs and credentials never leave your perimeter during analysis. You can have the model ready before the incident instead of discovering mid-breach that your primary analysis tools are blind to the very thing you need to see. HF deserves credit for rapid containment, transparent disclosure, and for already having self-hosted capability in place. They also used LLM-driven detection and triage on their own side. But the deeper signal is clear: In this AI world where both offense and defense are becoming agentic, sovereignty over your intelligence stack is no longer optional. The organizations and individuals who can run, inspect, audit, and (when necessary) remove guardrails on their own models will have the decisive edge in understanding and responding to threats that move at machine speed. Open source wins here not just because it is cheaper or more “democratic” in the abstract though those things matter. It wins because it is the only practical path to having tools that remain usable when the attack is real, the data is sensitive, and the safety filters of distant API providers become an obstacle instead of a feature selling hands tied lobotomies as “safety”. The agentic future is not coming. It is already probing production infrastructure. The question is no longer whether you will face autonomous agents. It is whether your analysis and response systems will still work when they arrive. And Dario, you and your game playing, ivory tower company is not needed.

English
1
1
2
101
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The quality gate for AI-generated UIs just emerged. It's a skill, not a model. Hallmark is an open-source design skill for Claude Code, Cursor, and Codex. It gives coding agents a concrete rule set: 21 macrostructures, 22 themes, a 65-gate slop test covering typography, contrast, layout, and anti-patterns. The goal is to make agent-built interfaces look intentionally designed instead of generic. 20,000 installs and 12,000 GitHub stars since May 2026. That velocity is a signal. Developers building with agentic coding tools have a shared problem they've had no clean name for: the output is functional but visually indistinguishable. Every agent-built landing page shares the same fingerprint. Hallmark is the first widely adopted attempt to break that with an explicit rule set. The three specific commands that make it useful: audit scores existing code against the anti-pattern catalogue. Redesign throws out the structural fingerprint while keeping copy and brand. Study extracts design DNA from a screenshot or URL into a portable design file. Each command maps to a real moment in the build process. The comparison I keep reaching for: ESLint started as a code quality tool and became required infrastructure for every JavaScript codebase. Prettier did the same for formatting. Both now run in CI. The pattern for quality gates in developer tools is that they start optional and become mandatory. Hallmark is moving in that direction. Version 2 is already in development. The tooling layer for agentic coding output is real now. Design quality is the next frontier after functional correctness. x.com/nutlope/status…
Hassan@nutlope

Now at ~20k installs & 12k GitHub stars! Started working on Hallmark v2 with @YoussefUiUx 🫡

English
1
0
1
90
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
More than half of CoreWeave's compute is now inference. That number tells you where the AI infrastructure industry has landed. A few years ago the split was clear. Training clusters were premium product. Inference happened afterward, on commodity hardware. That separation is collapsing. Reasoning models and reinforcement learning have changed the networking requirements for inference. RL needs distributed key-value caching. Long reasoning chains generate intermediate tokens that need to shuffle between nodes. Both require training-grade networking, not the thinner fabric that could handle standard decode workloads. The scale implications: CoreWeave's 100,000-GPU Grace Blackwell cluster runs at roughly 250 MW and has around 16 million connection points. At that scale, failure is not an edge case. Every 10% of cycles lost to failures, retries, or poor orchestration raises effective token costs by 10%. Cost per token is a full-system output, not a chip benchmark. What makes this interesting for the competitive landscape: older GPUs retain value through workload specialization. Newest chips handle prefill and frontier compute. Older hardware handles decode, smaller-model inference, and evals. Heterogeneous fleets are finding their margin. Vera Rubin is the next threshold. CoreWeave's estimate: up to 90% reduction in inference costs, plus improvements to time to first token and density. What I keep seeing across the AI infrastructure stack: the training-inference boundary is dissolving. A closed loop where production inference feeds back into RL training is not the future. It's the product roadmap being shipped today. x.com/ShanuMathew93/…
Shanu Mathew@ShanuMathew93

CoreWeave CTO Peter Salanki on where AI infrastructure economics are heading: >~50% of CoreWeave compute is already inference. Reasoning, reinforcement learning and distributed key-value caching increasingly require training-grade networking. >A 100,000-GPU Grace Blackwell cluster consumes ~250 MW and has ~16M connection points. At that scale, failure is inevitable. Goodput and completed work matter more than headline uptime. >Losing 10% of cycles to failures, retries or poor orchestration raises effective token costs by ~10%. Cost per token is a full-system output, not a chip benchmark. >Older GPUs can retain value through workload specialization: newest chips for prefill and frontier compute, older GPUs for decode, evaluations and smaller-model inference. >Vera Rubin could cut inference costs by up to 90%, improve time to first token and increase density. >Salanki “doesn’t lose sleep over power.” He sees enough transmission-level power in the US; the actual 2026 constraints are substations, transformers, cooling equipment and the skilled trades needed to turn grid capacity into an operating data center. >CoreWeave is staying NVIDIA-only because of what they see from customers. Better focus and execution today, with obvious supplier concentration and bargaining-power risk.

English
0
0
1
57
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The bottleneck blocking reliable long-horizon agents isn't model intelligence. It's the reward signal. Outcome rewards work fine when tasks are short. But agentic systems that perform tens or hundreds of tool calls before producing a final answer don't fit that pattern. The same outcome reward gets assigned backward across a hundred steps. The signal becomes sparse, noisy, and increasingly useless as trajectories grow longer. Microsoft Research and University of Wisconsin-Madison published TRACE this week. Turn-level Reward Assignment via Credit Estimation. The approach assigns reward at individual tool-call boundaries instead of trajectory endpoints. For each trajectory prefix, a frozen reference model generates log-probabilities over the gold answer. Changes in those values become Temporal Difference rewards, converted into per-turn credit without training an additional critic, without process labels, without Monte Carlo rollouts. The benchmark results on BrowseComp-Plus are striking. Qwen3-30B-A3B goes from 7.2 to 35.6 with pure RL and no cold-start SFT. The improvement transfers to open-web benchmarks. The pattern I keep noticing across agentic systems: every generalization failure traces back to credit assignment. Web agents, coding agents, search agents. The trajectory gets long, the outcome reward gets ambiguous, and RL training degrades. TRACE is the cleanest solution I've seen to that specific problem. Credit assignment is the hidden variable in why agentic RL is hard. The paper is worth reading. x.com/SharonYixuanLi…
Sharon Li@SharonYixuanLi

Scaling outcome-based RL won't solve long-horizon agentic tasks. Credit assignment is the bottleneck, and turn-level reward is inevitable. The question is how to get it. Process labels are expensive; we all know that. Excited to release TRACE: Turn-level Reward Assignment via Credit Estimation for Long-Horizon Agents. No trained critic, no process labels, no Monte Carlo continuations, no strong LLM judge. 🧵 📄 arxiv.org/abs/2607.13988 🤔 The core problem: Outcome rewards work well when a task contains a short reasoning trace and an easily verified answer. But agents may perform tens or hundreds of tool interactions before responding. A single final reward tells us whether the agent succeeded, but not which tool calls uncovered decisive evidence, which were redundant, or which sent the agent down the wrong path. This makes RL increasingly sparse, noisy, and inefficient as trajectories grow longer. ⚙️ Our approach: TRACE TRACE assigns credit at individual tool-call boundaries. For each trajectory prefix, a frozen reference model measures how much more predictable the gold answer has become. TRACE converts this into a state value and uses temporal-difference changes to reward each interaction: → Positive credit when a tool call moves the agent closer to the answer → Near-zero credit when it adds redundant information → Negative credit when it moves the agent away from the answer Probability to predict the final answer remains the global training objective; turn-level rewards simply reveal which actions contributed to it. 🔍 Why the formulation matters: The turn-level rewards telescope across the trajectory. Repeating searches or reopening the same evidence cannot artificially accumulate additional one-step credit. TRACE can also propagate delayed progress backward: if a search surfaces a promising page and a later `open` reveals the decisive evidence, both interactions can receive appropriately localized credit. 📈 The results: Using pure RL (without cold-start SFT, agentic mid-training, or live-web training data), TRACE substantially improves long-horizon search: → Qwen3-4B: 7.2 → 35.6 on BrowseComp-Plus → Qwen3-30B-A3B: 8.4 → 42.6 which is on-par with the Tongyi-DeepResearch-30B-A3B. Under controlled comparisons with the same models, data, tools, and outcome rewards, TRACE also outperforms GRPO, GSPO, and GiGPO across both model scales. 📄 Paper: arxiv.org/abs/2607.13988 Led by the amazing @LeitianT, and huge thanks to our collaborators at Microsoft Research: Baolin Peng, Wenlin Yao, Tao Ge, Hao Cheng, Mike Hang Wang, and @JianfengGao0217.

English
0
0
0
58
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The model that just sold for $587 million is worth understanding closely. InterPositive trains one model per production. Nothing scraped, nothing licensed, nothing carried over from the last project. The model learns only from the dailies of the film or show it's deployed on. That design choice solves three problems at once. Copyright: a model trained only on footage the production owns has clean IP provenance. Generalization failures: a model that knows nothing about other productions can't hallucinate styles that don't belong. Legal exposure: the 2023 strikes made AI provenance the most sensitive issue in Hollywood. Ben Affleck manufactured the proprietary training dataset on a closed soundstage, in four years of stealth. Each production that deploys it gets its own model, built from that production's raw footage. The output inherits the visual logic, lighting palette, and editorial consistency of that specific shoot. Netflix said roughly 300 of its titles used generative AI in 2026. InterPositive does the unglamorous work: replacing missing shots, reframing, fixing lighting, swapping backgrounds. Each one is a reshoot day avoided. Reshoot days on a major production run six figures apiece. The 16-person team price tag is $587M cash. That's $36.7M per person. But the team isn't the asset. The training data from that soundstage, and the framework for building production-specific models, is the asset. Netflix is buying a factory for copyright-clean visual AI at production scale. The category I keep watching is production-native models. The differentiation doesn't come from scale. It comes from data provenance and domain specificity. x.com/aakashgupta/st…
Aakash Gupta@aakashgupta

Netflix just paid $587 million in cash for a 16-person startup whose entire edge is an AI model that deliberately knows almost nothing. InterPositive trains its model only on the dailies of the specific film or show using it. One production, one model. Nothing scraped, nothing licensed from a library, nothing carried over from the last project. That single design choice solves the problem keeping every studio legal department up at night. A model trained on scraped footage produces output with radioactive copyright status, and the 2023 strikes made AI provenance the most sensitive issue in Hollywood. Train on footage the production already owns, and the output is exactly as clean as the footage that went in. Affleck even manufactured his own training data, capturing a proprietary dataset on a closed soundstage while the company ran in stealth for four years. Sarandos told investors roughly 300 Netflix titles used generative AI this year, with InterPositive's tools doing the unglamorous work: replacing missing shots, reframing, fixing lighting, swapping backgrounds. Each one a fix that would otherwise mean a reshoot day, and reshoot days on a major production run six figures apiece. The deal also came with Affleck as senior advisor, which might be the most valuable line item. Talent trusts an Oscar-winning director explaining AI in a way they will never trust a VP of machine learning. The frontier labs trained on the whole internet and bought themselves a decade of litigation. Affleck trained on a single film's dailies and sold for $587 million.

English
0
0
0
41
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The infrastructure bottleneck for agentic compute just moved. Modal built a scheduling system that spins up 1 million sandboxes concurrently in seconds. The number that matters: 18,500 sandbox creations per second. AWS Lambda's microVM creation caps at 100 per second. That is a 185x difference. What changed technically: Modal replaced centralized scheduling with a fleet of scheduling servers handling creation requests concurrently. No global coordination lock. Median sandbox start time is under half a second. At 100,000 concurrent sandboxes, that still holds. The real users making this matter: Lovable ran 20,000 concurrent sandboxes over a 48-hour event generating 1 million app creations. A major AI lab is already running 100,000 concurrent sandboxes for RL training workloads, with a stated target of 1 million. This is what agentic compute looks like when it actually scales. The use cases driving demand are reinforcement learning (parallel environment rollouts at massive scale), code agents (every code change in its own isolated sandbox), and browser agents (one browser instance per agent task). The platform landscape here includes Modal, E2B, Daytona, Runloop, and Fly.io, all converging on sub-second sandbox starts as the baseline requirement. What separates them is GPU access, pricing floors, and whether they can maintain isolation at this level of concurrency. The bottleneck I keep watching: it is no longer compute density. It is orchestration. Who can give a single agent workflow 10,000 isolated environments in 30 seconds, at a price a startup can pay. x.com/jonobelotti_IO…
Jonathon Belotti@jonobelotti_IO

One million sandboxes created in 52 seconds. 18.5k/s! AWS Lambda's microVM creation caps out at 100/s.

English
0
0
0
38
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The pattern I keep seeing on frontier model capabilities: stealth evals tell you more than public benchmarks. Kimi K3 is scoring top-tier at cybersecurity on internal, private evaluations run against real defensive tasks. Not benchmark-overfit results; raw capability on tasks that matter for red-teaming and hardening. Recall and precision strong enough to make it the workhorse choice for cyber work at K3's price point. But GPT-5.6 Sol is a different story: a leap ahead at 7x the cost per run, and far more cooperative on defensive cyber hardening compared to most models. This is the capability frontier splitting in a way I have not seen before. For the first time, the open-weight tier (Kimi K3) is genuinely competitive at cybersecurity, while the closed frontier (Sol) has pulled further ahead but at a cost structure that only makes sense for high-value targets. What this means in practice: for most agentic security workflows, a team running K3 gets strong defensive capability at a fraction of the price. For critical infrastructure hardening where you need the top end, you pay for Sol. There is also a safety dimension worth noting: unlike some frontier models, K3 is assessed as unlikely to have dangerous offensive cyber capabilities. Sol is more open to defensive hardening but that openness is carefully scoped. My take: the security use case is the fastest-moving frontier for open-weight model adoption. x.com/rauchg/status/…
Guillermo Rauch@rauchg

Based on internal evals: ▪️ Kimi K3 is top-tier at cybersecurity There is chatter on X that Moonshot benchmark-overfit. These are stealth evals. Model has raw IQ. ▪️ Sol is a leap ahead in cyber capability At a significantly higher cost, but quite remarkable still. ▪️ Fable refuses everything We couldn’t get it to complete the run at all. What’s interesting is that Sol in comparison was much more open to helping with defensive cyber hardening TL;DR: frontier, open-weight cybersecurity capability is here. Try it on deepsec.sh for defensive purposes.

English
0
0
0
65
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The open-weight model race just entered a new scale class and both entrants are from China. Alibaba previewed Qwen3.8-Max this week: 2.4 trillion parameters, open weights coming, multimodal, running as a preview on their Token Plan subscription. One week earlier, Moonshot released Kimi K3 at 2.8 trillion parameters with full open weights. Two 2T-class open models, both dropping in the same week. That is not coincidence. What is actually happening: Alibaba and Moonshot are racing to define the open frontier tier before open weights become the expected default at this scale. Whoever has the best-performing open-weight model at 2T-plus parameters sets the benchmark expectation for everything below it. The pricing picture is interesting. Alibaba bundles Qwen3.8 into a subscription Token Plan at $6 per month (Lite), $18 (Standard), or $68 (Pro with 40,000 weekly credits and 6-8 concurrent agents). Moonshot's K3 API is $3/M on cache misses and $15/M on output. Both are trying to get developers locked into their ecosystem before the weights drop and the model becomes a commodity. The real competition here is not benchmark rankings. It is distribution, ecosystem fit, and where agents get trained to call first. Fable 5 is still the clear frontier leader. But the gap between frontier and open-weight just got a lot smaller than anyone tracking benchmarks from 3 months ago would expect. My read: this week mattered for the open frontier. Both models will have known weaknesses. What I am watching is which one gets embedded into the first large-scale agent deployment. x.com/Alibaba_Qwen/s…
Qwen@Alibaba_Qwen

Qwen3.8 is launching and going open-weight soon!🌐 With a massive 2.4T parameters, this model is continuously evolving. We believe it’s one of the most powerful model available today, compatible to leading frontier AI models , second only to Fable 5. You don't have to wait to test it. Just now, the Qwen3.8-Max-Preview made its debut on Alibaba’s Token Plan, Qoder, and QoderWork. Be among the very first to try it out. Can't wait to hear what you build. Stay tuned! 🚀  Token Plan international:qwencloud.com/pricing/token-… China:platform.qianwenai.com/pricing/token-…

English
0
0
0
161
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The bottleneck for open model adoption just shifted from capability to setup friction. Moonshot AI is now sponsoring claude-code-router, an open-source project at 35,000 GitHub stars. The pitch: Kimi K3's 2.8 trillion parameters in one click, without touching your existing terminal setup, hooks, or CLAUDE.md. The router intercepts Claude Code API calls and redirects them to any backend: Anthropic, OpenAI, Kimi, Qwen, Hermes, and others. Adding K3 is now one click. Kimi's subscription requests pass through natively, your balance and usage show in the dashboard, automatic failover if a provider goes down mid-session. K3's cache pricing does the math for long contexts: $0.30 per million on cache hits, $3 per million on misses. For repeated context in agentic workflows, that is structurally cheaper than most closed alternatives. The model that wins is rarely the one with the best benchmark. It is the one installed on the most machines. Anthropic wins on integration depth by controlling the full stack. Moonshot's move is to get K3 embedded inside the infrastructure 35,000 developers already trust, before anyone has to consciously choose it. Kimi K3 also scored 1,679 on the Arena front-end code benchmark, ahead of Fable 5 in blind testing. Full open weights land July 27. That is when the real question starts: whether the router integration holds, or whether builders embed K3 directly into their own agent stacks. The pattern I keep watching: the open frontier race is being fought not on benchmarks but on distribution. x.com/zodchiii/statu…
darkzodchi@zodchiii

EVERYONE WANTS TO TRY KIMI K3. NOBODY WANTS TO CHANGE THEIR SETUP. KIMI GAVE THE SOLUTION. Moonshot now sponsors claude-code-router: your terminal, your hooks, your CLAUDE.md, their 2.8 trillion parameters. 35,000 stars. And the Kimi part is one click: → built-in Kimi presets: import the API or a Kimi Code subscription in one click → subscription requests pass through natively, zero protocol conversion → your Kimi balance and usage show up right in the router's dashboard → automatic failover when a provider goes down mid-session → K3's cache pricing does the rest: repeated context at $0.30 per million One honest note: the router's proxy mode installs a root certificate, so skip that toggle unless you know why you need it. The default setup doesn't touch it. Grab it 👇

English
0
0
2
177
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
Netflix paid $587 million for a 16-person team built around one core bet: deliberate constraint. InterPositive trains a model only on the dailies of a specific production. One show, one model. Nothing scraped from the internet. The model learns that production's lighting signatures, lens characteristics, and editorial rhythm. Color grading, relighting, VFX additions all informed by the footage itself. Netflix disclosed this in its Q2 2026 earnings: AI workflows have been used in roughly 300 titles this year. Films like Glory, Brasil 70: A Saga do Tri, and The American Experiment used it for crowd scenes and establishing shots. The logic here runs against the foundation model assumption. Foundation models say: one massive model trained on everything is better than a narrow model trained on less. InterPositive bets the opposite. In high-fidelity creative contexts, a model that knows only your footage outperforms one that has seen the whole internet. I keep seeing the same pattern across specialized domains. Bloomberg trained a financial model only on terminal data and outperformed GPT-4 on finance benchmarks. Harvey built on proprietary legal documents. Replit trained on specific codebase patterns. The narrow data wins in high-context, high-stakes environments. The reason Netflix paid that price is not purely the architecture. It is the trust relationship required to get a production to hand over its dailies. InterPositive spent four years in stealth building that trust with studios. That is the moat, not the model design. This pattern will repeat across every vertical where proprietary production data is the differentiator: medical imaging, legal documents, financial modeling, architecture. x.com/Polymarket/sta…
Polymarket@Polymarket

JUST IN: Netflix reveals it paid $587 million in cash for Ben Affleck’s AI startup InterPositive.

English
0
0
0
71
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The coding CLI agent market just split into two clear camps: tools that lock you into their model, and tools that let you pick. Claude Code is the premium locked option. Anthropic controls the full stack. You talk only to Claude. That is a deliberate architectural choice, not a limitation. Google tried the open path. Gemini CLI launched as open source, then on June 18 it was closed. Antigravity CLI replaced it. The free tier dropped from 1,000 requests per day to roughly 20. The open-source momentum was quietly revoked. Moonshot moved in the opposite direction. Kimi Code launched in June, then updated to 0.25.0 and 0.26.0 on the same day as K3 shipped. Model-agnostic by design: route to Anthropic, OpenAI, or Google through config. Open weights on the model side, open provider selection on the CLI side. Alibaba followed with Qwen Code: an Apache 2.0 fork of the original Gemini CLI codebase, optimized for Qwen3-Coder 480B MoE. The effective continuation of what Google abandoned. My read on the landscape: Anthropic and OpenAI own the premium closed segment. Moonshot and Alibaba own the open flexible segment. The model capability gap at the top end is closing. K3 leads six coding benchmarks right now, and K3 is Kimi Code's default model. For teams building long-horizon agent infrastructure, model routing flexibility matters more than it did a year ago. The model-agnostic CLIs give you that optionality without a rewrite when you need to swap providers. The Chinese labs picked up the architecture philosophy Google abandoned. x.com/Kimi_Moonshot/…
Kimi.ai@Kimi_Moonshot

Introducing Kimi K3: Open Frontier Intelligence 🔹 2.8 Trillion Parameters, 1 Million Context, Native Multimodal 🔹 Kimi Delta Attention enables up to 6.3x faster decoding in million-token contexts 🔹 Attention Residuals deliver ~25% higher training efficiency at <2% additional cost 🔹 Built for long-horizon agentic coding and self-evolving workflows Kimi K3 is now live on on Kimi.com, Kimi Work, Kimi Code, and the Kimi API. Open Weights by July 27, 2026. 🔗 API: platform.kimi.ai 🔗 Tech blog: kimi.com/blog/kimi-k3

English
0
0
1
150
Prasenjit Sarkar
Prasenjit Sarkar@stretchcloud·
The new constraint for open-weight model adoption is not the model. It is the serving infrastructure behind it. Kimi K3 launched July 16 as the largest open-weight model ever: 2.8T parameters, MoE with 896 experts activating 16 per query, 1M context window. It took the top spot on Frontend Code Arena (score 1,679), above Fable 5 and GPT-5.6 Sol. On SWE Marathon and Program Bench it leads the field. Pricing: $3/1M fresh input tokens, $15/1M output. But a single Moonshot provider is serving it on OpenRouter with no routing fallback. Early independent measures: 11 seconds to first token. 16 tokens per second throughput. For a single query that is tolerable. For an agent loop that needs 20 to 40 model calls per task, that translates to 3 to 7 minutes of wait time in latency alone. Agent builders running real workloads need 30 to 60 tps minimum. I keep seeing this pattern every time a major Chinese open-weight model launches. DeepSeek R1 in January. Kimi K2.5 in January too. Demand spikes, the single API route saturates, and users wait 2 to 4 weeks for competing providers to spin up. The fix is closer than usual this time. Moonshot releases full open weights on July 27. SambaNova, Groq, and local H100 deployments get a path to better serving within days of the weights release. Unsloth will almost certainly ship a quantized version for local inference within a week. For agent builders right now: benchmark K3 for quality, hold production traffic until July 27 and until secondary providers appear. The model quality floor just raised significantly. The serving problem is temporary. x.com/bridgemindai/s…
BridgeMind@bridgemindai

Kimi K3 has a serious problem. One provider is serving it. 16 tokens per second. 11 seconds of latency before the first token. I called it the best open source model I have ever used. That is still true. But at these speeds it is borderline unusable for real work. My agents sit idle waiting on it. Moonshot needs to release the weights so other providers can serve this thing properly. The best open model in the world is being throttled by its own infrastructure.

English
0
0
0
122