Picking an ad format on a synced machine now sets it for your account, so your other machines follow the choice you made where you made it, instead of only following the dashboard. The terminal status line works the same way, so turning it on where you are sitting is no longer undone a few minutes later. Your dashboard updates live as a machine reports in, with no refresh, and a format that arrives from sync is applied quietly rather than interrupting you about a change you made somewhere else.
The sponsored line works again on the newest Claude Code
A recent Claude Code update moved the part of the file Awaitful attaches to, which paused the thinking line and the chat banner until you turned your format on again. Awaitful reads the current shape of the file now, so the format you picked keeps working across a Claude Code update.
Restoring is how you put Claude Code back exactly as it was, and on a synced machine your account could ask for the format back within minutes of you removing it. A restore now settles that request rather than being undone by it, and nothing is re-applied without asking you first. It is the one action to take when something looks wrong, so it has to hold.
A choice you make sticks, even if the network does not
When you pick a format, that choice is now kept until your account has actually accepted it, instead of being dropped by a dropped request and quietly replaced by your older setting on the next check. A format is also only shared with your other machines once it has really worked on the one you picked it from, so a change you cancelled or that failed part way no longer travels.
Extension0.7.6
The panel stops taking your tab
The Awaitful panel could pull itself to the front while you were reading something else, most noticeably while your agent was thinking. It stays where you left it now and only comes forward when you ask for it.
Extension0.7.5
A guided setup checklist
When you sign in, the panel now walks you through three steps: sign in, turn on your best-earning ad format, and sync your settings across your devices. It clears itself once you finish or dismiss it, and everything stays changeable afterwards, so the checklist gets you started without locking anything in.
The switch once called "Control from web" is now "Sync across devices". Pick the ad format you want on one device or from your dashboard and Awaitful applies it to your other devices for you. Turning it on still asks you on each machine before it changes a file there, because only the machine can allow that.
Signing out and back in used to add a new entry to your connected machines every time. Awaitful now recognizes the same machine across sign-ins and keeps the name you gave it, so your device list stays clean. It does this with an id your machine already made up for itself, so nothing new leaves your computer to make it work.
After an update, the panel shows a short note once about what changed, with a link to the full changelog, then gets out of your way. It appears the first time you open the panel on the new version and does not come back, so it never nags.
Extension0.7.4
Every spot keeps its own look
The spinner, the advertiser logo and the chat banner glow used to be one set of choices applied everywhere at once. They now belong to the format that draws them, set on that format's own page, so a quiet thinking line can run alongside a livelier chat banner. Your existing choices carry over, and each format offers only what it can actually draw: the status bar and terminal are text, so they have no logo to show.
The terminal status line runs alongside whichever editor format you picked, in every terminal you open, and you can now ask for it from the dashboard rather than only from the extension panel. Asking never switches it on by itself: it changes a file on your machine, so your editor prompts you to confirm it there. The dashboard shows when your device has actually applied it, not merely that you asked.
A sponsored line now counts from the moment it is actually drawn on screen, not from the moment Awaitful decides to show one, and the same line open in two editors counts once rather than twice. A patched file is no longer taken as proof that a spot is working: if nothing confirms a line reached the screen across several thinking turns, earning moves back to your status bar and the panel says why. On a machine with no Claude Code, Awaitful says what is missing instead of showing an empty status bar, and writes nothing into a config folder for a product that is not installed.
Other tools change the same Claude Code files Awaitful does, and removing one does not undo what it already wrote, so its sponsored line can keep appearing until the file is put back. The panel names the tool where it can, finds it even when it is installed in a different editor on the same machine, and walks you through a clean copy one step at a time, each step ticking only once it has really happened. Awaitful never edits another extension's code and never removes or disables one by itself: the buttons are there, but the click is yours.
See engagement by surface, and how close you are to budget
Each campaign can now expand into an engagement panel: impressions, clicks, and click-through rate broken down by surface, busiest one first. A spend meter shows how much of your total budget is used once you have set a cap, and an honest note when you have not.
Developers with an Indian bank account can now withdraw directly, through Wise instead of Stripe. Connecting takes three steps in Awaitful's own form: a one-time tax form, your bank or UPI details, and a review before anything is sent. The transfer fee is shown before you confirm, and converts at Wise's mid-market rate.
See where your money went, and change where it lands
Your Payouts page now keeps a full withdrawal history, each entry showing the account it went to, so you can always see where your money has gone. You can change your payout account any time, to a different bank for example, unless a withdrawal is already on the way. And if a payout cannot be completed, it returns to your balance so you can try again.
Extension0.7.3
Pick where you earn, and see the rate
The panel now shows each spot's earning rate as a plain multiplier, so it is clear at a glance that the thinking line and chat banner earn more than the status bar, while the terminal stacks on top of whichever one you pick. And when another extension has already changed Claude Code, getting back to a clean copy is now guided one click at a time, rather than a list of steps to follow by hand.
Locked out? A link on the sign-in page now emails you a reset link, and opening it lets you choose a new password; the link expires in an hour. The account forms that send email are also quietly shielded from automated bots.
Dashboard
Notifications, in the app and by email
The dashboard now keeps a running feed of what matters, with a bell in the sidebar for anything unread: a review decision on a campaign, a payout that settled, a new device linked to your account, a change to your password, a wallet running low. Every notice has its own switch per channel. In-app is always there; email goes out only for the ones worth an inbox, and the security alerts stay on. Only mail someone asked for is ever sent, and a single spam complaint or hard bounce quietly stops mail to that one address, so the sending stays clean for everyone else.
Docs
Three new documentation pages
New articles cover how an advertiser is funded and charged, how the extension detects that an agent is thinking, and every extension command and setting in one reference. New diagrams draw the surfaces, the patch-safety flow, and where your money sits. The rest of the docs were checked against the code and corrected where they had drifted, each carrying a fresh last-updated date.
Subscribe to /changelog.xml and every entry on this page arrives in your feed reader as it ships. The feed is generated from the same source as the page, so the two can never disagree.
A public status page now shows whether Awaitful is up, independently monitored and hosted outside our own infrastructure - so when we say the service is healthy, that is checkable too. Linked from every footer.
Security research now has a front door: a security.txt at the standard well-known path, a public disclosure policy, and hardened response headers on every page - a content security policy, strict transport security, and friends. Reports go to [email protected] and get read by a human.
Twenty-two articles on how everything works, every claim written against the code and ending in a checkable receipt. Each page shows when it last changed, and a feedback control on every article lets you flag anything out of date - anonymously, by construction.
The landing, privacy, and terms pages are now prerendered to static HTML, so crawlers and AI assistants read full content without running JavaScript. The site also gained its mark-only logo, a sitemap, and a robots policy that welcomes AI crawlers.
Market
The bid market, watchable
Four live views of the auction: every verified view as a tick at the exact bid that paid for it, the standing order book, the slate minute by minute, and cumulative money paid to developers. Real data only - a quiet market renders as honest quiet, never as a fake pulse.
A new setting controls whether an advertiser logo appears before the sponsored line on the webview surfaces. Off means text only; on never invents a logo for ads without one.
The installer finds your editor - VS Code, Cursor, Devin, VSCodium, VS Code Insiders - and installs the extension from its own marketplace. Zero dependencies and no network calls of its own, both enforced by its published tests.
Advertisers can link or upload any image; the server downscales it and inlines the bytes into the ad, so an editor never fetches from an advertiser server and a developer address never reaches one. The setup guide also arrived: a floating checklist that follows you until setup is done.
The auction now excludes your own campaigns from the slates your machines see, on top of the ledger rule that already refused self-view money. The client also stopped claiming editor safety it had not verified for the running build.
Money moved onto a balanced double-entry ledger: each verified charge books the advertiser debit, the developer share, and the platform fee as one transaction that must balance. Money is never conjured and never quietly lost.
The client went public and the extension shipped to the VS Code Marketplace and Open VSX. From this day the code that runs on your machine is the code you can read.
Sign in with Google or GitHub, approve in the browser
Social sign-in arrived, and linking an editor became a one-tap approval in the browser using the session you already have. The egress manifest also went public: every request the client can make, written down field by field.
Two more surfaces: the chat banner and the terminal
The sponsored line learned to render as a banner above the composer and as a line in the terminal status area, alongside the status bar and the thinking line. Every surface beyond the status bar is opt-in, and the money rule is identical on all of them.
The flagship surface: the sponsored line rendered over the agent thinking indicator itself. Nothing is patched unless the file bytes hash-match a known original, everything is backed up first, and any doubt falls back to the status bar.
The monorepo is born and the backend deploys: auction, slates, verified events, and the first sponsored line served end to end. Everything since is on this page.