SAM 3 (Segment Anything Model 3) vs Modo

“The primitive is clean: prompted zero-shot segmentation extended across time and 3D space via a unified encoder-decoder with memory attention for frame propagation. The DX bet Meta made is that releasing weights under a research license with a working inference API beats a hosted-only offering for adoption — and they're right. First 10 minutes with SAM 2 was already survivable; SAM 3 adds 3D point-cloud input without blowing up the interface, which shows someone actually thought about backward compatibility. The weekend alternative here is not viable — you cannot replicate temporal-consistent video segmentation with a Lambda and a CLIP call. The specific decision that earns the ship: keeping the prompt interface stable across modalities so existing integrations don't break.”

“The spec-driven pipeline is the real differentiator here — most AI IDEs turn into spaghetti on large refactors because there's no planning phase. Modo's Requirements → Design → Tasks flow gives agents enough context to stay coherent across files. The multi-provider support is a bonus: swap to Ollama for private codebases without changing your workflow.”

“Category is foundation-model segmentation; direct competitors are Grounded SAM pipelines, Mask2Former, and increasingly Google's own video segmentation work. SAM 3 wins the open-weights race right now, but the research license is the fragile point — production commercial use is still gated, which means the actual deployment story for companies depends on Meta's licensing appetite. The scenario where this breaks is real-time mobile edge inference: SAM 3 is GPU-hungry and the latency profile at video frame rates on consumer hardware is not going to be pretty without distillation work others will have to do. What kills this in 12 months is not a competitor but a platform move: if Meta ships a hosted inference API with commercial terms, the current DIY-weights story gets replaced and half these integrations get rebuilt. Still a ship because open weights at this quality level genuinely raise the floor for the whole field.”

“It's a VS Code fork by a solo developer self-described as '60–70%' of the competition. That missing 30–40% matters in daily use — autocomplete quality, diff review, context awareness. The real question is whether an indie project can keep pace with Cursor's R&D budget, and historically the answer has been no.”

“The thesis SAM 3 bets on: within 3 years, segmentation becomes infrastructure-level — something every vision pipeline calls the way it calls an embedding model today, not something you train per task. For that to pay off, zero-shot generalization has to hold across the long tail of real-world domains (medical imaging, autonomous vehicles, AR), and inference costs have to fall enough that per-frame video processing is economically viable at scale. The second-order effect that matters most is not better video editing — it's that 3D point-cloud support puts a universal object-understanding primitive into the hands of robotics and spatial computing developers who previously had no open baseline worth building on. SAM 3 is on-time to the spatial-AI trend line; the robotics and AR application wave is just starting to need exactly this. The future state where this is infrastructure: every real-time AR scene graph runs a SAM 3 derivative as its perceptual backbone.”

“Spec-driven development is the right architectural instinct. When AI agents become fully autonomous in large codebases, they'll need formal planning layers — not just raw prompt-to-diff pipelines. Modo is early proof that structured agent workflows can be packaged as open-source developer tooling before the big players fully figure it out.”

“The job-to-be-done is singular: give any vision application a prompted segmentation capability without domain-specific training. SAM 3 nails it for image and now meaningfully extends it to video and 3D, which are the two modalities where the original SAM left users building brittle frame-by-frame hacks. The onboarding is a research repo — there's no 2-minute value moment unless you already know how to run a PyTorch inference script, which means the addressable user is builders, not end-users, and that's the right call given the research license. The completeness gap is real for 3D: point-cloud support is there but the tooling ecosystem around it (loaders, visualizers, export pipelines) is not Meta's problem to solve, so teams will spend non-trivial time on glue. Ships because the core job is done better than any open alternative, but the product opinion here is 'give developers a primitive' — teams that need a finished product are not the customer.”

“Being able to run a full AI IDE locally without sending proprietary design files or creative briefs to a third-party server is huge for creative agencies. Self-hostable, multi-provider, MIT — this checks every box for privacy-conscious creative teams who want AI assistance without the data exposure.”