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.

Supabase local dev just got much better for agents • Run locally without Docker • Multiple Supabase instances per repo/worktree • Declarative Schemas 2.0 with pg-delta generating migrations • Auth, API & storage config now lives in code

Supabase

211,147 subscribers

97,571 views • 2 days ago •via X (Twitter)

Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Make sure you install the Supabase plugin for AI coding agents when building apps with AI and Supabase

Make sure you install the Supabase plugin for AI coding agents when building apps with AI and Supabase

Supabase

12,420 views • 4 months ago

Supabase dashboard now supports transactions! Enable it from Account Preferences menu to try it out!

Supabase dashboard now supports transactions! Enable it from Account Preferences menu to try it out!

Supabase

55,423 views • 5 months ago

Here is Cursor building a Next.js + Supabase app, fetching a Supabase URL and anonymous key, and saving them to an env file for Next.js to consume:

Here is Cursor building a Next.js + Supabase app, fetching a Supabase URL and anonymous key, and saving them to an env file for Next.js to consume:

Supabase

24,616 views • 1 year ago

bbq anyone?

bbq anyone?

Supabase

115,562 views • 3 years ago

waiting till I'm offline -

waiting till I'm offline -

Supabase

60,800 views • 2 years ago

let's get this bread

let's get this bread

Supabase

119,408 views • 9 months ago

Launching Supabase-labs/tanstack-db, a TanStack DB collection adapter backed by Supabase. It supports live queries, optimistic mutations, automatic Realtime sync, and is fully typed. Currently in alpha. Try it out, and let us know any feedback!

Launching Supabase-labs/tanstack-db, a TanStack DB collection adapter backed by Supabase. It supports live queries, optimistic mutations, automatic Realtime sync, and is fully typed. Currently in alpha. Try it out, and let us know any feedback!

Supabase

39,850 views • 3 months ago

British devs every time they type "color" in CSS 🛀

British devs every time they type "color" in CSS 🛀

Supabase

528,461 views • 3 years ago

Meet the founders! Get your tickets today to hear all the announcements we will make at Supabase Select on October 2!

Meet the founders! Get your tickets today to hear all the announcements we will make at Supabase Select on October 2!

Supabase

11,418 views • 2 months ago

when bro's pr has -- and emojis

when bro's pr has -- and emojis

Supabase

124,668 views • 6 months ago

signing up to a competitor's product and hoping they won't notice

signing up to a competitor's product and hoping they won't notice

Supabase

25,014 views • 2 years ago

Postgres Changes now supports AND filters and column selection. You can match on more than one column in a single subscription, and pick which columns come back in the payload.

Postgres Changes now supports AND filters and column selection. You can match on more than one column in a single subscription, and pick which columns come back in the payload.

Supabase

13,274 views • 2 months ago

We're rolling out a new Edge Function Overview page. Open a function and see how it's running: error rates, execution time, and how much CPU and memory it uses.

We're rolling out a new Edge Function Overview page. Open a function and see how it's running: error rates, execution time, and how much CPU and memory it uses.

Supabase

13,133 views • 2 months ago

Grok 4.5 is now in Codex now too. No API key, no billing setup, no config file. If you have X Premium, you sign in with your X account and Grok 4.5 runs inside your Codex. OAuth handles it. Your subscription is your access. That's it. And Grok 4.5 just got a lot better, so if you already pay for X Premium, you can now run it in Codex for free.

Grok 4.5 is now in Codex now too. No API key, no billing setup, no config file. If you have X Premium, you sign in with your X account and Grok 4.5 runs inside your Codex. OAuth handles it. Your subscription is your access. That's it. And Grok 4.5 just got a lot better, so if you already pay for X Premium, you can now run it in Codex for free.

Ziwen

111,187 views • 2 months ago

The Visual Studio Code insiders version that just shipped and will ship in the next few days will come with an insane amount of new capabilities. A few highlights: - You can now run sub-agents in parallel. Yes, really. I even attached a video. - Major UX improvements for sub agents, especially visible in the chat window - A new search tool wrapped as a sub-agent that iteratively runs multiple search tools: semantic_search, file_search, grep_search Which connects nicely to the point above: multiple searches running in parallel, efficiently and fast - Anthropic’s Message API is now enabled by default - You can choose the model for the cloud agent (three available, all premium) - Extended thinking support when using the Claude cloud agent This is part of the broader multi-vendor cloud support under AgentsHQ I wrote about a few weeks ago - Tasks sent to the background agent (basically the CLI tool) now always run in isolation, each with its own git worktree - In a multi-repo workspace, assigning a task to a cloud agent prompts you to choose the target repo Same behavior when opening an empty workspace with no repo - Support for building an external index for files not supported by GitHub’s default indexing - UI/UX improvements for starting new sessions and switching between local / background / cloud agents - Skills are now first-class citizens, just like prompt files, with better UX indicating when a skill is loaded - Improved API for dynamic contribution of prompt files New V2 includes skills as part of the model. Curious to see the extensions that will leverage this - Finally, initial support for showing context usage percentage per session - Skills are enabled by default - Resizable chat window and session view. Small thing, but it was driving me crazy 😁 - A new integrated browser meant to replace the old simple browser Maybe the beginning of real browser use? - Better UI/UX for token streaming in chat - Ability to index external files not supported by GitHub There’s a lot more. Some of it hasn’t fully landed yet, but everything that has is already in Insiders. The next stable release should drop in early February. As usual, I’m just shocked by the volume of features this team ships every month. After the holiday slowdown, this one is shaping up to be a wild release.

The Visual Studio Code insiders version that just shipped and will ship in the next few days will come with an insane amount of new capabilities. A few highlights: - You can now run sub-agents in parallel. Yes, really. I even attached a video. - Major UX improvements for sub agents, especially visible in the chat window - A new search tool wrapped as a sub-agent that iteratively runs multiple search tools: semantic_search, file_search, grep_search Which connects nicely to the point above: multiple searches running in parallel, efficiently and fast - Anthropic’s Message API is now enabled by default - You can choose the model for the cloud agent (three available, all premium) - Extended thinking support when using the Claude cloud agent This is part of the broader multi-vendor cloud support under AgentsHQ I wrote about a few weeks ago - Tasks sent to the background agent (basically the CLI tool) now always run in isolation, each with its own git worktree - In a multi-repo workspace, assigning a task to a cloud agent prompts you to choose the target repo Same behavior when opening an empty workspace with no repo - Support for building an external index for files not supported by GitHub’s default indexing - UI/UX improvements for starting new sessions and switching between local / background / cloud agents - Skills are now first-class citizens, just like prompt files, with better UX indicating when a skill is loaded - Improved API for dynamic contribution of prompt files New V2 includes skills as part of the model. Curious to see the extensions that will leverage this - Finally, initial support for showing context usage percentage per session - Skills are enabled by default - Resizable chat window and session view. Small thing, but it was driving me crazy 😁 - A new integrated browser meant to replace the old simple browser Maybe the beginning of real browser use? - Better UI/UX for token streaming in chat - Ability to index external files not supported by GitHub There’s a lot more. Some of it hasn’t fully landed yet, but everything that has is already in Insiders. The next stable release should drop in early February. As usual, I’m just shocked by the volume of features this team ships every month. After the holiday slowdown, this one is shaping up to be a wild release.

Oren Melamed

29,555 views • 8 months ago

A peanut-sized Chinese model just dethroned Gemini at reading documents. GLM-OCR is a 0.9B parameter vision-language model. It scores 94.62 on OmniDocBench V1.5, ranking #1 overall. For context, it outperforms models 100x its size. 100% open-source. It works in two stages. 1. A layout engine detects every region in a document. 2. Each region gets read in parallel. The model predicts multiple tokens per step instead of one. That's what makes it so fast at small size. It handles things most OCR tools struggle with: > Complex tables and nested layouts > Handwritten text and stamps > Math formulas and code blocks > Mixed image-and-text documents You can run it locally through Ollama. It fits on edge devices with limited compute. Every expensive OCR API just got a free competitor.

A peanut-sized Chinese model just dethroned Gemini at reading documents. GLM-OCR is a 0.9B parameter vision-language model. It scores 94.62 on OmniDocBench V1.5, ranking #1 overall. For context, it outperforms models 100x its size. 100% open-source. It works in two stages. 1. A layout engine detects every region in a document. 2. Each region gets read in parallel. The model predicts multiple tokens per step instead of one. That's what makes it so fast at small size. It handles things most OCR tools struggle with: > Complex tables and nested layouts > Handwritten text and stamps > Math formulas and code blocks > Mixed image-and-text documents You can run it locally through Ollama. It fits on edge devices with limited compute. Every expensive OCR API just got a free competitor.

AlphaSignal

92,302 views • 6 months ago

A peanut-sized Chinese model just dethroned Gemini at reading documents. GLM-OCR is a 0.9B parameter vision-language model. It scores 94.62 on OmniDocBench V1.5, ranking #1 overall. For context, it outperforms models 100x its size. 100% open-source. It works in two stages. 1. A layout engine detects every region in a document. 2. Each region gets read in parallel. The model predicts multiple tokens per step instead of one. That's what makes it so fast at small size. It handles things most OCR tools struggle with: > Complex tables and nested layouts > Handwritten text and stamps > Math formulas and code blocks > Mixed image-and-text documents You can run it locally through Ollama. It fits on edge devices with limited compute. Every expensive OCR API just got a free competitor.

A peanut-sized Chinese model just dethroned Gemini at reading documents. GLM-OCR is a 0.9B parameter vision-language model. It scores 94.62 on OmniDocBench V1.5, ranking #1 overall. For context, it outperforms models 100x its size. 100% open-source. It works in two stages. 1. A layout engine detects every region in a document. 2. Each region gets read in parallel. The model predicts multiple tokens per step instead of one. That's what makes it so fast at small size. It handles things most OCR tools struggle with: > Complex tables and nested layouts > Handwritten text and stamps > Math formulas and code blocks > Mixed image-and-text documents You can run it locally through Ollama. It fits on edge devices with limited compute. Every expensive OCR API just got a free competitor.

Jafar Najafov

13,630 views • 5 months ago

Seems like Visual Studio Code is starting to tell you: your agent primitives need to move. There is now a new migration banner in the Chat panel, and it is part of a much bigger change happening under the hood: the move from the old Local harness to the new Agent Host architecture built around AHP. This is not just about moving where an agent runs. The old model was very VS Code-centric: prompts, custom agents, instructions and skills could live in VS Code-specific locations and the agent runtime lived inside the extension host. The new Agent Host separates the agent runtime from the editor. Sessions can keep running when the window closes, be shared across VS Code windows, run remotely, and support different harnesses such as Copilot, CLI and Copilot Desktop App through a common session layer. And that means some of our primitives need to move too. Prompt files are being deprecated for Agent Host and migrated to Skills. User-level agents and instructions that lived in VS Code profile storage need to move to harness-supported locations. Even the old location settings are being deprecated. The new migration experience can detect these things and guide you through moving or converting them, while keeping the originals unless you explicitly remove them. The new banner is basically the first visible sign that this migration is becoming a real product workflow. Basically telling us - it's time to move on!!!! If you have accumulated a lot of prompts, custom agents, instructions and skills over the last year, now is probably a good time to understand where they actually live and which harness owns them. To summarize the shift - it isn't just: VS Code Chat → Agent Host It is: VS Code-specific primitives → harness-native primitives. And I think this is going to become increasingly important as agents stop being features inside an IDE and become runtimes that multiple clients can connect to. Go run your migrations now 🏃‍♀️

Oren Melamed

29,753 views • 4 days ago

Holy shit... Keygraph just built an AI that hacks your web app before hackers do. It's called Shannon and it's a fully autonomous AI pentester that finds REAL exploits, not just alerts. 96.15% success rate on the hint-free XBOW Benchmark. Your team ships code every day with Claude Code and Cursor. Your pentest? Once a year. That's 364 days of shipping vulnerabilities to production. Shannon closes that gap. What it actually does: → Autonomously hunts attack vectors in your source code → Uses a built-in browser to execute real exploits → Handles 2FA/TOTP logins with zero intervention → Delivers copy-paste Proof-of-Concepts (no false positives) → Runs Nmap, Subfinder, WhatWeb, Schemathesis under the hood Real results on OWASP Juice Shop in a single run: → 20+ high-impact vulnerabilities found → Complete auth bypass + full database exfiltration → Privilege escalation to admin via registration bypass → SSRF enabling internal network recon → Systemic IDOR across user data The architecture is what makes it work. 4 phases: Recon → Vuln Analysis → Exploitation → Reporting Specialized agents run in parallel for Injection, XSS, SSRF, and Broken Auth. Strict "No Exploit, No Report" policy kills false positives at the source. Covers the critical OWASP classes: - Injection - XSS - SSRF - Broken Authentication & Authorization One command. ~1 hour runtime. ~$50 per full pentest with Claude Sonnet. Every Claude (coder) deserves their Shannon. The Red Team to your vibe-coding Blue Team. 100% Opensource (AGPL-3.0). 10.6k stars already. Repo in reply ↓

Holy shit... Keygraph just built an AI that hacks your web app before hackers do. It's called Shannon and it's a fully autonomous AI pentester that finds REAL exploits, not just alerts. 96.15% success rate on the hint-free XBOW Benchmark. Your team ships code every day with Claude Code and Cursor. Your pentest? Once a year. That's 364 days of shipping vulnerabilities to production. Shannon closes that gap. What it actually does: → Autonomously hunts attack vectors in your source code → Uses a built-in browser to execute real exploits → Handles 2FA/TOTP logins with zero intervention → Delivers copy-paste Proof-of-Concepts (no false positives) → Runs Nmap, Subfinder, WhatWeb, Schemathesis under the hood Real results on OWASP Juice Shop in a single run: → 20+ high-impact vulnerabilities found → Complete auth bypass + full database exfiltration → Privilege escalation to admin via registration bypass → SSRF enabling internal network recon → Systemic IDOR across user data The architecture is what makes it work. 4 phases: Recon → Vuln Analysis → Exploitation → Reporting Specialized agents run in parallel for Injection, XSS, SSRF, and Broken Auth. Strict "No Exploit, No Report" policy kills false positives at the source. Covers the critical OWASP classes: - Injection - XSS - SSRF - Broken Authentication & Authorization One command. ~1 hour runtime. ~$50 per full pentest with Claude Sonnet. Every Claude (coder) deserves their Shannon. The Red Team to your vibe-coding Blue Team. 100% Opensource (AGPL-3.0). 10.6k stars already. Repo in reply ↓

Guri Singh

20,591 views • 6 months ago

single RTX 3090. 24 GB VRAM. Qwen3.5-35B-A3B. 4-bit quant, 113 tokens per second at full 262K context harnessing Claude Code locally with no API, no subscription, no proxy. told it what it is. 30 Mamba2 layers, 10 attention, 256 experts, 8 active per token. said "build something that shows off what you can do." it visualized its own architecture. interactive. tokens flowing through layers. 256 experts lighting up on routing. served in the browser from the same GPU running inference. single prompt. then i said level up. 3D. Three.js. separate files. flythrough camera. clickable layers. it planned first, scaffolded 6 files, hit one API bug, fixed it itself, then optimized for smooth framerate. two iterations to a working 3D neural network explorer. llama.cpp just merged a native Anthropic endpoint. Claude Code points at localhost. the whole setup is two commands. no LiteLLM. no proxy config. the open source models coming out of china right now are genuinely changing what's possible on consumer hardware. respect to the Qwen team. this is acceleration.

single RTX 3090. 24 GB VRAM. Qwen3.5-35B-A3B. 4-bit quant, 113 tokens per second at full 262K context harnessing Claude Code locally with no API, no subscription, no proxy. told it what it is. 30 Mamba2 layers, 10 attention, 256 experts, 8 active per token. said "build something that shows off what you can do." it visualized its own architecture. interactive. tokens flowing through layers. 256 experts lighting up on routing. served in the browser from the same GPU running inference. single prompt. then i said level up. 3D. Three.js. separate files. flythrough camera. clickable layers. it planned first, scaffolded 6 files, hit one API bug, fixed it itself, then optimized for smooth framerate. two iterations to a working 3D neural network explorer. llama.cpp just merged a native Anthropic endpoint. Claude Code points at localhost. the whole setup is two commands. no LiteLLM. no proxy config. the open source models coming out of china right now are genuinely changing what's possible on consumer hardware. respect to the Qwen team. this is acceleration.

Sudo su

110,464 views • 7 months ago