--- title: "Workflow | Netlify Changelog" description: "Get the latest updates on Netlify products and features to meet your developer needs." source: "https://preview--www.netlify.app/changelog/tag/workflow/" last_updated: "2026-10-29T12:15:05.000Z" --- # Posts tagged "Workflow" All Tags Agent-runners AI Ai-gateway Angular Astro AX Billing Build CLI Database Design Devtools Domains E-commerce Edge-functions Extensions Forms Framework Functions Logs Next.js Nuxt.js Remix SDK Security Sveltekit Updates Workflow [Subscribe to feed](https://www.netlify.com/changelog/tag/workflow/feed.xml) - [ ## Build and deploy to Netlify from Grok ](/changelog/2026-10-23-netlify-connector-for-grok/) October 23, 2026 - [ai](/changelog/tag/ai/) - [workflow](/changelog/tag/workflow/) You can now connect Netlify to [Grok](https://grok.com/) with the Netlify connector, so your Grok agent can answer questions about your projects, update supported project settings, and deploy to Netlify through conversation. The connector gives Grok up-to-date context for building and deploying to Netlify, and it works across Grok Bot, Grok CLI, and [grok.com](https://grok.com/). You don’t need to call the connector by name. Describe what you want, and when the task needs Netlify access, Grok uses the connector for you. For example, you can ask Grok to: - “Deploy this project to Netlify.” - “What’s the status of my latest deploy?” - “Show me my Netlify projects.” - “Build me a website for my restaurant and deploy it to Netlify.” To get started, open [Connectors](https://grok.com/connectors) in Grok, search for **Netlify**, then select **Add** and follow the setup prompts. You’ll need a Grok account with access to connectors and a [Netlify account](https://app.netlify.com/signup). Learn more in our guide to [setting up Grok for Netlify](https://docs.netlify.com/build/build-with-ai/agent-setup-guides/set-up-grok-for-netlify/). [Permalink to Build and deploy to Netlify from Grok Permalink](/changelog/2026-10-23-netlify-connector-for-grok/) - [ ## Introducing the Support Hub ](/changelog/2026-10-16-support-tickets-in-the-netlify-ui/) October 16, 2026 - [workflow](/changelog/tag/workflow/) Enterprise teams can now create, track, and reply to support tickets without leaving Netlify in our new Support Hub. Go to **User settings > Support** to see your tickets, check their status, and continue your conversation with the Netlify support team. Team Owners can see every ticket their team members created, not just their own. The **Requester** column shows who opened each ticket. Members on your team can only view the tickets they opened. ## What you can do - **Create tickets** with a subject, a Markdown description, and CC recipients. - **Track progress** with clear statuses: Open, Awaiting customer response, and Closed. - **Search, sort, and filter** your tickets, including tickets you’re CC’d on. - **Reply from the dashboard.** Your reply goes straight to the support team. ## Not on Enterprise? Support is available on every plan, including Free plans. Use the [Netlify Support page](https://www.netlify.com/support/) or email [support@netlify.com](mailto:support@netlify.com). ## Learn more Learn more from our [Support Hub guide](https://docs.netlify.com/manage/support/overview/) [Permalink to Introducing the Support Hub Permalink](/changelog/2026-10-16-support-tickets-in-the-netlify-ui/) - [ ## Subscribe to Netlify events from ChatGPT ](/changelog/2026-10-07-subscribe-to-netlify-events-from-chatgpt/) October 7, 2026 - [ai](/changelog/tag/ai/) - [workflow](/changelog/tag/workflow/) - [extensions](/changelog/tag/extensions/) You can now subscribe to Netlify events from ChatGPT and set up automations that respond to what’s happening on your sites. Instead of checking the Netlify dashboard or waiting on an email, you can have ChatGPT act as soon as something happens. Events you can subscribe to include: - A deploy succeeded - A build failed - A form submission came in For more events to subscribe to, check out our [deploy events](https://docs.netlify.com/deploy/deploy-notifications/). ## Combine events with Netlify plugin and MCP server Events get more useful when you pair them with everything else you can already do through the [Netlify ChatGPT plugin](https://openai.com/business/plugins/netlify/) and [Netlify MCP server](https://docs.netlify.com/build/build-with-ai/agent-setup-guides/agent-setup-overview/#mcp-server-support). For example, you could set up an automation that: - Reviews new form submissions and flags the ones that need a follow-up - Summarizes what changed when a production deploy succeeds Because these automations live in ChatGPT, you can describe what you want in plain language and adjust it as your workflow changes. ## Get started Connect Netlify in ChatGPT, then ask it to subscribe to the events you care about for your project. Learn more in our guide to [using Netlify with ChatGPT](https://docs.netlify.com/build/build-with-ai/agent-setup-guides/use-netlify-with-chatgpt/). [Permalink to Subscribe to Netlify events from ChatGPT Permalink](/changelog/2026-10-07-subscribe-to-netlify-events-from-chatgpt/) - [ ## Comment on specific lines of code in Agent Runners ](/changelog/2026-10-06-agent-runners-diff-line-comments/) October 6, 2026 - [agent runners](/changelog/tag/agent-runners/) - [ai](/changelog/tag/ai/) - [workflow](/changelog/tag/workflow/) You can now add comments to individual lines in the diff on the **Code** tab of Agent Runners, so you can give your agent precise feedback on the code it generated. Previously, asking for a fix meant describing where the problem was in your prompt, such as naming the file, quoting the code, or explaining which function you meant. Now you can pinpoint exactly where you want changes. Open the **Code** tab for an agent run, select the **+** next to a line in the diff, and leave a comment about what you want changed. Your comments are sent along with your next prompt, so the agent knows exactly which code lines you’re referring to. ![Agent Runners Code tab showing a diff of index.html with a comment box open on line 278 that reads “use class name subdued instead” and an Add comment button](/images/changelog/agent-runners-diff-line-comment.png) This makes follow-up prompts more useful when you want to: - Correct a specific bug or edge case without rewriting the whole request - Ask for a different approach in one part of a change while keeping the rest - Flag naming, styling, or structure issues right where they appear - Leave feedback on several spots across multiple files in a single follow-up run Try it on your next [agent run](https://app.netlify.com/start), or learn more about [making changes with Agent Runners](https://docs.netlify.com/build/build-with-ai/agent-runners/make-changes-with-agent-runners/). [Permalink to Comment on specific lines of code in Agent Runners Permalink](/changelog/2026-10-06-agent-runners-diff-line-comments/) - [ ## Prompt and preview in one view with Agent Runners ](/changelog/2026-09-28-agent-runners-side-by-side-preview/) September 28, 2026 - [agent runners](/changelog/tag/agent-runners/) - [ai](/changelog/tag/ai/) - [workflow](/changelog/tag/workflow/) Agent Runners now shows you a preview right next to your prompt. Previously, you’d get a link to the Deploy Preview and have to open it in a separate tab to see what the agent changed. Now the preview appears inline, so you can review the result and write your next prompt without switching back and forth. Plus, you can still access the [Deploy Preview link](https://docs.netlify.com/deploy/compare-preview-options/#preview-within-agent-runners) if you need it. This makes iterating with an agent feel more like a conversation. See what changed, spot what’s off, and follow up with the next instruction, all in one view. ## Example flow For example, say you’re building a strategic task organizer and prompt your agent to add a button that generates a quarterly impact report. Now you can watch your agent’s updates in the side preview next to your prompt. ![Agent Runners side-by-side view showing a chat prompt to add a quarterly report button next to the live Deploy Preview of the resulting task organizer app](/images/changelog/side-by-side-preview-example.png) In this example, your agent on Netlify will also let you know if your project cannot save your tasks across browser sessions yet, and you can approve adding a database in the same view. This is just one example of how Netlify gives you professional-grade capabilities, such as a real working database, with your agent of choice when you prompt with [Agent Runners](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). ## Try it out See it in action when you [start a new agent run](https://app.netlify.com/start) or learn more about [working with agents on Netlify](https://docs.netlify.com/build/build-with-ai/agent-runners/make-changes-with-agent-runners/). [Permalink to Prompt and preview in one view with Agent Runners Permalink](/changelog/2026-09-28-agent-runners-side-by-side-preview/) - [ ## New project activity feed ](/changelog/2026-09-24-new-activity-feed/) September 24, 2026 - [workflow](/changelog/tag/workflow/) - [agent runners](/changelog/tag/agent-runners/) As part of our ongoing work to simplify the [Netlify dashboard](https://app.netlify.com), we’ve added an activity feed to the project overview page. It’s available on all plans and adapts to how your project is set up. Now when you open a project, the activity feed gives you a snapshot of your project’s latest updates, with quick access to: - Production versions of your project, including the version last published - Preview versions of your project - Agent runs, so you can see what agents are working on and what you and your teammates have prompted ![Project activity feed in the Netlify dashboard listing recent activity newest first, with filters for All, Production, Previews, and Agent runs. Entries include an in-progress agent run, a published production deploy, and two branch deploys with Preview links.](/images/changelog/project-activity-feed.png) This means that instead of tracking down Production deploy links, Deploy Preview links, branch deploy links, and your agent runs list separately, you can now see where your project stands at a glance in one single spot. The feed also suggests next steps to help you get started. It’s one of several dashboard improvements we’re gradually rolling out to simplify the Netlify experience, so you may have spotted a few already, with more to come. [Permalink to New project activity feed Permalink](/changelog/2026-09-24-new-activity-feed/) - [ ## Agent Runners: Get a working result when low on credits ](/changelog/2026-09-14-agent-runners-wrap-up-before-credit-limit/) September 14, 2026 - [agent runners](/changelog/tag/agent-runners/) - [ai](/changelog/tag/ai/) - [workflow](/changelog/tag/workflow/) Agent Runners are now better at completing their work when a run has less credits remaining than the task requires. If you are close to running our of credits during a run, the agent will start focusing on delivering the most useful result it can with the credits it has left. It finishes work already in progress, leaves the project in a working state, and provides a clear summary of what it completed. Previously, an ambitious task could end abruptly before the agent wrapped up, leaving partial changes and little explanation. Now, you’re more likely to get a working result you can use right away, or a solid, clearly documented starting point for your next run. This improvement applies automatically to every agent and model available in Agent Runners. There’s nothing to enable or configure. Learn more in [Make changes with Agent Runners](https://docs.netlify.com/build/build-with-ai/agent-runners/make-changes-with-agent-runners/) and [how credits work](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/). [Permalink to Agent Runners: Get a working result when low on credits Permalink](/changelog/2026-09-14-agent-runners-wrap-up-before-credit-limit/) - [ ## Social media share buttons ](/changelog/2026-09-11-social-media-share-buttons/) September 11, 2026 - [workflow](/changelog/tag/workflow/) Sharing your Netlify projects is now faster with built-in social media share buttons. When you’re ready to show off what you’ve built, you can share your project directly to X, LinkedIn, Reddit, Facebook, or Bluesky. Choose your preferred platform and Netlify opens a ready-to-publish post with your project link, so you can reach your community with fewer steps. [Permalink to Social media share buttons Permalink](/changelog/2026-09-11-social-media-share-buttons/) - [ ## Cursor Origin now supported as a Git provider ](/changelog/2026-09-10-cursor-origin-git-provider/) September 10, 2026 - [devtools](/changelog/tag/devtools/) - [workflow](/changelog/tag/workflow/) You can now connect repositories hosted on [Cursor Origin](https://cursor.com/docs/origin) to Netlify, so every Git push deploys an updated version of your project at a preview URL or a production URL. Netlify supports [Cursor Origin](https://cursor.com/docs/origin) with continuous deployment, meaning that once your codebase’s repo is connected, Netlify will automatically: - Build and deploy your project with every git push - Build Deploy Previews for your pull requests - Send deploy notifications to your pull request comments on Cursor Origin so you can check preview URLs there ## Requirements Cursor Origin uses OAuth authentication, so connecting a repo works much like our existing Azure DevOps support: the Cursor user who authenticates needs access to the Cursor Origin codebase that owns the repository. To use Cursor Origin with Netlify, you do not need a specific pricing plan with Netlify. ## Support scope Note that features outside of continuous deployment, such as Agent Runners and the Netlify Drawer, are not supported at this time. ## Get started To learn more, check out these docs: - [Get started Cursor Origin](https://docs.netlify.com/build/git-workflows/repo-permissions-linking#get-started-with-cursor-origin) - [Link your repo to your Netlify project](https://docs.netlify.com/manage/projects/connect-project-to-repo/) - [Deploy a new project to Netlify from your Cursor Origin repo](https://docs.netlify.com/start/quickstarts/deploy-from-repository/) [Permalink to Cursor Origin now supported as a Git provider Permalink](/changelog/2026-09-10-cursor-origin-git-provider/) [Next page](/changelog/tag/workflow/page/2)