--- title: "Workflow | Netlify Changelog" description: "Get the latest updates on Netlify products and features to meet your developer needs." source: "https://www.netlify.com/changelog/tag/workflow/" last_updated: "2026-08-29T08:20:52.000Z" --- # Posts tagged "Workflow" All Tags Agent-runners AI Ai-gateway Angular Astro AX Build CLI Database Design Devtools Domains E-commerce Extensions Forms Framework Functions Logs Next.js Nuxt.js Remix SDK Security Updates Workflow [Subscribe to feed](https://www.netlify.com/changelog/tag/workflow/feed.xml) - [ ## GitHub stacked pull requests now create Deploy Previews ](/changelog/2026-08-27-github-stacked-pull-request-deploy-previews/) August 27, 2026 - [devtools](/changelog/tag/devtools/) - [workflow](/changelog/tag/workflow/) Netlify now creates a [Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/) for every pull request in a GitHub stack when the stack ultimately targets your project’s [production branch](https://docs.netlify.com/deploy/deploy-types/production-deploy/) (usually `main`). You can review and share each layer of a larger change before it merges. ![A GitHub stacked pull request showing a successful Netlify Deploy Preview check](/images/changelog/github-stacked-pull-request-deploy-preview.png) [GitHub Stacked Pull Requests](https://github.blog/changelog/2026-07-30-stacked-pull-requests-are-now-in-public-preview/) help teams split a larger update into smaller, connected pull requests. Each pull request can focus on one step of the work, making changes easier to review and merge in sequence. Previously, Netlify only created a Deploy Preview for the first pull request in your stack while additional pull requests in the stack didn’t get their own Deploy Previews. Now, every pull request in the stack gets its own Deploy Preview. There’s nothing new to configure. Create and update your stack in GitHub as usual, and Netlify automatically adds a Deploy Preview to each eligible pull request. ## Learn More - [Get an overview of GitHub Stacked Pull Requests](https://github.github.com/gh-stack/introduction/overview/) - [Follow GitHub’s quick start for creating a stack](https://github.github.com/gh-stack/getting-started/quick-start/) [Permalink to GitHub stacked pull requests now create Deploy Previews Permalink](/changelog/2026-08-27-github-stacked-pull-request-deploy-previews/) - [ ## Pre-launch toolbar and the Powered by Netlify badge ](/changelog/2026-08-19-pre-launch-toolbar-and-powered-by-netlify-badge/) August 19, 2026 - [workflow](/changelog/tag/workflow/) - [agent runners](/changelog/tag/agent-runners/) Private projects on Netlify will now show a pre-launch toolbar so you can share your project for review and run audits using AI checks before you make your project public. Private projects and agent runs require a [Credit pricing plan](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/). If you’re on a Legacy pricing plan, you will not have access to the pre-launch toolbar. Audits consume credits like any other [agent run](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). For public projects, **new projects created on a Free plan on or after August 19, 2026 show a Powered by Netlify badge to all visitors**. The badge is configurable for each project through your project configuration settings. To turn the Netlify badge on or off for all visitors of your site: 1. Go to **Project configuration > General > Powered by Netlify badge** and turn it on or off. Additionally, any visitor can hide the badge for themselves, and that choice is stored locally on their browser and never reaches Netlify. All projects created before August 19, 2026 have the badge off by default. Users on a Credit-based Personal and Pro plans can also turn the badge on or off per-project. For these plans, the badge is always off by default. ## Release timeline We’re rolling both overlays out gradually over the next few weeks, so a project that qualifies may not have them yet. Learn more about the [pre-launch toolbar](https://docs.netlify.com/manage/projects/pre-launch-toolbar/) and the [Powered by Netlify badge](https://docs.netlify.com/manage/projects/powered-by-netlify-badge/) in the Netlify documentation. [Permalink to Pre-launch toolbar and the Powered by Netlify badge Permalink](/changelog/2026-08-19-pre-launch-toolbar-and-powered-by-netlify-badge/) - [ ## Agent Runners can now ask clarifying questions ](/changelog/2026-08-19-agent-runners-clarifying-questions/) August 19, 2026 - [agent runners](/changelog/tag/agent-runners/) - [ai](/changelog/tag/ai/) - [workflow](/changelog/tag/workflow/) Agent Runners can now ask you clarifying questions before they start building. When a few details could significantly improve the result, the agent pauses and asks instead of guessing. ![The clarifying questions UI in an Agent Runners session, asking: What should the tracker dashboard keep track of?](/images/changelog/agent-runners-clarifying-questions.png) ## How clarifying questions work Say you start with something broad, like “Build a tracker dashboard.” Previously the agent had to make every call for you: what the dashboard should track, whether entries should be editable and saved to a database or live in the code as a read-only placeholder, whether the look should be dark and high-contrast or light, clean, and editorial. Now it can ask, and you can answer directly where the agent run works. ## Answer, skip, or add your own context Answering questions is always optional so you can answer the ones you have opinions about and skip the rest. Or you can skip all questions and let the agent decide. Finally, you can always add context in your own words alongside your answers. In our testing, even a few quick answers make the first build noticeably sharper and saves credits you’d otherwise spend on course corrections. Once you answer, the run continues as usual: the agent writes the code, works with Netlify’s platform features, and creates a Deploy Preview you can review and iterate on. ## Learn more Clarifying questions work with every agent and model available in Agent Runners. Try it out and see [how to use Agent Runners](https://docs.netlify.com/build/build-with-ai/agent-runners/make-changes-with-agent-runners/) in our docs. [Permalink to Agent Runners can now ask clarifying questions Permalink](/changelog/2026-08-19-agent-runners-clarifying-questions/) - [ ## Manage your team invitations from your Netlify dashboard ](/changelog/2026-08-12-accept-team-invites-in-app/) August 12, 2026 - [workflow](/changelog/tag/workflow/) Invitations to join an existing team now show up within your Netlify dashboard, where you can accept or decline them directly without checking your email inbox. Previously, the invitation email was the only way in. If it got buried, filtered, or sent to an address you no longer check, then getting collaboration started with your teammate took a lot longer than it needed to. Now, when you sign in to Netlify with an email address that has a pending invitation, you’ll see it waiting for you. Accept it and you’re on the team immediately. Decline it and it’s cleared out. Either way, you never have to go digging through your inbox. Nothing changes about how invitations are sent. Invitees still receive the same email they always have, and accepting from that link works exactly as before. This is simply a second, more reliable path to the same place. Learn more about inviting and managing teammates in [Manage team members](https://docs.netlify.com/manage/accounts-and-billing/team-management/manage-team-members/) in the Netlify documentation. [Permalink to Manage your team invitations from your Netlify dashboard Permalink](/changelog/2026-08-12-accept-team-invites-in-app/) - [ ## Pay for Netlify with Apple Pay and Google Pay ](/changelog/2026-08-12-apple-pay-google-pay/) August 12, 2026 - [workflow](/changelog/tag/workflow/) You can now pay for Netlify with Apple Pay or Google Pay, in addition to paying by credit card. Both options show up as you’d expect at checkout, so you can confirm a payment with the device you already have in hand instead of tracking down a card. It’s a small change, but it removes a genuine bit of friction—especially when you’re upgrading in the middle of shipping something and don’t want to break flow to go find your wallet. Credit cards continue to work exactly as they always have. If that’s what your team uses, there’s nothing to change and nothing to migrate. Apple Pay and Google Pay are simply two more ways to pay. Learn more in the [Netlify billing documentation](https://docs.netlify.com/manage/accounts-and-billing/billing/overview/). [Permalink to Pay for Netlify with Apple Pay and Google Pay Permalink](/changelog/2026-08-12-apple-pay-google-pay/) - [ ## Ask mode for Agent Runners ](/changelog/2026-07-30-agent-runners-ask-mode/) July 30, 2026 - [agent runners](/changelog/tag/agent-runners/) - [ai](/changelog/tag/ai/) - [workflow](/changelog/tag/workflow/) Netlify Agent Runners now have a mode selector. Pick **Ask** and the agent reads, investigates, and answers questions about your project. **Build** is still the default and works exactly as before. Ask mode is strictly read-only. The agent can’t edit files, run commands, deploy, or change settings. With no build or Deploy Preview, Ask runs are often faster and use fewer credits. It answers with real context: your repository, your project context, and your project’s Netlify Database. Your data is often the fastest way to answer a question about your app, and Ask mode can query it with no risk of a write. A few prompts to steal: - “How many users are in the database?” - “Walk me through how authentication is implemented in this project. Which files handle it, and where is the token stored?” - “Our Largest Contentful Paint is bad on mobile. Read the code and tell me what’s most likely responsible.” - “Plan out how we can migrate to the latest version of Astro.” Because it’s a mode on the same run, you can switch to Build the moment an answer turns into a task — same run, same context, no re-explaining. Ask mode is available on all agents, Claude Code, Google Gemini, and OpenAI Codex, in Agent Runners today. See the docs on [Ask and Build modes](https://docs.netlify.com/build/build-with-ai/agent-runners/make-changes-with-agent-runners/#ask-mode). [Permalink to Ask mode for Agent Runners Permalink](/changelog/2026-07-30-agent-runners-ask-mode/) - [ ## Keep projects private by default with project visibility ](/changelog/2026-07-28-start-with-private-project-urls/) July 28, 2026 - [workflow](/changelog/tag/workflow/) Teams on a [Free, Personal, or Pro plan](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/) now have project visibility settings to ensure that all of your project stay private until you decide to make them public. More people are shipping prototypes, internal tools, early client work, and projects built with agents. A deploy is often a work in progress, not a publication. Netlify now reflects that distinction. Project visibility settings allow you to: - quickly ensure your project stays internal for your Netlify team until you’re ready to launch more publicly. - ensure that your project stays private for you and your Netlify team. - choose defaults that keep internal-only projects private, such as for internal apps and tools or sensitive releases. While project access affects who on your team can access a project from the Netlify dashboard, project visibility impacts who can view your project, both at the live URL and inside of Netlify, and requires Netlify login credentials if a project is set to private. ## Starting defaults Starting today, all new Netlify teams on a [Free, Personal, or Pro plan](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/) will have their projects set to private by default. This means that new Netlify teams will need to adjust the project visibility of each new site or app to decide when to make them publicly available. If you have an existing [Free, Personal, or Pro plan](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/) (all credit-based plans), then your starting project visibility settings are set differently to keep the previous default behavior before project visibility settings launched. This means all your project URLs stay publicly available unless you’ve set up other authentication with code or Netlify’s password protection options. ## Change your project visibility To change your project’s visibility, you can set a team default for all new and existing projects at: [Team settings > General > Visitor access > Default project visibility](https://app.netlify.com/teams/~/settings/general#default-project-visibility) To change only one project’s visibility settings: [Project configuration > General > Visitor access > Project visibility](https://app.netlify.com/projects/~/configuration/general/#project-visibility) ## Availability Project visibility settings are only available for Credit-based [Free, Personal, or Pro plans](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/). If you have a Legacy pricing plan, an Enterprise plan, an Open Source plan, you will not find project visibility settings. In this case though, you can still use [password protection](https://docs.netlify.com/manage/security/secure-access-to-sites/password-protection/), [Team login protection (for Enterprise only)](https://docs.netlify.com/manage/security/secure-access-to-sites/password-protection/#protect-your-sites-with-netlify-team-login) or configure [authentication with code](https://docs.netlify.com/manage/security/secure-access-to-sites/overview/#require-password-or-login-credentials). ## Learn more Learn more about [setting up and managing project visibility](https://docs.netlify.com/manage/security/secure-access-to-sites/project-visibility/) in our docs. [Permalink to Keep projects private by default with project visibility Permalink](/changelog/2026-07-28-start-with-private-project-urls/) - [ ## Netlify Drop updates ](/changelog/2026-07-27-netlify-drop-refresh/) July 27, 2026 - [workflow](/changelog/tag/workflow/) [Netlify Drop](https://app.netlify.com/drop) has a refreshed look, with even more support for your questions and guidance on what’s next after you drop your latest site or app. We first launched Netlify Drop 13 years ago when we introduced the web to a simpler way to deploy your web project and get a custom link for it. Since that time we’ve learned a lot about how people (and now agents) use Drop. You can learn more from our [official blog post revisiting Netlify Drop](https://www.netlify.com/blog/thirteen-years-of-netlify-drop/) and how it’s evolved over time. ## Same core functionality with more context The newly improved Drop page keeps the same core functionality, letting you drag and drop your project files or folder, while making it easier for you or an agent to find answers along the way. For example, did you know Netlify can detect your framework and run a build step for you? You don’t have to build your project first. If you drop a project folder that uses a framework requiring a build, we’ll direct you to log in first, then take care of the build step for you. ## Try it out Try it out at [app.netlify.com/drop](https://app.netlify.com/drop). ## After you drop After you drop a project, claim it to keep your project online and join millions of others, from solo builders to global brands, who manage their sites and apps on Netlify. After you claim your project, you can keep building in your preferred workflow. We’ve got you covered with more ways than ever to keep building and deploying: - [Keep dropping](https://docs.netlify.com/build/build-with-ai/agent-runners/make-changes-with-agent-runners/) to update the same production URL - [Push your deployed project to a newly created GitHub repo](https://docs.netlify.com/build/git-workflows/create-a-repo-from-netlify/) - Keep deploying with dev tools, such as our [CLI](https://docs.netlify.com/api-and-cli-guides/cli-guides/get-started-with-cli/) or [API](https://docs.netlify.com/api-and-cli-guides/api-guides/get-started-with-api/) - [Keep developing with popular AI agents](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/) directly from your Netlify dashboard using Agent Runners From there you can keep launching with confidence, [undo mistakes (even without Git)](https://docs.netlify.com/deploy/manage-deploys/manage-deploys-overview/#rollbacks), build with a team, and grow to any size, all starting from a drop. [Permalink to Netlify Drop updates Permalink](/changelog/2026-07-27-netlify-drop-refresh/) - [ ## Invite Developers and Internal Builders without assigning a project ](/changelog/2026-07-20-invite-builders-without-project-access/) July 20, 2026 - [workflow](/changelog/tag/workflow/) You can now invite a [Developer](https://docs.netlify.com/manage/accounts-and-billing/team-management/roles-and-permissions/#developer) or [Internal Builder](https://docs.netlify.com/manage/accounts-and-billing/team-management/roles-and-permissions/#internal-builder) to your team without assigning them to an existing project. Previously, the UI required every new Developer or Internal Builder to be given access to at least one existing project before you could add them. That got in the way of a common workflow: bringing someone on specifically to spin up new work, without handing them the keys to projects they don’t need to touch. Because both roles can create their own projects directly, this is often exactly what teams want. Invite a new teammate, let them start building right away, and keep your existing projects untouched. When they create a project, they’re automatically assigned the Developer role on it, so they own the work they start without gaining access to everything else. The result is cleaner, least-privilege onboarding: people get exactly the access they need to begin, and nothing more. To try it, head to your team’s Members page and invite a Developer or Internal Builder without selecting any existing projects. Learn more about managing project access in our [project access docs](https://docs.netlify.com/manage/accounts-and-billing/team-management/manage-project-access). [Permalink to Invite Developers and Internal Builders without assigning a project Permalink](/changelog/2026-07-20-invite-builders-without-project-access/) [Next page](/changelog/tag/workflow/page/2)