@wahidsaleemi@HermesAgentTips@OpenRouter Wait - I thought the open router/auto was based on latency and model availability - not a smart router? Did they change this?
@HermesAgentTips It's more a question of what you can afford! I'm currently riding the limits on my Kimi plan for K2.6 which is by far the best tool using agent for balance of tokens and multi calls imo.
@Microsoft365 please please can we enforce users of MS Scout to have E5 licenses minimum so we can ensure they dont cheap out without DLP and purview etc...?
@Microsoft365 please please can we enforce users of MS Scout to have E5 licenses minimum so we can ensure they dont cheap out without DLP and purview etc...?
@windowsdev its not lost on me that the @GitHubCopilot billing system changed a day before they released this which requires a ...Github billing account/subscription.
About to finish my install of @windowsdev Microsoft Scout. Intune all set up - Time to see the power of the Claw under MS's iron policy based fist!...
(or potential lack thereof.)
@aymieelis@MichaelGannotti@Microsoft@Microsoft365 No identity needed in Github, that seems to be purely for the AI inference billing. EntraID/whatever they want to call M365/Azure AD now is where the Identity is propagated from.
anyone looking for some coffee time reading, I always like checking in on @CloudflareRadar stats page, always something interesting going on! https://t.co/9uDhVzy9mD
Formal Complaint: GitHub Copilot Token-Based Billing Model
@GitHubCopilot
Subject: Critical Issue with New Token-Based Billing — Product Has Become Unusable
Summary of the Issue
I am writing to formally complain about the recent shift to token-based billing for GitHub Copilot, which was rolled out this morning. This change has fundamentally broken the value proposition of the product and is rendering it unusable for paying subscribers, including myself.
Specific Problems Observed
Within just a few hours of the new billing model going live, the developer community is already reporting alarming consumption patterns:
Pro+ subscribers paying $39/month are reporting that 60% of their monthly credits were depleted in only 2 hours of normal usage.
One user reported losing 20% of their entire monthly allowance from a single file review — no code generation, just a review.
At this rate, a paying customer will exhaust their plan in less than a single working day, despite paying a premium subscription fee.
This is not "normal usage at scale" — this is a broken pricing model that punishes the very developers who rely on Copilot daily for their work.
Why This Makes the Product Unusable
The core promise of Copilot was a predictable, always-available AI coding assistant integrated into the developer workflow. Token-based billing destroys that promise because:
Developers cannot predict costs. Every keystroke, every file review, every refactor becomes a financial calculation rather than a productivity boost.
The tool actively discourages use. Users will hesitate before invoking Copilot, defeating the entire point of an AI assistant.
The $39/month Pro+ tier is misleading. Customers signed up expecting reliable access, not a pre-paid metered service that runs out mid-morning.
Heavy users — your most loyal customers — are penalized the most.
The Competitive Reality
While GitHub Copilot is moving toward a restrictive metered model, competitors are moving in the opposite direction:
Cursor offers Composer 2.5 with unlimited usage once token limits are reached on their plans, ensuring developers can keep working without interruption.
Other tools (Windsurf, Cody, Continue) offer flat-rate or far more generous usage tiers.
Developers will not stay on a platform that runs out of credits before lunch when alternatives offer uninterrupted productivity at the same or lower price point.
My Demand
If GitHub does not revise this licensing model, the product is effectively dead. I am requesting:
Reinstatement of a flat-rate unlimited (or effectively unlimited) tier for Pro and Pro+ subscribers.
Transparent, upfront communication of what each interaction actually costs in tokens.
A grace period or credit refund for users who burned through their allowance under the new model without warning.
A long-term commitment that core IDE-integrated features will not be metered into uselessness.
Without these changes, I — along with a growing number of developers — will be canceling our subscriptions and migrating to Cursor or competing alternatives. The decision to monetize aggressively at the expense of usability will not be remembered as a successful pivot; it will be remembered as the moment GitHub Copilot lost its market.
Please escalate this to the product and pricing teams immediately.
@MichaelwEllison@benedictevans I never considered 'figuring' (and the human computer) was its own entire profession before calculators 👀
Just spent 20mins reading about slide rules and logarithmic mathematical reference books. TIL!
@MichaelwEllison@benedictevans I never considered 'figuring' (and the human computer) was its own entire profession before calculators 👀
Just spent 20mins reading about slide rules and logarithmic mathematical reference books. TIL!
FUCK<
Both @openclaw & @NousResearch Hermes Agent both have fully native Windows modes now and 0 barrier to entry.
A security nightmare of an agentic privacy apocalypse will soon take place. When even devs are giving out bad security advice 'normies' don't stand a chance.
Congrats! Looks great.
Looking forward to the detached remote/headless version of this. Will be SUPER powerfull to control all my VPS based Hermes agents via a local native desktop app, even better if it integrates cloudflared, tailscale, or even better - simple but effective, SSH
@IBuzovskyi : respect the enthusiasm, but this "just give it your email and install on your main PC" advice is a ticking time bomb.
It is legit dangerous advice with all the newcomers into this market.
The moat of proficiency and skill keeping out non-technical users has now evaporated with the likes of Openclaw and hermes agent having native (windows/mac/linux) desktop applications.