Skip to main content

Posts

GitHub Resets Copilot Pricing as AI Compute Costs Surge

The development community saw this one coming: GitHub will transition its Copilot service to a usage-based billing model on June 1, replacing its existing system of fixed subscriptions supplemented by premium request limits. As reported last week, GitHub suspended new sign-ups for several of its Copilot subscription tiers as it faced a surge in demand from agentic coding workflows. To address that, under GitHub’s new pricing model, customers across individual, business, and enterprise tiers will receive a monthly allocation of AI credits, which are consumed based on token usage. This includes input, output, and cached data processed by underlying models. Once those credits are exhausted, users can purchase additional capacity at published rates. The change leaves base subscription prices intact. Individual plans remain priced at $10 per month for Pro and $39 for Pro+, while business and enterprise tiers continue at $19 and $39 per user per month, respectively. Each plan’s monthly ...
Post a Comment
Read more
Recent posts

Embracing the MCP Suck: Taming the Wild West of AI Protocols

The Model Context Protocol (MCP) is moving faster than the developer community can keep up with, racing past its original design parameters and leaving teams scrambling to build clients that can match its pace. The result is an ecosystem where the protocol itself keeps shifting under everyone’s feet, and where the tooling, conventions and security thinking that should accompany a foundational standard are still being figured out on the fly. Joey Stout, solutions architect at Spacelift, joins Mike Vizard to make the case that this is the price of being early. Stout describes an environment that increasingly resembles a Wild West, where rogue MCP servers get spun up inside organizations without anyone in leadership knowing they exist, let alone whether they have basic guardrails wrapped around them. The convenience of standing one up in a few minutes has outrun the discipline needed to govern them. MCP servers can give AI agents broad reach into internal systems, data and APIs, an...
Post a Comment
Read more

Ten Great DevOps Job Opportunities

DevOps.com is now providing a weekly DevOps jobs report through which opportunities for DevOps professionals will be highlighted as part of an effort to better serve our audience. Our goal in these challenging economic times is to make it just that much easier for DevOps professionals to advance their careers. Of course, the pool of available DevOps talent is still relatively constrained, so when one DevOps professional takes on a new role, it tends to create opportunities for others. The ten job postings shared this week are selected based on the company looking to hire, the vertical industry segment and naturally, the pay scale being offered. We’re also committed to providing additional insights into the state of the DevOps job market. In the meantime, for your consideration. Dice Booz Allen Hamilton Beavercreek, OH DevOps Engineer $61,900 to $141,000 CGI Reston, VA DevOps Engineer $108,300 to $137,100 Noblis Philadelphia, PA DevOps Engineer $86,800 to $135,625 Le...
Post a Comment
Read more

Microsoft Foundry Tackles the AI Agent Tool Problem Nobody Talks About

Building AI agents sounds straightforward until you actually do it. You need an agent to onboard a new employee. It has to create an Entra ID account, provision GitHub access, spin up cloud resources, create tasks in Azure DevOps, and send a welcome message in Teams. Five tools. Five different authentication models. Five different teams are managing those tools. Now multiply that across every agent your organization is building. That’s the problem Microsoft is addressing with Toolboxes in Foundry, now available in public preview. What Toolboxes Actually Do A Toolbox is a named, reusable bundle of tools managed in Microsoft Foundry. You define your tools once, configure authentication centrally, and expose everything through a single MCP-compatible endpoint. Any agent that can consume an MCP endpoint can use a Toolbox — regardless of the framework it was built on. The endpoint looks like this: https://zava.services.ai.azure.com/api/projects/<project>/toolbox/<toolbox-na...
Post a Comment
Read more

Microsoft Turns to Anthropic’s Mythos to Improve Cyber Defense

Microsoft has unveiled plans to incorporate Anthropic’s Claude Mythos Preview model and other AI models into its Security Development Lifecycle, embedding AI directly into the stages where code is written and tested. Rather than relying primarily on static analysis tools, Microsoft is adopting AI models capable of analyzing code dynamically and identifying complex vulnerabilities that might otherwise go undetected until later stages of development. Released on April 7, Anthropic’s Mythos model has already demonstrated a previously unmatched ability to uncover critical flaws across operating systems and widely used software. Anthropic claimed that the model’s ability to find security vulnerabilities is so advanced that it should not be released to the public. Microsoft gained access to the model through Anthropic’s Project Glasswing, a program that grants limited access to select tech firms for cybersecurity research. Within this framework, Microsoft is reporting measurable improve...
Post a Comment
Read more

Why Contact Enrichment Belongs in Your Application Architecture, Not Your Sales Workflow

Most B2B applications collect incomplete data by design. A lead form captures a name and company. A recruiting tool surfaces a LinkedIn profile. An event registration system logs an email address and job title. The record enters your system and sits there, half-formed, waiting for someone to manually fill in the gaps before it can be acted on. This is an architectural problem, not a workflow problem, and solving it at the architecture layer is what separates applications that create operational leverage from ones that just digitize manual work. Understanding how to build contact enrichment into your application using professional data APIs changes  how you think about the data ingestion layer entirely. Rather than passing incomplete records downstream and hoping someone fills in the blanks, you enrich at the point of entry, automatically, before the record ever reaches a human. The Architecture Problem Behind Incomplete Lead Records The gap between the data a user submits and t...
Post a Comment
Read more

Claude’s Code Quality Conundrum Continues

A lot is going on at Anthropic. Access to the almost-fabled Mythos model remains restricted (despite some reports of unauthorized access), and nobody knows quite what is likely to happen or when in terms of its final rollout. Developers, meanwhile, are left with their own challenges; last week’s “upgrade” to Opus 4.7 has left some software engineers already longing for a return to 4.6 with its less literal instruction interpretation and its perhaps less cautious use of safeguards and controls. Then there’s the Claude quality conundrum in and of itself. Root of the Problem? Anthropic says it recognizes the fact that users are reporting that they are getting “worsened responses” over the past month. In answer to this, the organization confirms it has traced these reports to three separate changes that affected Claude Code, the Claude Agent SDK, and Claude Cowork. The Claude API and the inference layer were not impacted. All three issues have now been resolved as of April 20 (vers...
Post a Comment
Read more