Blog Posts with tag "GitHub Copilot"

Using MiMo V2.5 with GitHub Copilot BYOK and OpenCode Zen (Promo)

Using MiMo V2.5 with GitHub Copilot BYOK and OpenCode Zen (Promo)

MiMo V2.5 is the latest reasoning and coding model from Xiaomi’s AI lab. Xiaomi positions MiMo as a general-purpose reasoning model with particular strength in code generation, structured output and tool calling. In May 2026 the model was made available through OpenCode Zen as part of a promotional offer, meaning it can be used at no cost during the promotion period.

Read Blog Post
Using OpenAI Models in VS Code with GitHub Copilot BYOK

Using OpenAI Models in VS Code with GitHub Copilot BYOK

GitHub Copilot’s pricing shift from flat premium request units to token-based GitHub AI Credits, scheduled for June 1, 2026, changes the economics of heavy AI usage in VS Code meaningfully. Models with large context windows, high output verbosity or intensive agent loops now have a more direct relationship between compute and cost. That makes model selection a more relevant engineering decision than it was under the older quota model.

Read Blog Post
Using Kimi K2.5 and DeepSeek V4 in VS Code with GitHub Copilot BYOK and OpenCode

Using Kimi K2.5 and DeepSeek V4 in VS Code with GitHub Copilot BYOK and OpenCode

GitHub Copilot is moving into a different cost model. GitHub announced that Copilot plans will transition from premium request units to GitHub AI Credits on June 1, 2026. Usage will be calculated from token consumption, including input, output and cached tokens, using the listed API rates for each model. This is a more direct mapping between compute usage and billing, but it also changes the economics for teams that have started to use agentic workflows heavily.

Read Blog Post
GitHub Copilot - Custom Agents for Full-Stack Teams: A Practical Operating Model for .NET, React and Azure

GitHub Copilot - Custom Agents for Full-Stack Teams: A Practical Operating Model for .NET, React and Azure

GitHub Copilot custom agents allow teams to define specialized AI assistants, each with its own role, tool access and behavioral boundaries. Instead of relying on one general-purpose assistant for everything, a team can create multiple agents that mirror the actual roles in the engineering organization. After working with custom agents for a while, the biggest insight was simple: the quality of AI-assisted engineering improves dramatically once the AI knows what role it is supposed to play.

Read Blog Post
Agent Skills Standard: The Quality Contract Behind Reliable AI Agents

Agent Skills Standard: The Quality Contract Behind Reliable AI Agents

Large language model agents can appear intelligent while still producing unstable output across runs, contexts and tasks. In practice, this instability is rarely caused by model quality alone. The dominant factor is often missing operational structure: no explicit boundaries, no role-specific constraints, no reusable task patterns and no agreed execution policy.

Read Blog Post