Changelog

What shipped, by day, written for people who run workflows, build them, or sell them. Days with nothing worth showing are left out.

Jump by month: October 2026 · September 2026 · August 2026 · July 2026 · June 2026 · May 2026 · April 2026 · March 2026 · February 2026 · January 2026 · December 2025 · November 2025 · September 2025 · August 2025 · July 2025

October 2026#

October 15, 2026#

• Paid runs always use the model the creator chose. Your first runs of a workflow were quietly switched to a cheaper model, and from the 11th run you could be asked for your own API keys even though you were paying. Both are fixed.
• Plus members can turn on Use my API keys in the run panel. Steps on OpenAI, Anthropic or Google models then run on the keys saved in your API Vault, and their model cost comes off the price, which the panel shows before you run. Steps on models only Edgaze hosts, like DeepSeek and Kimi, stay on Edgaze and stay in the price, and the creator's price still applies.
• If a provider rejects one of your keys, that step stops with a clear message instead of quietly running on Edgaze. Runs on your own keys are paid from your wallet, and your bundle runs are kept for hosted runs.
• AI steps in Workflow Studio no longer have their own API key or Edgaze-hosted switch. Every step is Edgaze-hosted, and your own keys are a single choice for the whole run.
• A run where some steps fail but the rest still produce your results now says "Completed with issues", in amber, and lists the steps that didn't finish. It used to say the run failed.
• You pay only for the compute of the steps that finished on a run that completes with issues, never more than the compute shown before the run, and no creator price. A bundle run is not used up, and a free demo that completes with issues does not use up your demo.
• The email and notification for a run that waited in line say "finished with issues" when some steps didn't finish.
• The API, webhooks and MCP report how a completed run went: outcome is completed, or completed_with_issues when some steps failed.
• A run waiting in line now reads pending in the API and queued in MCP until it starts. It used to say running while it waited.
• Live run pages and API streams stay connected on long runs. A stream hands over to a fresh connection about every 5 minutes without losing anything (the API sends event: reconnect with the last event id), and the run page keeps following a long run instead of giving up after 45 minutes.
• When support refunds a run, a run paid with a bundle goes back to your bundle, a run that used remixed workflows is refunded in full, and a run started with an API key no longer counts against that key's spend limit.
• Analytics events sent without identifying you no longer carry an empty user ID or the location of Edgaze's servers.
• The Privacy Policy names Webshare, the proxy provider used to fetch YouTube transcripts and web pages that block our servers.
• Workflow Studio test runs now use a weekly usage allowance instead of 10 free runs per workflow. It is measured by what each run actually costs, shown as a percentage, resets every Monday at 00:00 UTC and does not roll over. Test runs use the model each step is set to.
• Each test run gets an execution budget from its estimate before it starts, and never takes more than 30% of the week. A run that needs more stops with "Stopped: execution budget reached", keeps what it finished and counts only that.
• Settings has a new Usage section: this week's Workflow Studio usage and when it resets, your Composer usage, and Use wallet funds to keep testing from your wallet once the allowance runs out (compute price only, confirmed once a week).
• Workflow Studio shows a small usage ring next to Run, with this workflow's runs left this week, and asks before a run only when it can't start on the allowance or would be the week's first wallet-paid run.

October 14, 2026#

• Edgaze has a light theme. It follows your device's light or dark setting by default and switches with it, or you can pick Light or Dark yourself.
• Change the theme from the sun and moon button in the site header, the app sidebar, Workflow Studio, the docs and the blog, or choose System, Light or Dark in the footer and in Settings → Appearance.
• Switching themes fades the new one in from where you clicked, and your choice is remembered on this device.
• Checkout, payout setup and the security check match the theme you are using.
• "Connect your accounts" links from MCP and the API now open Connected accounts in settings. They pointed at a page that does not exist.
• The Wait block's example workflows wait as long as they say: 5 minutes, 2 seconds and 1 hour. They were finishing almost at once.
• When an API run needs a connected account, the 409 response lists the accounts to connect in error.details.
• Listing runs through the API no longer returns the inner runs of a workflow used inside another workflow. The other run endpoints already hid them.
• The API, billing, builder and MCP docs were checked against the product and corrected, including the full list of API errors, how cancelling a run works, and what happens to your funds while a run waits in line.
• Run bundles keep working after the creator publishes a new version. Your runs use the version you bought until the bundle runs out, the run panel says so, and you can still pick the newer version and pay for it from your wallet.
• An API key's spend cap now counts the creator's price as well as compute, so a run that would take a key over its cap no longer starts.
• Cookie choices have a new Marketing setting. Google Ads loads only if you allow it, and ad click IDs are kept only with that consent. Because this is a new choice, you will see the cookie banner once more.
• Server-side product analytics are linked to your account only when you have allowed analytics. Otherwise they are sent without anything that identifies you.
• The restricted-account page lists what a restriction covers and how to appeal through support@edgaze.ai.
• The Privacy Policy, Cookie Policy, Terms and the other policies were updated to name every service we use, where data is processed, and how refunds, disputes and waiting runs work.

October 13, 2026#

• On iPhone, the action receipt in the Gateway section fits inside its label again.

October 12, 2026#

• When Edgaze is at full capacity, your run waits in line instead of failing, and starts on its own as soon as there is room. The run page shows your place in line and an estimated wait, and you can close it.
• Signed in, we email you when a run that waited is done. On a demo, leave your email on the waiting screen and we send you the result.
• Plus runs go first in line and have capacity kept for them, and the waiting screen shows they are in the Plus priority line. Every run moves up the longer it waits, so nobody waits forever.
• A run that cannot start in time is released, and you are not charged.
• The API reports a waiting run as pending with its place in line (queue), and MCP shows it too.
• Runs are more reliable during brief outages: a start that could not reach the engine now waits and retries instead of failing.
• Edgaze MCP is listed in the official MCP registry as ai.edgaze/edgaze.
• Agent apps can tell which Edgaze tools only read, like search and inspect, and which one starts a run, so they know when to ask you first.
• The approval screen for agent apps checks who is asking. An app that only claims to be Claude, ChatGPT or Cursor is marked Unverified, and the screen names the site your approval sends access to.
• When an agent connects to MCP with an API key, paid runs respect that key's permissions and spend limit.
• Banned accounts are blocked everywhere, including the API, MCP, publishing, Composer, checkout and reviews.
• Reports unlist a listing only after three different accounts, none of them brand new, have reported it.

October 9, 2026#

• Runs have a new live view. Instead of a step log, you see what the workflow is doing in plain words, like "Writing your launch note", the text as it is written, and a progress bar.
• Results open with a headline that names what is ready, how long it took and what it cost, and one set of controls: Copy or Download, Run again, and a menu with raw data, full screen, Share and Open in Runs. With several outputs, you switch between them at the top.
• Run pages fill the screen while live and when finished, and work at phone width.
• Creators decide what customers see for each step in its settings, under What customers see: edit the activity line, and choose whether a model step shows its writing live.
• A workflow's steps stay with its creator. Buyers starting a run receive only the questions they answer, and runs through the API or MCP show stages instead of the workflow's steps to anyone but the creator.
• In agent apps that support it, an MCP run plays live in the chat, with a link to the run page when the app blocks the view.
• New run shows the same cards as the marketplace, with search that also finds unlisted workflows, and more loads as you scroll. Picking one shows its live price and a link to its product page before you continue.
• The Runs page groups runs under Today, Yesterday, Previous 7 days and Earlier, and shows a charge only when there is one.
• The product page's run card is simpler. Remix, API and a new MCP button sit in one row, and the wallet card appears only when you have funds or runs to spend.
• The MCP sheet asks which assistant you use and shows the exact setup steps for it. Windsurf is now Devin Desktop, and the steps for Cursor, Claude, ChatGPT and the rest match each app's current setup.
• Result images appear whole once loaded instead of painting top to bottom, and a failed run puts its reason in the middle of the screen.
• The version picker only shows when a workflow has more than one version, and version numbers count from the first version.

October 8, 2026#

• Product pages and demos fill in their example inputs again. Some forms showed up empty, and "Generating example inputs" could spin forever. It now always stops.
• Signed-in buyers and creators keep the example inputs when their version of the workflow loads. A field counts as yours only once you type in it.

October 5, 2026#

• Cancelling a run always finishes. A run cancelled just as it was wrapping up could sit on "Cancelling…" indefinitely.
• A run you cancel while it is still starting no longer goes on to run anyway.
• A cancelled run with nothing to show gets its own screen with how many steps finished and Run again. It used to say the workflow ran successfully with no outputs.
• A workflow's steps and prompts can only be read by its creator, and buyers no longer receive the step-by-step detail of their runs. Creators still see their own prompts and workflows in their library.
• Runs move between steps faster, now that the engine that runs them sits in the same region as Edgaze's database.

October 4, 2026#

• Runs start much faster. The first step begins a second or two after you click Run, where paid runs used to take 12 to 17 seconds.
• Results appear the moment they are final. Paid runs used to show as running for about 7 seconds after the last step while billing finished.
• Long runs show their results. A run with a very long log could say "This workflow did not produce any outputs" even though it had finished.
• Runs that finished but were still marked as running are now corrected automatically.
• The compare and use-case pages show each entry as a card, and the page header no longer covers the first logo.

September 2026#

September 29, 2026#

• Listings have reviews. Rate a workflow from 1 to 5 stars once you have run it successfully, or a prompt you bought, and creators can reply in public. Reviews are marked Verified run or Verified purchase, and you can report one.
• Run via API on a product page has a Try it tab. Run the workflow with your API key and see the result without writing code. A paid run first shows your wallet, what is left after the run, and the key's spend limit, and asks you to confirm.
• Comments on listings are now called Questions & discussion.
• When a demo needs a security check, it opens over the page instead of replacing the run panel.
• API keys you give a run are used only while a step runs and are deleted when the run ends. They are no longer saved with the run.

September 26, 2026#

• Public pages on phones no longer get stuck when you scroll past the footer.

September 24, 2026#

• File upload fields take a paste. Press ⌘V or Ctrl+V anywhere on the run form, or tap Paste on a phone. With several upload fields, the file goes to the one you picked or the only empty one, and otherwise you choose.
• Paste text into an upload field and you can attach it as a file. Name it main.py or notes.md so the model knows what it is reading.
• A file question can take several files. Turn on Allow multiple files in the block settings and set a limit of up to 10.
• Image blocks that edit an uploaded photo follow their prompt again. The photo's details were replacing the prompt, so edits came back unchanged or unrelated.
• When Gemini declines to make an image, the error now says why.
• GPT-6 Sol and GPT-6 Luna are in the model catalog. GPT-6 Sol is the new default and costs less than the GPT-5.6 models it replaces, and GPT-6 Luna is the lowest-cost option.
• GPT-5.6 Sol and GPT-5.6 Terra have left the catalog. Workflows that use them now run on GPT-6 Sol automatically, with no edits needed.
• Claude Opus 5.5 replaces Opus 5 at a lower price. Workflows set to Opus 5 or an older Opus move to Opus 5.5 automatically.
• GPT-5.6 Luna has left the catalog too. GPT-6 Luna is newer and cheaper, so workflows that use GPT-5.6 Luna now run on GPT-6 Luna automatically, with no edits needed.
• Very long prompts on GPT-6 models bill at the model's long-context rate. When a prompt passes 272K input tokens, the run's estimate and charge use that rate, so the shown estimate matches the real cost of a long run.

September 23, 2026#

• Signed out, each section of the developer console (workflows, API keys, webhooks, usage) now explains what it is for and offers a Sign in button, instead of sending you to a separate sign-in page.
• Signing in from the developer console or the docs opens a sign-in window, so you stay on the page you were reading.

September 19, 2026#

• Some older purchased workflows that stopped running after an earlier update work again.
• If you bought a workflow without pinning a version, you can run the active version again.
• Demo runs work again.
• Landing illustrations no longer cover the docs link on phones.

September 18, 2026#

• Workflows can act in your connected apps. New blocks for GitHub, Slack, Gmail, Google Drive, Google Docs, Google Calendar, and Google Sheets cover the actions people actually automate, like filing an issue, posting to a channel, or appending to a doc.
• Connect an account once from Connected accounts in settings. Each run asks you to approve exactly what it may do before it starts, the person running picks the repository or channel, and disconnecting takes effect immediately. Creators never see anyone's sign-in.
• If a connection expires mid-run, the run pauses so you can reconnect, then resumes where it left off instead of failing.
• When a connected app rejects something, you see the app's own reason and which step failed.
• Aviato is the first integration that needs no account at all. Edgaze covers it, lookups are part of the run's price, and previewing is free.
• Composer can now build on its own. It drafts and edits a workflow end to end, pauses to ask your approval before a step that writes to a connected app, and picks up the same run when you answer.
• Studio has guided block insertion. Every output port and edge has an insert button that opens a picker filtered to blocks that fit, condition branches are labeled, and clicking the canvas places a block where you clicked.
• Remix is a block. Pick a published workflow from the picker and it drops into your graph as a node with the parent's thumbnail.
• A new Repeat block runs a step a set number of times, with control over how many run at once and whether one failure stops the rest.
• A reload no longer eats unsaved work. Drafts come back after a crash and are protected while saving.
• Test runs in Studio use your real connected accounts. If you have not connected what a step needs, the run pauses so you can connect and resume.
• Runs keep going through deploys and come back from crashes. Cancelling a run now stops it mid-step instead of letting it run to the end.
• Publishing a workflow is all-or-nothing, so a failure cannot leave a half-saved listing. The version you bought keeps running at the price you paid.
• Webhooks retry a failed delivery for up to about nine hours instead of dropping it, a dead endpoint pauses itself instead of being retried forever, and delivery status shows in the developer console.
• GPT-6 Astra is in the model catalog, and Claude models with tight capacity are flagged in the picker.
• Web scrape is harder to beat. A bot-blocked page retries once through a different route, crawl delays are respected, and a page that only renders with JavaScript is no longer mistaken for real content.
• New Gateway page explains how connected apps work, and the homepage has a Gateway section.
• New pages compare Edgaze with Zapier, n8n, Make, Gumloop, and Apify, and walk through setups for agents, the workflow API, MCP, and long-running workflows.
• Navigation was reworked: a four-section menu, a real drawer on phones, and a cleaner footer.
• Released as v1.3.6.

September 16, 2026#

• The privacy policy spells out how Google user data is handled when you connect a Google account.

September 2, 2026#

• Branded Open Graph cards.
• Product demo prefill experience.
• Ranked marketplace search results.
• Public billing and API documentation.

August 2026#

August 30, 2026#

• Durable delay units and seven-day limits.

August 29, 2026#

• Publish documentation platform post.
• Publish durable runs post.
• Publish mobile workflow creation post.
• Publish Workflow Studio rebuild post.
• Publish model resilience post.
• Publish runnable AI demo post.
• Blog reading and navigation experience.

August 28, 2026#

• Quiet mega-menu hover icons and link the whole prefill disclaimer.
• Guest drafts in the first-workflow tutorial.
• Guest drafts in Workflow Studio.
• Keep docs sitelinks crawlable while showing Docs and API.
• Drop the docs home sitelink chip row.
• Signed-in library previews on the hub.
• Preview created and purchased library collections.
• Preview a library item without leaving the hub.
• Highlight purchased library cards from a hash.
• Highlight created library cards from a hash.
• Highlight a library card from its item hash.
• Scroll a library card into view from its hash.
• Let guests build, save locally, and continue after sign-in in Studio.
• Label local drafts on the mobile builder clutter.
• Keep inspector vault and shared secrets behind sign-in.
• Let guests start and continue a local workflow from the launcher.
• Adopt a local guest workflow draft after sign-in.
• Hand compatible authenticated flow runs back for the same idempotency key.
• Ask Composer guests to sign in when a turn requires it.
• Rate-limit guest Composer with fingerprint and hashed IP caps.
• Keep an explicit return-to when opening sign-in.
• Send email confirmation back to the original destination.
• Prefer the tab-local return path after OAuth.

August 25, 2026#

• You can sign in with GitHub from the regular sign-in screen, checkout, onboarding, creator and invite claims, applications, and agent consent. Edgaze also shows which sign-in method you last used on this device.
• Form-based workflows keep their questions on the product page, so buyers see the fields a creator configured before they run.
• A Web scrape field can turn a product or site name such as stripe into the page to read. If you paste several links with notes, it uses the first real URL.
• Creator payouts are now available in Bangladesh.
• Marketplace rows stay full and stable while sections refresh, instead of leaving gaps or moving the wrong listing between rails.
• About, Brand, Help, Pricing, and Docs now share the same clear sitelinks and public navigation, making important pages easier to find from search and around the site.
• The developer console has clearer empty states and quieter controls for API keys, usage, and webhooks.
• Creators can sell before finishing payout setup. If setup is still incomplete 90 days after the first sale, paid listings pause until onboarding is finished; held earnings are not forfeited.
• The Invest page is easier to scan, with more room for the deck and less boxed chrome.

August 24, 2026#

• Edgaze MCP is linked from the footer, and its agent setup control stays readable and copyable on narrow screens.
• Developers can pin the public OpenAPI definition from edgaze-ai/edgaze-openapi. It updates automatically when the API on main changes.

August 23, 2026#

• The pricing page footer spans the full width instead of sitting inside the last section column.
• New and Noteworthy on the marketplace fills a full row instead of leaving one stray card after For You and Featured.
• Creator analytics and conversions use fresh listing metrics instead of stale counts.

August 22, 2026#

• Run-everywhere animations on the homepage keep moving on phones instead of freezing.

August 17, 2026#

• Creators can mark a workflow input as required in Studio. The toggle is off by default.
• Gemini 3.7 Flash and Flash-Lite are in the model picker with prices that match Google.
• Run estimates for Claude Sonnet 5 match Anthropic's current list price.
• Claude Opus 5 is in the model catalog. Workflows that still pointed at Opus 4.8 remap automatically.
• The Azure mark stays secondary in the model inspector so the model name stays easy to read.
• Azure-hosted models show as Hosted on Azure with the Azure mark, not Foundry.

August 16, 2026#

• Creators have one earnings dashboard for available earnings, Stripe balances, weekly bank deposits, recent sales, and performance by workflow.
• If Stripe still needs payout details, the dashboard says what is missing and opens payout setup without sending you away from the page.
• If you have not joined the creator program yet, Earnings starts with that step and opens the dashboard when you are ready.
• Workflow publish failures include a short error ID, so support can trace the exact problem without exposing private details.

August 15, 2026#

• Ask an agent for something ordinary, like an image or a short brief, and search can find the matching marketplace workflow from everyday language. You do not have to know the listing code.
• The price your agent sees in search is the price you are charged. It is not an old snapshot from when the listing was first published.
• When a run returns an image, a video, or a file, the agent gets a link to the hosted run page so you can open the real result. Plain text still comes back in the chat.
• Press and media assets live on /brand. You can download marks, wordmarks, and color tokens. Old /press links redirect there.
• This changelog is now a dated public log, and new days are drafted from what ships on main.

August 14, 2026#

• Your agent can run a marketplace workflow from Cursor, Claude, ChatGPT, Codex, VS Code, Windsurf, OpenCode, and similar apps. It can search the catalog, read the form and the live price, start a demo or a paid run, and bring the result back.
• Connect at https://mcp.edgaze.ai. Sign in on https://www.edgaze.ai. The REST API stays on https://api.edgaze.ai.
• Let the app open sign-in. Do not go looking for a consent page yourself. A bare consent link has no sign-in request, so it will not work.
• Settings now has Connected apps. You can see which agents have access and disconnect one.
• What you sell through an agent is the same published listing people run on the site. There is no second graph and no second price.
• The homepage and MCP docs have a prompt you can paste so an agent can set itself up.
• A zero wallet after install is normal. Top up at Your wallet before a paid run. Start with Your first run.

August 13, 2026#

• Product pages open faster. Coming back does not flash the wrong layout while we check whether you still have a demo.
• Comments and the run box wait until you scroll near them, so the first paint stays on the product. A link from email still opens the comment.
• Public products show up in search and in the sitemap. Private, empty, or noindex listings do not get advertised.
• The homepage headline is readable while the rest of the page finishes loading.

August 12, 2026#

• The listed run price matches what we charge, including rounding. Catalog copy now says when a listed price is an estimate and when the live quote is what you pay.
• Cancelled means cancelled on the product page, in your runs list, and in the API. A cancel is not shown as completed.
• Composer tells you what phase it is in and asks before it edits your workflow. Approvals show up in the chat instead of applying a patch silently.
• Profile and settings open faster from the account menu on a phone. The menu no longer dumps you back to a blank state.

August 11, 2026#

• The homepage shows real outcomes: an image, a chart, a document, a list. It looks like a product demo, not a feature grid.
• The run panel on that block matches the product-page demo. The button goes to the marketplace so you can run a real workflow.

August 10, 2026#

• Marketplace search understands Edgaze codes like @handle/product, so you can jump to a listing from the code on a card or a profile.
• Results line up better with what you typed, including titles, handles, and codes in the same query.

August 9, 2026#

• Share a product with a QR code or by copying the link. Both go to the same public listing.
• Live activity only shows public runs. Private or unpublished work stays off the feed.
• If a web scrape fails, you see the failure. A Success-only graph no longer paints a failed scrape as if it worked.
• There is a first-workflow tutorial with a short video for each step, from the first block to a run you can publish.
• A failed run no longer leaves money sitting on your balance. The hold goes back to your wallet.
• The cookie banner is smaller and waits until the mascot is ready, so it does not cover the first thing you came to do.

August 6, 2026#

• Homepage run limits are easy to see before you start a demo, so you know how many tries you have left.
• A scrape or file error does not use up your demo. Only a real completed demo counts.
• For You shows two full rows of listings on every screen size, instead of a short strip that looked empty.
• Every docs page asks if it helped. The vote is anonymous. We use it to fix pages people bounce off.

August 2, 2026#

• New Web scrape block: paste a URL and get the article. It works on GitHub, Wikipedia, YouTube, Reddit, and similar sites, and it fails in the open when a page cannot be read.
• You can upload PDFs, Word files, and zips. The workflow can read them when the model supports that kind of file.
• The homepage has demos you can actually run, not just screenshots of a builder.
• Failed runs explain what went wrong in plain language, including scrape and document errors.
• Listings that had no price now show one, so you can see the charge before you run.

July 2026#

July 31, 2026#

• You can search docs from the docs header. Results go to the heading, not just the page.
• The status page is clearer when a check is out of date, so you can tell a real incident from a stale canary.
• Retrying an API run keeps the same workflow version you started with. You do not silently jump to a newer publish.
• New builder tutorial: a company-intelligence workflow, from inputs to a finished brief. See Company intelligence.
• API docs cover versions and how to move a purchase to a newer one.

July 30, 2026#

• A paused run stays paused. Refreshing the page or reconnecting the stream does not restart it.
• Webhooks are not sent again if the first delivery fails. That retry rule is now in the API docs, so you can write your receiver against it.

July 29, 2026#

• You can cancel an API run you started, from the run detail or the list, if you have write access.
• Paid prompt text does not show up in marketplace feeds, trending, or homepage cards. You still see the full text on a product you own or bought.
• Two people cannot spend the same prepaid run at the same time. Runs already going count toward your free-run and max-run limits.
• Banned accounts cannot check out. The block is on the payment path, not only on the product page.
• You can only remix a public, published workflow. Drafts and private graphs are not remix sources.
• New guides: free demos, managed execution, and sell everywhere.
• New homepage. The latest blog post is in the nav.

July 26, 2026#

• The API reference is public and matches the live API. The OpenAPI document is served without a key.
• If an input is wrong, create-run tells you which field failed, not only that the request was invalid.
• You can see versions on a workflow you bought and move that purchase to a newer publish.
• An API key can be given workflow:write when you want it to accept those updates. New keys keep that permission off until you turn it on.
• The developer console has the same version and accept-update actions as the API.

July 25, 2026#

• Loops are simpler. A list goes in, a result comes out, and the inside of the loop has its own editor. You no longer wire item and index ports by hand.
• Long prompts open full screen, so you can edit them without the inspector feeling cramped.
• Inside a loop, the block library only offers blocks that belong there.
• Workflow Studio is in the phone menu. Composer has a menu button too, so you can switch without losing the chat.
• Docs for loops match the new editor. See Workflow Studio.

July 23, 2026#

• Older purchases that were bought once still work. In your library they show as Legacy, so you can tell them apart from per-run products.

July 22, 2026#

• The API checks required inputs before it charges you. A missing field fails cheaply.
• Chat blocks no longer send a temperature you never chose. If you leave it alone, the model uses its default.
• A bad connection between blocks is caught while you build, with the error pointed at the loop editor when that is where it lives.
• A rule you wrote stays a rule. It does not turn into an AI block on its own.
• Loop cards show when a loop will cost more, because each item is another run of the inside. The graph stays on screen on a phone.

July 21, 2026#

• Composer builds one path from Input to Output and will not ship a workflow with dead ends.
• Status is a short line in the chat. You open a diff when you want to see what changed.
• On a phone, you start in Composer. The full graph is still there if you need it.
• Kimi and DeepSeek keep their logos in the model picker. You can search for them by name.
• Closing the side panel clears the selection. Lines between blocks are easier to see on a dark canvas.
• Composer usage and Plus are in one place, so the monthly cap and the upgrade are not on two different screens.

July 20, 2026#

• API links on the site go to https://api.edgaze.ai. Docs examples use that host.
• Run via API on a product page is ready to copy, including the workflow id and a create-run body.
• If Composer names a block that is not on the canvas, it recovers instead of breaking the draft.
• Marketplace images no longer leave a blank hole while they load.
• Released as v1.3.0.

July 19, 2026#

• Docs is split into three paths: run a workflow, create and sell, or build with the API. Start at Docs.
• Checking a run, watching it live, and getting a webhook all use the same statuses. If a stream drops, you can pick it up again from the last event.
• A listing says whose keys it uses: Edgaze-hosted, the creator's connected key, or a key you provide.
• Billing docs cover the price you see, what the creator earns, failed runs, run packs, and older purchases. Start at What you pay for.
• New products start in Composer. Prompt products people already bought still work.
• The run button waits until your files have finished uploading, so you do not start a run on a half-sent PDF.

July 18, 2026#

• Model names, prices, and backups come from one catalog. Old model names still work on workflows that already use them.
• You do not paste a key for models Edgaze already hosts. Hosted rates are on the model catalog.
• The model picker shows logos and a short note when you hover, including when a backup will take over.
• Photos shrink on your phone before they upload, and the size limit is written next to the picker.
• Created and Purchased in your library need you to be signed in. Those routes are not public lists.

July 17, 2026#

• Your library is two lists: things you made and things you bought. The old mixed index is a hub that sends you to one of those.
• After you buy, you land on what you bought, not on a generic library dump.
• Cards use a 16:9 thumbnail and a price that matches the listing.

July 16, 2026#

• Password reset and confirm links work in any browser, including the one you did not start the request from.
• YouTube transcripts break less often when a video page changes shape.
• Your runs page is a history you can search. Opening another run does not start a second live stream.
• You see one price at charge time. We do not show the creator split on the receipt.
• Remix starts with a short explanation of what you are copying and what you will set yourself.

July 15, 2026#

• Text is easier to read on dark screens, including marketplace cards and the builder canvas.
• Listing cards no longer get cut off on a phone.
• Sign-up fits the screen and starts with the form, so you are not scrolling past a hero to type an email.
• A paid run on the product page waits until you actually have access. You cannot start a charge from a stale "you already own this" state.
• Run again asks you to confirm, so a second charge is intentional.

July 14, 2026#

• Double-tap a listing card to like it. You do not have to hit a small heart.
• If something is down, a banner can say so across the site, including the marketplace and the builder.

July 13, 2026#

• You can ask for a missing block from the library, so a gap in the palette is a request, not a dead end.
• The homepage carousel uses real marketplace workflows, not placeholder cards.
• New homepage, and a clearer creators page that includes how earnings work.

July 12, 2026#

• The developer console is workflows, keys, webhooks, and usage. Each screen asks you to sign in.
• /developer is the public page. The console waits until you have an account, so a shared link does not open someone else's keys.

July 11, 2026#

• Composer shows how much you have used this month. Plus updates as soon as you pay, without a refresh loop.
• Pack prices are easier to read. A top-up cannot be counted twice if you retry the same payment.
• Version history in the builder is more reliable when you publish twice in a row.
• Publish and checkout handle Plus and run packs in the same flow, so you are not sent to a second page to finish paying.

July 10, 2026#

• Plus limits how many runs you can have going at once. Pricing and wallet show the upgrade next to that limit.
• Wallet history uses workflow names, not only run ids.
• You can start a run from your runs list and share that run with a link.
• Form values fill into chat blocks, so a product-page field becomes the prompt the model sees.
• If a run fails, the money held for it goes back to your wallet. You do not file a ticket to unstick a hold.

July 9, 2026#

• The public API is at api.edgaze.ai. Keys, runs, and webhooks use that host.
• You cannot remix an older kind of purchase. Remix is for published per-run workflows.
• Publish is a short flow: price, backup model, preview, then sell.
• Profiles show remix counts and the founding badge, without extra chrome around them.

July 8, 2026#

• The API can list workflows. The developer console can too, with the same catalog fields.
• Creator earnings show on listings as the creator's cut, not as a token bill.
• The API reference is in docs, next to create-run and webhooks.

July 7, 2026#

• Docs starts with running something, then selling it. Billing pages have next and previous, so you can walk what you pay for without going back to the index.

July 6, 2026#

• A workflow inside another workflow connects in the builder and still connects when it runs. Nested inputs map through instead of dying at the inner Input block.
• A run that has already started keeps going through a deploy. You do not lose a live job because we shipped in the middle of it.

July 5, 2026#

• New listings charge per run. You see one price. Failed runs are free. The creator earns 80% of their margin. Hosted compute is not part of that cut.
• Creators set their cut at publish. Buyers do not see a token bill or a compute invoice.
• Inputs that are too large are stopped before anyone is charged.
• You can buy a pack of runs. The pack is used first, then your wallet.
• At checkout you can top up, buy a pack, or run now if you have enough.
• A remixed workflow has its own price. You cannot point two workflows at each other in a loop.
• If we have to use a more expensive model, your price stays the same. Creators can turn that backup off so the run fails instead.
• Plus with your own key: you pay a small orchestration fee plus the creator's cut. Your provider bill is yours.
• You run the version you bought, at that version's price, even if the creator published a more expensive one later.
• Run packs expire after two years. Refunds have a support path.
• Older purchases still work for the people who already bought them.

July 4, 2026#

• Blocks show a hint of their settings on the card, so you can scan a graph without opening every inspector.
• Marketplace images stay sharp without being huge files.
• Creators earn on their cut. Hosted compute is not creator income, and it is not shown as if it were.

July 3, 2026#

• The pricing page matches wallet billing and Plus, including the own-key path. What you read there is what checkout charges.

July 2, 2026#

• Public API: start and read runs, find workflows, create keys with spend limits, and get a signed ping when a run finishes.
• If you already have access, the product page has Run via API with a copy-ready request.
• Workflow Studio home and the marketplace live feed were redesigned so the first action is obvious.
• Comment links from email open the right thread, including on a listing that paginates comments.
• Form fields on a run stay in a stable order, so a saved share link fills the same boxes.
• A real failure is not retried as if the model just hiccuped. You see the error instead of a second charge.

July 1, 2026#

• Workflow Studio has a new home, templates, block library, and settings. You can start from a template or a blank graph.
• Remix is more reliable when the parent workflow has nested blocks.
• Live activity is more accurate about what actually finished, not what was still queued.

June 2026#

June 30, 2026#

• The runs list shows when something actually finished, including the time, not only that it left "running."
• Template search suggests as you type, so you can find a starter graph without scrolling the whole library.

June 29, 2026#

• Wallet page: balance, history, and top-up in one place. See Your wallet.
• A purchase locks the version you bought. Each publish is a new version you can name.
• If a newer version exists, you see a banner and can switch. Switching is explicit.
• Plus includes checkout, a billing portal, and your own keys.
• You can share a run at /run/{id}. The page shows the result without opening the builder.
• You can remix a published workflow in Studio and set your own price on the new listing.

June 28, 2026#

• The live run focuses on the block that is working. The log works on a phone, including scroll and wrap.
• Product page, builder, and API all start a run the same way, and they check access first. A missing purchase fails before the model is called.

June 27, 2026#

• A card payment shows up in your wallet as soon as Stripe confirms it.
• Creator payouts wait until bank setup is done. You can keep selling. You cannot cash out on an unfinished Connect account.
• The price we showed you is the price we charge, even if a provider's cost jumps during the run.

June 26, 2026#

• Settings is easier on a phone, including sign out, so you are not hunting for a desktop-only control.
• The pitch deck opens again.
• Cookie preferences in the footer are simpler. You can change analytics without re-reading the whole banner.

June 25, 2026#

• Demos, including image demos, fail less often when a model or a file host is slow.
• You can try Composer without an account. When the free tries run out, we ask you to sign in instead of failing the chat.

June 24, 2026#

• Set it yourself clears the filled-in demo inputs, so you can replace a suggestion without deleting field by field.
• A finished demo stays on the page. It does not disappear behind "demo used."
• Cookie banner and preferences. Analytics waits until you say yes.

June 19, 2026#

• The product page appears right away. Fields fill in one by one if we have a suggestion, instead of blocking the whole form on the first hint.

June 18, 2026#

• Demo inputs can be filled in for you from the listing's sample.
• The bot check stays hidden unless something looks off, so most people never see a challenge.
• Signed-in demos on paid workflows start without an error when you still have a demo left.
• Image results show as images, not as a raw URL you have to open.

June 17, 2026#

• After a demo is used, you see the gallery and Buy Access. The page does not look like you can run another free try.
• On a phone, the sticky button is Buy Access, not another demo.

June 16, 2026#

• The run box is on the left. The thumbnail sits under the creator, so the first thing you read is what the product does.
• Buy Access is the main button on a paid listing.

June 15, 2026#

• You can run a demo on the product page. No extra window, and no jump into the builder.
• You can look at a finished demo again, including the output you already generated.
• The marketplace is quicker on a phone, including cards and the live feed.

June 11, 2026#

• Hosted runs keep their images and files after the run ends, so a refresh does not lose the result.
• If Anthropic or Gemini is down, the run can finish on a backup when the listing allows it.
• Trying a run in the builder while signed in is a real run, not a guest demo. It uses your wallet or pack when the workflow is paid.
• Each signed-in account has a demo limit. It is per account, not per browser.

June 10, 2026#

• Hosted runs fail less often when a model stalls or a file host is slow. You see a real error if it still cannot finish.

June 9, 2026#

• If Anthropic is down, the run can continue on OpenAI. Image blocks get the same backup.
• YouTube transcripts fail less often when a video has captions in a format we already support.

June 5, 2026#

• Back from a listing remembers where you were in the marketplace, including on a phone and including the category you were in.
• A comment link from email opens the thread on that listing.

June 3, 2026#

• New creator onboarding, including Composer, from a first draft to something you can publish.
• The marketplace is better on a phone, including live activity that does not jump the layout.
• Released as v1.2.6.

June 2, 2026#

• Edgaze codes are easier to find on cards and profiles. Live activity is quieter, so a busy hour does not take over the page.
• You can set notification preferences, including what email you get after a run or a comment.
• How it works asks you to sign in when you need an account, instead of showing a dead action.

May 2026#

May 29, 2026#

• The blog is live. Posts about Composer, the first workflow, and why workflows beat prompts start there.

May 28, 2026#

• Composer is steadier when it edits your workflow. A long chat is less likely to apply a half-finished change.

May 26, 2026#

• Product pages are back, with a calmer comments section that does not sit on top of the run box.
• Composer slows down if you send too much at once, instead of dropping the draft.
• Hints and the run window are less noisy. Status text is shorter. The window does not steal focus while you type.

May 25, 2026#

• Photos on listings, Composer chats, and saved API keys fail less often. A retry does not create a second key.

May 23, 2026#

• You can draft a workflow in chat with Composer. Describe the outcome, and it builds a graph you can open in Studio.

May 17, 2026#

• Listings have better photos, likes, and a simpler menu. The product page is thinner, so the run and the gallery are the first things you see.

May 13, 2026#

• Legal and trust pages were refreshed, including terms, privacy, and the pages that say what a run is allowed to do.
• Careers date pickers work on a phone, so an application does not require a desktop calendar.

May 8, 2026#

• You can apply for a role from one form while signed in. Attachments go with the application. You do not email a PDF separately.

April 2026#

April 28, 2026#

• Creator onboarding walks you from a first workflow to publish, including the black sign-in and the first Studio session.

April 26, 2026#

• Preview inputs are checked before a run starts. A missing required field fails on the form, not after the model is called.

April 25, 2026#

• Released as v1.2.5. Featured storefronts can ship new workflows without waiting on a platform release.

April 24, 2026#

• YouTube transcripts work again after a player change on YouTube's side.
• Link previews work when you paste a URL in social apps, including the image and the title.

April 23, 2026#

• gpt-image-2 is available in image blocks. Lowest workflow prices are simpler to set at publish.
• If the main image model times out, a backup can finish the picture when the listing allows it.

April 22, 2026#

• Creators get paid more reliably, including when a transfer has to retry.
• The earnings dashboard stays signed in while you move between balances and payouts.
• Demos are harder to game with a refresh or a second tab. The library scrolls on a phone.
• Run windows sit in the middle of the desktop and stop spinning forever when a run is already done.

April 21, 2026#

• Demos show whether they are available, even while you move between listings. You do not tap Run and then find out the demo is gone.
• Payout setup status matches what Stripe has, including the country and the next step they still need.

April 20, 2026#

• Public pages and publish are cleaner. The publish flow asks for less, in a stable order, and the marketing pages match the product you actually get.

April 19, 2026#

• Template library in Workflow Studio, with docs for how a template becomes a listing.
• Publishing from a phone is easier. The form fits the screen and the preview is the listing card, not a desktop-only canvas.

April 18, 2026#

• A listing that changed owners sends you to the new one. Old links do not 404.
• The phone top bar is back, including search and the account menu.

April 17, 2026#

• You can zoom the canvas. Trackpad and buttons both work.
• Image blocks have aspect ratios, so a 1:1 and a 16:9 output are a setting, not a prompt you hope the model honors.

April 15, 2026#

• Saved API keys work from the run box, including keys you added in settings.
• Listing photos upload when someone is helping you publish, so a co-publisher can finish the gallery.

April 14, 2026#

• Claiming a profile is less likely to collide with someone else on the same handle.
• Following counts can stay private.
• Released as v1.2.4.

April 13, 2026#

• Stripe Connect works in more countries, with a clearer setup and the country asked up front.
• Duplicate payout accounts are combined, so you do not see two balances for the same bank.
• A missing sample output no longer breaks the demo. The run still starts. The gallery just stays empty until there is a result.
• Earnings and Stripe balances stay in sync after a payout or a retry.

April 12, 2026#

• Trending has clearer rules about what can appear and how long it stays there.
• Password reset sends you back to the page you were on, not to a generic home.
• Connect setup asks for your country correctly, including when you change it mid-flow.

April 11, 2026#

• Product pages count views. Public listings are easier to find in search, including title and description.

April 10, 2026#

• Listing pages, sign-in, and link previews are more reliable. A slow image host no longer blanks the whole card.

April 9, 2026#

• What you get on a product page is clearer on a phone: gallery, run, and price, in that order.
• Removed listings leave the public profile. They do not linger as a dead card.

April 8, 2026#

• An old tab can reload the builder or marketplace without a white screen.
• Gemini blocks and downloads fail less often.
• Sign-in errors are in plain language, including a wrong password and a cancelled Google prompt.

April 7, 2026#

• Verified creators. A checked profile is visible on the listing and on the public page.
• Released as v1.2.3.

April 6, 2026#

• Link previews are real images, not broken icons, when you paste an Edgaze URL in chat or social apps.

April 5, 2026#

• Demos and the phone run window behave. A finished demo does not leave the window spinning.
• Link previews use the right image for the listing you shared.

April 4, 2026#

• The software license was revised. The public terms match how runs and listings actually work.
• A busy live run is less likely to freeze when several blocks finish at once.

April 3, 2026#

• Live runs recover more cleanly when a model fails. You get the error on the block that failed, and the rest of the graph does not look like it is still running.

April 2, 2026#

• The run window is faster and more stable. Opening a second run does not stall the first one.

April 1, 2026#

• The run people see is separate from the builder, with live updates. Sharing a run no longer opens Studio.
• New icons across the builder. Gemini is more reliable on long prompts.

March 2026#

March 31, 2026#

• Live runs stream faster. Tokens and images show up as they land, instead of waiting for the whole block.

March 26, 2026#

• Anthropic and Gemini blocks in the builder, next to the models Edgaze already hosted.
• PDFs open correctly in the run output, including multi-page files.
• Released as v1.2.2.

March 25, 2026#

• About page copy and layout are fixed.
• Link previews work again after a metadata miss on product URLs.

March 24, 2026#

• Prices on product pages match the listing. Preview images are the gallery you uploaded, not a leftover builder thumbnail.

March 23, 2026#

• Builder and run fixes from real use: graphs that would not save, runs that would not leave "starting," and a few blocks that ignored their own settings.

March 16, 2026#

• Search engines get a better map of the site, including marketplace and docs.
• Released as v1.2.1.

March 15, 2026#

• Creator program, payments, press, and About are public. You can read how selling works and where the company is.
• Creators build. Buyers run. That split is the product, not a side mode.
• Released as v1.2.0.

March 14, 2026#

• Creators can connect a bank account and get paid through Stripe Connect. Selling can start before payout setup is finished. Cashing out cannot.

March 13, 2026#

• Edgaze Blog starts as a real section, not a placeholder.
• Product pages are clearer about price, demo, and what you get.
• Bank setup continues for people who already started Connect.

March 11, 2026#

• Storefront and builder fixes from the payments work: a listing that could not publish after Connect, and a storefront that showed the wrong owner.

March 5, 2026#

• Trending this week on the marketplace, with a short list of public listings that actually ran.

March 4, 2026#

• Landing, docs, and the rest of the site feel like one product. The same names, the same dark chrome, the same paths into run and build.

March 3, 2026#

• Creator invites. You can join from a link instead of a public form.
• Docs cover Stripe basics: connect a bank, wait for pending earnings, then payout.
• Published workflows keep working after builder changes. A graph you already sold does not break because the editor moved a port.
• The builder is better at showing errors on the block that caused them.

March 1, 2026#

• Stripe Connect, and the first legal pages for payouts. Creators can start onboarding. Buyers still pay Edgaze. The split to the creator waits on a successful run.

February 2026#

February 27, 2026#

• Site copy and legal pages updated ahead of payouts, so terms, seller pages, and the landing page agree on how money moves.

February 26, 2026#

• Edge Platforms, Inc. is a Delaware C-Corporation.
• The product is still Edgaze. The company name is on the legal pages. The site, the marketplace, and the builder do not change name.

February 23, 2026#

• Inspector, block library, and a clearer way to catch workflow errors before you publish.
• Your profile is on the top bar, including handle and the menu into settings.
• Released as v1.1.0.

February 22, 2026#

• Inspector and builder security improvements. A graph you open from a listing cannot run unexpected network calls from the editor itself.

February 20, 2026#

• Welcome email when you sign up.
• Password reset works, including the link back into the app.
• Menus are clearer: marketplace, library, builder, and account are labeled as those things.

February 16, 2026#

• Where a listing allows it, you can try a flow without buying. That is the first public demo on a product page.

February 15, 2026#

• Public beta. Marketplace, builder, accounts, docs, and publishing are open.
• Prompt Studio and Workflow Builder, with @handle/name product pages.
• Browse, search, storefronts, likes, and comments.
• Email or Google sign-in. Custom handles, with a 30-day wait to change them. Founding Creator badge for people who published early.
• This is the second Edgaze. The first one was a student app. The thing that survived is a packaged outcome someone else can run.
• Released as v1.0.0.

February 11, 2026#

• Fixes and docs before the public launch: sign-in loops, broken listing cards, and the first pass of builder docs that match the editor you actually get.

February 10, 2026#

• You can edit your handle. Loading is calmer while the new URL is reserved.

February 4, 2026#

• Builder docs. Security and interface fixes so a shared graph cannot write over someone else's draft.

February 2, 2026#

• Open beta on the marketplace. Preview images, docs, and landing pages updated so the public site matches the builder people were already using.

January 2026#

January 30, 2026#

• The builder is more stable on long graphs. Marketplace browsing is better, including search and category pages.

January 29, 2026#

• Workflow runs have a real screen, not only a toast in the builder.
• Sign-in sends you back to the page you were on.
• The apply form works end to end, including attachments.

January 26, 2026#

• Sign-in, product pages, prompts, and profiles are more reliable. A refresh no longer drops you on a blank profile or a listing without a run button.

January 24, 2026#

• Back works on workflow previews. Product-page sign-in no longer loops you through the same prompt.

January 23, 2026#

• More builder blocks, a preview that works on phones, a better block library, and a working feedback form.

January 16, 2026#

• Workflow comments work on a listing. You can share a prompt product with a public URL.
• The apply form shows phone numbers on Windows, including the country code.

January 6, 2026#

• Prompts and workflows show up in search, including title and handle.
• Landing links work. The site no longer jumps around on a phone when the top bar loads.

December 2025#

December 27, 2025#

• Sign-in, builder, and marketplace became one product. One account, one shell, one set of routes.
• Most of the original student tools are gone. What is left is the path that became workflows: build something, run it, let someone else run it.

November 2025#

November 20, 2025#

• Google sign-in, profiles, and social links. You can create an account, set a handle, and put links on the public page.
• The first profile menu and sidebar that look like the app that shipped in beta, not like a landing-page experiment.

November 18, 2025#

• First commit in this repository. The name is older. This is the day the current codebase starts, not the day the idea starts.

September 2025#

September 22, 2025#

• The student super-app is out. Building every campus tool by hand was the wrong center of gravity.
• The interesting part is the infrastructure under those tools: a visual builder, a way to publish, a way for someone else to run the result, and a way to pay for that run.
• The audience changes from students to anyone who wants to package an AI outcome. Most of the original tools will not last. The idea of a packaged outcome does.

September 15, 2025#

• The first edgaze.ai page goes live. Beta signups open. There is no launch event and no waiting list of people already sold.
• The waitlist starts at zero. That is not a joke in the copy. It is what the counter said.
• That student-tools beta page is still up at edgaze-ai.pages.dev. Visual builder, marketplace, credits, and "Build, share and monetize student tools" are all already on that page, before this repo exists.

August 2025#

August 27, 2025#

• The pitch is "The AI Super-App for Students": one application with the tools a student might need, instead of a pile of chatbots and forums.
• Underneath that pitch, a builder, a marketplace where other people could publish tools, and a credits system for running them start to show up. That is the DNA of today's Edgaze, still wearing a campus costume.

August 25, 2025#

• The first Edgaze is a set of purpose-built student tools, not a workflow platform.
• Scam Checker, AI University Decider, Offer Letter Checker, and AgentDB are on the board. Each one is a specific decision, not a generic chat.
• The idea that survives every later pivot is already here: package AI around an outcome someone can just run.

August 13, 2025#

• A frontend talks to a working backend. Edgaze runs.
• It is primitive next to the product now. It is the first day it is software instead of designs and a name.

August 3, 2025#

• EscapeMyAgent starts feeling too narrow. The problem is not only education agents. Students were making hard calls with bad information: universities, offers, whether something was legitimate, admissions, and a pile of disconnected services.
• The name becomes Edgaze. edgaze.ai is checked and taken as the home.
• This is the closest thing to Edgaze's birthday as a name.

July 2025#

July 27, 2025#

• EscapeMyAgent.com exists. It is not a company. It is a small product for a problem that was annoying enough to build.
• The problem: students dealing with education agents while applying to university, with almost no visibility into their own application, withdrawals, or refunds.
• You can check what an agent is doing, flag a questionable situation, and handle the parts of an application that used to sit with someone else.
• This is the first ancestor of Edgaze. The through-line is the same: someone should get a specific outcome without having to understand all the complexity behind it.