---
title: "Workflow | Netlify Changelog"
description: "Stay updated with the latest features, fixes, and improvements. Realize the speed, agility and performance of a scalable, composable web architecture with Netlify. Explore the composable web platform now!"
source: "https://www.netlify.com/changelog/tag/workflow/page/2/"
last_updated: "2026-08-05T01:47:49.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)

-   [
    
    ## Monitor credit usage by day
    
    ](/changelog/2026-03-24-monitor-credit-usage-by-day/)
    
    March 24, 2026
    
    -   [workflow](/changelog/tag/workflow/)
    
    Users on credit-based plans can now see a day-by-day breakdown of their credit consumption. Head to **Usage & Billing** > **Account usage insights** > **Credits** to view exactly how your credits are being used each day.
    
    Track credit usage across the following [meters](/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/#credits-usage-for-metered-billing):
    
    -   AI Inference
    -   Bandwidth
    -   Compute
    -   Production deploys
    -   Web Requests
    
    ![Day-by-day credit usage breakdown in the Netlify UI](/images/changelog/credit-usage-per-day.png)
    
    This makes it easier to spot usage trends, identify spikes, and plan ahead — so you can stay on top of your credit consumption without any guesswork.
    
    Learn more about [how credits work](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/).
    
    [Permalink to Monitor credit usage by day Permalink](/changelog/2026-03-24-monitor-credit-usage-by-day/)
    
-   [
    
    ## Introducing Prompt Templates
    
    ](/changelog/2026-03-18-prompt-templates/)
    
    March 18, 2026
    
    -   [agent runners](/changelog/tag/agent-runners/)
    -   [workflow](/changelog/tag/workflow/)
    
    To help you and your agents build more effectively, we’re introducing reusable Prompt Templates available directly from within Netlify.
    
    Browse a [curated collection of reusable prompts](https://docs.netlify.com/prompt-templates/browse/) for common Netlify workflows: accessibility audits, A/B testing with Edge Functions, and more. Each template uses variable placeholders so you can adapt it to your project without starting from scratch.
    
    Prompt Templates live directly in your project’s [agent runs dashboard](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). From there you can:
    
    -   **Browse** public prompt templates
    -   **Customize and save** your own versions of any template for your team
    -   **Submit templates** back to the community to share what is working for you
    
    Learn more about [managing Prompt Templates](https://docs.netlify.com/prompt-templates/manage/) for your team.
    
    [Permalink to Introducing Prompt Templates Permalink](/changelog/2026-03-18-prompt-templates/)
    
-   [
    
    ## See your available credits at a glance
    
    ](/changelog/2026-03-11-display-available-credits/)
    
    March 12, 2026
    
    -   [workflow](/changelog/tag/workflow/)
    
    ![Monitor credit usage in the Netlify UI](/images/changelog/monitor-credit-usage.png)
    
    We’ve updated how credits are displayed across the Netlify UI. Instead of showing a “used credits / total credits” counter, you’ll now see your **available credits** — the number of credits you actually have left to use.
    
    Now, you’ll see exactly how many credits remain on your account without needing to do the math yourself. For a detailed breakdown of your monthly credit consumption, check the **Credit usage breakdown** card on your team’s billing page.
    
    Learn more about [how credits work](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/).
    
    [Permalink to See your available credits at a glance Permalink](/changelog/2026-03-11-display-available-credits/)
    
-   [
    
    ## Use Netlify Agent Runners from Linear
    
    ](/changelog/2026-02-27-agent-runners-linear-integration/)
    
    February 27, 2026
    
    -   [agent runners](/changelog/tag/agent-runners/)
    -   [workflow](/changelog/tag/workflow/)
    
    Linear users can now launch Netlify Agent Runners directly from any Linear issue, allowing you to seamlessly share context with your AI agent of choice. If you have your Linear issue synced with related Slack messages, this context will also be included in your agent run prompt.
    
    Before starting your agent run, you can review and edit your prompt. Next, you can choose which AI agent to use — Claude Code, Google Gemini, or OpenAI Codex. Netlify Agent Runners doesn’t lock you into using a single AI agent so you can pick the agent that fits the task best.
    
    To start an agent run from Linear:
    
    1.  Go to a Linear issue where you want to trigger an agent run.
    2.  In the top right corner, select **Configure coding tools…**. ![Linear issue view showing the Configure coding tools option in the top right corner](/images/changelog/linear-configure-coding-tools.png)
    3.  Toggle **Netlify Agent Runners** on.
    4.  Go back to the issue and in the top right corner, select **Open in Netlify Agent Runners**. ![Linear issue view showing the Open in Netlify Agent Runners option in the top right corner](/images/changelog/linear-open-in-netlify-agent-runners.png)
    5.  Review the prompt and choose your AI agent.
    6.  To start the agent run, select **Run task**.
    
    Once you’ve enabled this integration from your personal Linear preference settings, any Linear issue you open in your workspace will give you the option to open with Netlify Agent Runners.
    
    Now your entire team can save time and seamlessly share context between Linear and Netlify Agent Runners while keeping this work clearly tracked across Linear and Netlify. Learn more about [Agent Runners](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/).
    
    [Permalink to Use Netlify Agent Runners from Linear Permalink](/changelog/2026-02-27-agent-runners-linear-integration/)
    
-   [
    
    ## Apply specific environment variable values to all branches with a prefix
    
    ](/changelog/apply-specific-environment-variables-to-all-branches-with-a-prefix/)
    
    March 6, 2025
    
    -   [workflow](/changelog/tag/workflow/)
    -   [build](/changelog/tag/build/)
    
    ![](https://cdn.sanity.io/images/o0o2tn5x/marketing/8ce5ea01d52303bec8072d4ed7a448508c615b76-914x418.png)
    
    We now support configuring your environment variables to apply a value to groups of branches with a given prefix. Explore the new functionality in Site configuration > Environment variables. When adding a branch value for your environment variable, add a wildcard at the end to apply the value to all branches beginning with the prefix. For example setting the branch name to `release/*` will apply the supplied value to branches named `release/1.2`, `release/alpha-0.0.1`, and so on.
    
    Combine with the ability to [configure your site to deploy branches matching selected prefixes](https://docs.netlify.com/site-deploys/overview/#branch-deploy-controls) to super-charge your branch workflows!
    
    [Permalink to Apply specific environment variable values to all branches with a prefix Permalink](/changelog/apply-specific-environment-variables-to-all-branches-with-a-prefix/)
    
-   [
    
    ## Set up deploys for all branches with a prefix
    
    ](/changelog/set-up-deploys-for-all-branches-with-a-prefix/)
    
    February 18, 2025
    
    -   [build](/changelog/tag/build/)
    -   [workflow](/changelog/tag/workflow/)
    
    ![Netlify UI settings to deploy all branches with the prefix release](https://cdn.sanity.io/images/o0o2tn5x/marketing/1db6ae1900bb72def6e9413dc6d8a4689a17d990-1209x860.png)
    
    We now support configuring your site to deploy all branches with a specific prefix. Leverage the new functionality by configuring Branch Deploys in Site Configuration > Continuous deployment. Add a wildcard at the end of your prefix to deploy all branches beginning with the given text - for example, enter `release/*` to automatically deploy `release/alpha-1`, `release/v2`, and so on.
    
    [Permalink to Set up deploys for all branches with a prefix Permalink](/changelog/set-up-deploys-for-all-branches-with-a-prefix/)
    

[Previous page](/changelog)