From bdb86f4e59b98bd1ebb681620a1a705d0845d7f1 Mon Sep 17 00:00:00 2001 From: shaziya <99940835+shaziyabandukia@users.noreply.github.com> Date: Tue, 13 Oct 2026 08:56:13 -0700 Subject: [PATCH] chore(www): add blog post: Ship changes to your Supabase backend with Grok Bot (#51430) ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? New blog post (www): "Ship changes to your Supabase backend with Grok Bot", announcing Supabase joining the SpaceXAI Partner Network. ## What is the current behavior? N/A ## What is the new behavior? Adds `/blog/ship-changes-to-your-supabase-backend-with-grok-bot`, dated 2026-10-13, with Nick Littman, Elsa Heffernan, and Shaziya Bandukia as authors. ## Additional context Also updates Nick Littman's title in `authors.json` to Solution Architect. --------- Co-authored-by: dshukertjr --- ...to-your-supabase-backend-with-grok-bot.mdx | 66 ++++++++++++++++++ apps/www/lib/authors.json | 2 +- .../og.png | Bin 0 -> 272557 bytes .../thumb.png | Bin 0 -> 40897 bytes 4 files changed, 67 insertions(+), 1 deletion(-) create mode 100644 apps/www/_blog/2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot.mdx create mode 100644 apps/www/public/images/blog/2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot/og.png create mode 100644 apps/www/public/images/blog/2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot/thumb.png diff --git a/apps/www/_blog/2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot.mdx b/apps/www/_blog/2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot.mdx new file mode 100644 index 00000000000..53d3a612f63 --- /dev/null +++ b/apps/www/_blog/2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot.mdx @@ -0,0 +1,66 @@ +--- +title: 'Ship changes to your Supabase backend with Grok Bot' +description: 'Supabase joins the SpaceXAI Partner Network: request a change in chat with Grok Bot, and Cursor builds and runs it on your Supabase backend.' +author: nick_littman, elsa_heffernan, shaziya_bandukia +date: '2026-10-13' +categories: + - product +tags: + - ai + - integrations + - mcp +imgSocial: '2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot/og.png' +imgThumb: '2026-10-13-ship-changes-to-your-supabase-backend-with-grok-bot/thumb.png' +toc_depth: 2 +--- + +Supabase is joining the SpaceXAI Partner Network. With Grok Bot connected to Cursor, anyone on your team can request a change in chat, and Cursor builds and runs it against your Supabase backend through the [Supabase MCP server](https://supabase.com/docs/guides/getting-started/mcp). + +Grok Bot takes a request from the person who needs it, in the place they already work, and hands it to Cursor as scoped engineering work. Cursor writes and runs the code, and through the Supabase MCP server, it can query the database, inspect the schema, read logs, and deploy Supabase Edge Functions, all inside the one Supabase project where the data already lives. + +
+