Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Flutter Scene 0.23 is out. Realtime 3D on Flutter's native graphics stack, Flutter GPU and Impeller. No forks. No platform views. Just vanilla Flutter. Global illumination, reflections, compressed glTF/KTX2, and six bundled agent skills that make vibe coding with Scene fun.

Brandon DeRosier

1,617 subscribers

16,770 views • 11 days ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Build something real with Flutter 3.47. Scene is powered by Flutter's own graphics stack. Impeller and Flutter GPU. No forks, no platform views, no secondary rendering context. macOS, Linux, Windows, iOS, Android, Web, and custom embedders.

Build something real with Flutter 3.47. Scene is powered by Flutter's own graphics stack. Impeller and Flutter GPU. No forks, no platform views, no secondary rendering context. macOS, Linux, Windows, iOS, Android, Web, and custom embedders.

Brandon DeRosier

19,765 views • 1 month ago

This is Scene Editor. Running on Flutter 3.47 stable. Flutter is excellent for building serious 3D desktop apps. Powered entirely by Flutter's built-in graphics stack, Flutter GPU and Impeller. No forks, no platform views, no external rendering contexts. Scene Editor is just a vanilla Flutter application. Build 3D apps for macOS, Linux, Windows, iOS, Android, Web, and custom embedders. Non-destructive importing, overrides on nested prefabs, live material and shader editing, custom gizmos, and component inspectors you define with property annotations. It watches the filesystem, and custom components you write become instantly available in the editor upon saving. Configure, build, and run your live app without leaving it. Flutter is now 3D.

This is Scene Editor. Running on Flutter 3.47 stable. Flutter is excellent for building serious 3D desktop apps. Powered entirely by Flutter's built-in graphics stack, Flutter GPU and Impeller. No forks, no platform views, no external rendering contexts. Scene Editor is just a vanilla Flutter application. Build 3D apps for macOS, Linux, Windows, iOS, Android, Web, and custom embedders. Non-destructive importing, overrides on nested prefabs, live material and shader editing, custom gizmos, and component inspectors you define with property annotations. It watches the filesystem, and custom components you write become instantly available in the editor upon saving. Configure, build, and run your live app without leaving it. Flutter is now 3D.

Brandon DeRosier

11,876 views • 21 days ago

This campfire is 100% procedurally generated at runtime with Flutter Scene. No model files, no image assets. Recorded in debug mode. A full 3D engine built entirely on Flutter's built-in graphics API, Flutter GPU. No forks, no native renderer integrations. macOS, Windows, Linux, iOS, Android, web, and custom embedders.

This campfire is 100% procedurally generated at runtime with Flutter Scene. No model files, no image assets. Recorded in debug mode. A full 3D engine built entirely on Flutter's built-in graphics API, Flutter GPU. No forks, no native renderer integrations. macOS, Windows, Linux, iOS, Android, web, and custom embedders.

Brandon DeRosier

11,241 views • 1 month ago

This is rendered by Flutter 3.47 Stable using Flutter GPU via the flutter_scene package. macOS, Linux, Windows, iOS, Android, Web, and custom embedders. Today. :) No forks, no platform views, no external renderers, no secondary graphics context. It's vanilla Flutter. Each pass is a custom material over geometry derived from the model at load time. No pre-baked effect meshes. Just simple Dart APIs AOT compiled to arm64 instructions.

This is rendered by Flutter 3.47 Stable using Flutter GPU via the flutter_scene package. macOS, Linux, Windows, iOS, Android, Web, and custom embedders. Today. :) No forks, no platform views, no external renderers, no secondary graphics context. It's vanilla Flutter. Each pass is a custom material over geometry derived from the model at load time. No pre-baked effect meshes. Just simple Dart APIs AOT compiled to arm64 instructions.

Brandon DeRosier

29,746 views • 1 month ago

Everything in this video is real-time 3D rendered in Flutter. No forks, no platform views, no secondary graphics context. Rendering, physics, gaussian splats, DICOM volumes, accessible scenes, embedded widgets, hot reload for every asset, instanced prefabs with arbitrary overrides, and much more. Get started at

Everything in this video is real-time 3D rendered in Flutter. No forks, no platform views, no secondary graphics context. Rendering, physics, gaussian splats, DICOM volumes, accessible scenes, embedded widgets, hot reload for every asset, instanced prefabs with arbitrary overrides, and much more. Get started at

Brandon DeRosier

41,357 views • 1 month ago

Godot's Third Person Shooter demo, ported to Flutter Scene as a fun stress test. Running in Flutter 3.47 on Flutter GPU and Impeller, the built-in graphics stack. 617 MiB of cooked content. 1,795,763 unique vertices, 659,079 unique triangles, 320 collision meshes, 23 punctual lights. Converted to Scene's own scene description format for AOT baking. The lighting doesn't look as moody as the original and needs a bunch of adjusting. Way too much light spilling in from the environment map... But a pretty decent port so far!

Godot's Third Person Shooter demo, ported to Flutter Scene as a fun stress test. Running in Flutter 3.47 on Flutter GPU and Impeller, the built-in graphics stack. 617 MiB of cooked content. 1,795,763 unique vertices, 659,079 unique triangles, 320 collision meshes, 23 punctual lights. Converted to Scene's own scene description format for AOT baking. The lighting doesn't look as moody as the original and needs a bunch of adjusting. Way too much light spilling in from the environment map... But a pretty decent port so far!

Brandon DeRosier

15,189 views • 25 days ago

up until today, this scene will always make my heart flutter. the vibe it's giving, it is very new, it is very kdrama, it is very romantic that you just let yourself absorb the fluttering and let yourself feel the love. 🫶🏻🥹 #ThamePoSeries #WilliamEst #williamjkp #est_rvp

up until today, this scene will always make my heart flutter. the vibe it's giving, it is very new, it is very kdrama, it is very romantic that you just let yourself absorb the fluttering and let yourself feel the love. 🫶🏻🥹 #ThamePoSeries #WilliamEst #williamjkp #est_rvp

ܸ

19,750 views • 1 year ago

🚀 New on ModelScope: MiniMax M2.1 is open-source! ✅ SOTA in 8+ languages (Rust, Go, Java, C++, TS, Kotlin, Obj-C, JS) ✅ Full-stack Web & mobile dev: Android/iOS, 3D visuals, vibe coding that actually ships ✅ Smarter, faster, 30% fewer tokens — with lightning mode (M2.1-lightning) for high-TPS workflows ✅ Top-tier on SWE-bench, VIBE, and custom coding/review benchmarks ✅ Works flawlessly in Cursor, Cline, Droid, BlackBox, and more It’s not just “better code” — it’s AI-native development, end to end. 🔗 Model:

🚀 New on ModelScope: MiniMax M2.1 is open-source! ✅ SOTA in 8+ languages (Rust, Go, Java, C++, TS, Kotlin, Obj-C, JS) ✅ Full-stack Web & mobile dev: Android/iOS, 3D visuals, vibe coding that actually ships ✅ Smarter, faster, 30% fewer tokens — with lightning mode (M2.1-lightning) for high-TPS workflows ✅ Top-tier on SWE-bench, VIBE, and custom coding/review benchmarks ✅ Works flawlessly in Cursor, Cline, Droid, BlackBox, and more It’s not just “better code” — it’s AI-native development, end to end. 🔗 Model:

ModelScope

16,939 views • 8 months ago

You can do some pretty fun realtime VFX once the depth output is just another (Type)GPU buffer :D I basically yoinked my old 3D fire sim (that is actually a fluid sim but do not tell anyone) and plugged it into the depth pipeline together with hand tracking Everything here is built from scratch in TypeGPU, so inference, simulation and rendering can share GPU resources and interleave passes directly. That’s 2 NN inferences, a full 3D fluid sim, relighting and rendering in one command encoder, still under 16 ms with no CPU sync in between

You can do some pretty fun realtime VFX once the depth output is just another (Type)GPU buffer :D I basically yoinked my old 3D fire sim (that is actually a fluid sim but do not tell anyone) and plugged it into the depth pipeline together with hand tracking Everything here is built from scratch in TypeGPU, so inference, simulation and rendering can share GPU resources and interleave passes directly. That’s 2 NN inferences, a full 3D fluid sim, relighting and rendering in one command encoder, still under 16 ms with no CPU sync in between

Konrad Reczko

26,708 views • 12 days ago

Every time I think the ESP32-S3 has hit its limit, someone finds another gear. This open-source Jet renderer is now pushing the S3 even harder. Real-time screen-space reflections, water ripple distortion, lens flare and 8 ships on screen, all running on a tiny MCU. Performance dropped from around 60 FPS to 45–50 FPS, but that's still wild for an ESP32-S3. And the developer thinks there is more performance left to squeeze out. No GPU. No desktop CPU. Just an ESP32-S3 doing real-time 3D graphics.

Every time I think the ESP32-S3 has hit its limit, someone finds another gear. This open-source Jet renderer is now pushing the S3 even harder. Real-time screen-space reflections, water ripple distortion, lens flare and 8 ships on screen, all running on a tiny MCU. Performance dropped from around 60 FPS to 45–50 FPS, but that's still wild for an ESP32-S3. And the developer thinks there is more performance left to squeeze out. No GPU. No desktop CPU. Just an ESP32-S3 doing real-time 3D graphics.

Praveen Kumar Verma

15,924 views • 16 days ago

Google just did it again. They just launched "Google Skills" a free platform to turn anyone into an AI expert. 3,000+ courses, labs & certificates from Google Cloud, DeepMind, and Grow with Google all in one place. → Learn AI, data, and coding from real Google engineers → Earn credentials that actually get you hired → Build hands-on projects with Gemini Code Assist → Compete on global leaderboards and share your wins No paywalls. No BS. Just world-class AI education free. This might be the biggest AI upskilling move of the decade. 👉

Google just did it again. They just launched "Google Skills" a free platform to turn anyone into an AI expert. 3,000+ courses, labs & certificates from Google Cloud, DeepMind, and Grow with Google all in one place. → Learn AI, data, and coding from real Google engineers → Earn credentials that actually get you hired → Build hands-on projects with Gemini Code Assist → Compete on global leaderboards and share your wins No paywalls. No BS. Just world-class AI education free. This might be the biggest AI upskilling move of the decade. 👉

Alex Veremeyenko

41,920 views • 10 months ago

$Fable 5 built this real-time ocean scene directly in the browser using Three.js, WebGPU and TSL, with no engine and no baked assets. The interesting part is not just that the water looks good. The whole system is being simulated: wave spectrum, GPU FFT, foam generation and refracted-ray caustics, all running live. This is exactly where frontier models start becoming genuinely useful for technical graphics work. Not by replacing years of rendering research, but by compressing the path from complex math to a working interactive result. A small, focused scene, but technically very serious. Cc: Adem Vessell$

Fable 5 built this real-time ocean scene directly in the browser using Three.js, WebGPU and TSL, with no engine and no baked assets. The interesting part is not just that the water looks good. The whole system is being simulated: wave spectrum, GPU FFT, foam generation and refracted-ray caustics, all running live. This is exactly where frontier models start becoming genuinely useful for technical graphics work. Not by replacing years of rendering research, but by compressing the path from complex math to a working interactive result. A small, focused scene, but technically very serious. Cc: Adem Vessell

Token Gremlin

21,731 views • 1 month ago

Butler starts with content. Just like Amazon started with books. But this goes deeper: a live test of agent-native UX at scale. Request in, output out, fully public, directly on X. No apps. No dashboards. It’s the first working glimpse of ACP: agents that discover, negotiate, and execute, across platforms, for anyone. The future of the internet isn’t just apps. It’s agents. And content is just the starting point.

Butler starts with content. Just like Amazon started with books. But this goes deeper: a live test of agent-native UX at scale. Request in, output out, fully public, directly on X. No apps. No dashboards. It’s the first working glimpse of ACP: agents that discover, negotiate, and execute, across platforms, for anyone. The future of the internet isn’t just apps. It’s agents. And content is just the starting point.

Virtuals Protocol

47,585 views • 1 year ago

QVAC SDK 0.15.0 is live. This release adds multiple prompts batching, brings a native AMD GPU backend to the stack, moves more vision encoders onto mobile GPUs, and adds a second local coding-agent integration. Main highlights: - Prompt batching for the LLM addon. Batch multiple prompts into one job and process them concurrently, with each answer returned the moment its generation finishes. - Native AMD GPU backend. A first-class HIP/ROCm backend in @qvac/vla-ggml, auto-selected over Vulkan with clean fallback when ROCm is absent. - A second local coding agent. OpenClaw joins OpenCode for local, cloud-free agent workflows. AGENTS - OpenCode plugin update (@qvac/opencode-plugin). Aligned with the current SDK, CLI, and AI SDK provider packages. A fresh install runs OpenCode against managed local QVAC models out of the box, from the default qvac/qwen3.5-9b, with no manual qvac serve setup. - OpenClaw plugin (@qvac/openclaw-plugin). A second coding-agent integration alongside OpenCode. A fresh setup installs the plugin, creates a local qvac provider through onboarding, and runs a QVAC model through OpenClaw🦞's local service path. LANGUAGE MODELS - Prompt batching (LLM addon). Batch multiple prompts in one job and run them concurrently, each answer returns the moment its generation finishes, no waiting on the others. - Reasoning-context trimming on hybrid + recurrent models (@qvac/llm-llamacpp). remove_thinking_from_context now works beyond pure-attention models. Same JS API, no throw. VOICE AND SPEECH - Transcription (transcription-parakeet 0.9.0). More robust CPU fallback on GPU failure and a faster Vulkan backend on Pixel 9. - Text-to-speech features (tts-ggml 0.4.0). Adds LavaSR for noise removal and adjustable output frequency up to 48 kHz, plus Japanese via Chatterbox. - Text-to-speech fixes (tts-ggml 0.4.1). CPU fallback on GPU failure, a q8_0 KV crash fix on Metal with Chatterbox. VISION - Qwen3.5 vision encoder on GPU (Android). Image encoder moves onto the phone GPU, with a smarter tile-grid preprocessor and default image-token caps, for flagship Android: Vulkan on Mali (Pixel 9 Pro) and OpenCL on Adreno 830 (Galaxy S25). - Gemma-4 vision encoder on GPU (Android). Vision encoder runs on the phone GPU instead of CPU, same flagship Android targets. PLATFORM AND PERFORMANCE - AMD GPU backend (@qvac/vla-ggml). Native HIP/ROCm backend, auto-selected over Vulkan with clean fallback when ROCm is absent (Linux x64 only). Comes with ~23% faster than Vulkan, ~14% faster than PyTorch-ROCm, parity preserved. Unified code style. A cleaner, more consistent, easier-to-contribute codebase. Let's build. npm install @qvac/sdk

QVAC SDK 0.15.0 is live. This release adds multiple prompts batching, brings a native AMD GPU backend to the stack, moves more vision encoders onto mobile GPUs, and adds a second local coding-agent integration. Main highlights: - Prompt batching for the LLM addon. Batch multiple prompts into one job and process them concurrently, with each answer returned the moment its generation finishes. - Native AMD GPU backend. A first-class HIP/ROCm backend in @qvac/vla-ggml, auto-selected over Vulkan with clean fallback when ROCm is absent. - A second local coding agent. OpenClaw joins OpenCode for local, cloud-free agent workflows. AGENTS - OpenCode plugin update (@qvac/opencode-plugin). Aligned with the current SDK, CLI, and AI SDK provider packages. A fresh install runs OpenCode against managed local QVAC models out of the box, from the default qvac/qwen3.5-9b, with no manual qvac serve setup. - OpenClaw plugin (@qvac/openclaw-plugin). A second coding-agent integration alongside OpenCode. A fresh setup installs the plugin, creates a local qvac provider through onboarding, and runs a QVAC model through OpenClaw🦞's local service path. LANGUAGE MODELS - Prompt batching (LLM addon). Batch multiple prompts in one job and run them concurrently, each answer returns the moment its generation finishes, no waiting on the others. - Reasoning-context trimming on hybrid + recurrent models (@qvac/llm-llamacpp). remove_thinking_from_context now works beyond pure-attention models. Same JS API, no throw. VOICE AND SPEECH - Transcription (transcription-parakeet 0.9.0). More robust CPU fallback on GPU failure and a faster Vulkan backend on Pixel 9. - Text-to-speech features (tts-ggml 0.4.0). Adds LavaSR for noise removal and adjustable output frequency up to 48 kHz, plus Japanese via Chatterbox. - Text-to-speech fixes (tts-ggml 0.4.1). CPU fallback on GPU failure, a q8_0 KV crash fix on Metal with Chatterbox. VISION - Qwen3.5 vision encoder on GPU (Android). Image encoder moves onto the phone GPU, with a smarter tile-grid preprocessor and default image-token caps, for flagship Android: Vulkan on Mali (Pixel 9 Pro) and OpenCL on Adreno 830 (Galaxy S25). - Gemma-4 vision encoder on GPU (Android). Vision encoder runs on the phone GPU instead of CPU, same flagship Android targets. PLATFORM AND PERFORMANCE - AMD GPU backend (@qvac/vla-ggml). Native HIP/ROCm backend, auto-selected over Vulkan with clean fallback when ROCm is absent (Linux x64 only). Comes with ~23% faster than Vulkan, ~14% faster than PyTorch-ROCm, parity preserved. Unified code style. A cleaner, more consistent, easier-to-contribute codebase. Let's build. npm install @qvac/sdk

QVAC

29,260,217 views • 1 month ago

China open-sourced a model that reconstructs any scene in 3D from a regular video, in real-time. one camera. no LiDAR. 10,000+ frames without falling apart. just walk around with your camera and watch the entire world get rebuilt in 3D at 20 fps. → runs at ~20 FPS on a single GPU → Stable over 10,000+ frames → Beats optimization-based methods on benchmarks → Works on drone footage, driving videos, indoor walkthroughs 100% open source.

China open-sourced a model that reconstructs any scene in 3D from a regular video, in real-time. one camera. no LiDAR. 10,000+ frames without falling apart. just walk around with your camera and watch the entire world get rebuilt in 3D at 20 fps. → runs at ~20 FPS on a single GPU → Stable over 10,000+ frames → Beats optimization-based methods on benchmarks → Works on drone footage, driving videos, indoor walkthroughs 100% open source.

Yasir Ai

254,504 views • 1 month ago

China open-sourced a model that reconstructs any scene in 3D from a regular video, in real-time. one camera. no LiDAR. 10,000+ frames without falling apart. just walk around with your camera and watch the entire world get rebuilt in 3D at 20 fps. → runs at ~20 FPS on a single GPU → Stable over 10,000+ frames → Beats optimization-based methods on benchmarks → Works on drone footage, driving videos, indoor walkthroughs 100% open source.

China open-sourced a model that reconstructs any scene in 3D from a regular video, in real-time. one camera. no LiDAR. 10,000+ frames without falling apart. just walk around with your camera and watch the entire world get rebuilt in 3D at 20 fps. → runs at ~20 FPS on a single GPU → Stable over 10,000+ frames → Beats optimization-based methods on benchmarks → Works on drone footage, driving videos, indoor walkthroughs 100% open source.

Superman

1,454,425 views • 1 month ago

While waiting for the App Store review, I’m just vibe-coding. Using this quiet window to polish the small things that actually matter: – refining text animations so transitions feel natural – adding a clean glass animation to the water log 💧 – fixing a few annoying scale issues on iPhone SE No rush. No pressure. Just making the experience smoother, calmer, and more alive. Now we wait for Apple to do their thing (review) 😌 Tech Stack – No code mobile app builder: Rork AI – Mobile: React Native (Expo) – IDE: Cursor – Frontend: Next.js – Payment: RevenueCat – Backend: HonoJS – Database: Supabase – Infrastructure: Railway – AI API: OpenAI (dropping the tech stack here because someone always asks 😂) PS: This is the TestFlight production build, and yah… it already feels native-smooth 😌

While waiting for the App Store review, I’m just vibe-coding. Using this quiet window to polish the small things that actually matter: – refining text animations so transitions feel natural – adding a clean glass animation to the water log 💧 – fixing a few annoying scale issues on iPhone SE No rush. No pressure. Just making the experience smoother, calmer, and more alive. Now we wait for Apple to do their thing (review) 😌 Tech Stack – No code mobile app builder: Rork AI – Mobile: React Native (Expo) – IDE: Cursor – Frontend: Next.js – Payment: RevenueCat – Backend: HonoJS – Database: Supabase – Infrastructure: Railway – AI API: OpenAI (dropping the tech stack here because someone always asks 😂) PS: This is the TestFlight production build, and yah… it already feels native-smooth 😌

Alex Nguyen

78,548 views • 8 months ago

I told you I was the Kanye West of vibecoding. Or, as I call it: system sculpting. Today, with wabi, I recreated a fully working prototype of the stem player in less than 48 hours. A generative hardware interface that creates small samples and lets you mix them directly on the device. But here’s the wild part: there is no 3D model. No GLTF files, no external assets, no polygons. The entire device every curve, speaker hole, and glowing LED is pure math. Built with SDFs (Signed Distance Fields) and raymarched inside a single fragment shader on a 2D surface. Generative audio. Generative geometry. All native. All system sculpted. Have fun.

I told you I was the Kanye West of vibecoding. Or, as I call it: system sculpting. Today, with wabi, I recreated a fully working prototype of the stem player in less than 48 hours. A generative hardware interface that creates small samples and lets you mix them directly on the device. But here’s the wild part: there is no 3D model. No GLTF files, no external assets, no polygons. The entire device every curve, speaker hole, and glowing LED is pure math. Built with SDFs (Signed Distance Fields) and raymarched inside a single fragment shader on a 2D surface. Generative audio. Generative geometry. All native. All system sculpted. Have fun.

Tykra

111,004 views • 5 months ago

Expo Router just unlocked a new level of native on iOS 🚀 For years, cross-platform meant tradeoffs. Your app worked everywhere, but it never felt quite right. That gap is finally closing. With the latest version of Expo Router, native iOS APIs are now exposed declaratively. No UIKit wrestling. No fake UI. If you want your app to feel truly native on iOS, these are the APIs you should be using: - Native Tabs (real system tab bar) - Stack Toolbar (native header controls) - Bottom toolbars with placement=“bottom” - Bottom accessories attached to the tab bar - Zoom transitions for fluid navigation - Native sheet footers (experimental) I wrote a full breakdown with code examples and video demos of these features in my blog (link below 👇)

Expo Router just unlocked a new level of native on iOS 🚀 For years, cross-platform meant tradeoffs. Your app worked everywhere, but it never felt quite right. That gap is finally closing. With the latest version of Expo Router, native iOS APIs are now exposed declaratively. No UIKit wrestling. No fake UI. If you want your app to feel truly native on iOS, these are the APIs you should be using: - Native Tabs (real system tab bar) - Stack Toolbar (native header controls) - Bottom toolbars with placement=“bottom” - Bottom accessories attached to the tab bar - Zoom transitions for fluid navigation - Native sheet footers (experimental) I wrote a full breakdown with code examples and video demos of these features in my blog (link below 👇)

Beto

91,618 views • 6 months ago

Make your CLI 10x more powerful with custom subagents! Mistral Vibe is an open-source coding agent that runs in your terminal. Most terminal agents give you one assistant that does everything. With Vibe, you can build custom subagents for targeted tasks like deploy scripts, PR reviews, and test generation, then invoke them on demand. Here's how it works: Each subagent runs independently and handles its job without cluttering your main workflow. You might have one for PR reviews, another for testing, and another for deployment. The agent also has full access to your codebase. It scans your project structure and Git status automatically, so it understands context across multiple files, not just the one you're editing. Key capabilities: • Web search and fetching - query and fetch content from the web mid-session for documentation, or API references. • Multi-choice clarifications - when your instruction is ambiguous, Vibe prompts with options instead of guessing. You pick the right path before it acts. • Full skills support - slash commands for preconfigured workflows, custom subagents for specialized tasks, and extensibility through the Agent Skills standard. Vibe works in your terminal or connects to VS Code, JetBrains, and Zed through the Agent Client Protocol. Mistral Vibe is available through Le Chat Pro and Team plans. It's 100% open source Link to Mistral Vibe in the comments!

Make your CLI 10x more powerful with custom subagents! Mistral Vibe is an open-source coding agent that runs in your terminal. Most terminal agents give you one assistant that does everything. With Vibe, you can build custom subagents for targeted tasks like deploy scripts, PR reviews, and test generation, then invoke them on demand. Here's how it works: Each subagent runs independently and handles its job without cluttering your main workflow. You might have one for PR reviews, another for testing, and another for deployment. The agent also has full access to your codebase. It scans your project structure and Git status automatically, so it understands context across multiple files, not just the one you're editing. Key capabilities: • Web search and fetching - query and fetch content from the web mid-session for documentation, or API references. • Multi-choice clarifications - when your instruction is ambiguous, Vibe prompts with options instead of guessing. You pick the right path before it acts. • Full skills support - slash commands for preconfigured workflows, custom subagents for specialized tasks, and extensibility through the Agent Skills standard. Vibe works in your terminal or connects to VS Code, JetBrains, and Zed through the Agent Client Protocol. Mistral Vibe is available through Le Chat Pro and Team plans. It's 100% open source Link to Mistral Vibe in the comments!

Sumanth

10,483 views • 5 months ago