The blog
Development, stacks & AI
Notes on modern development, stack updates and AI-assisted development.
Turborepo: securing the Vercel remote cache with OIDC
Since late July 2026, Vercel's remote cache accepts OIDC authentication for Turborepo: replace permanent tokens with a short-lived CI identity.
Next.js 16.2: getting your projects ready for AI agent workflows
Next.js 16.2 brings concrete building blocks that make front-end projects easier to read, debug and drive with AI agents, without giving up human verification.
GitHub Copilot now bills by usage: how to adapt your coding agent workflows
Since June 1, 2026, GitHub Copilot has moved to billing based on GitHub AI Credits. The listed plan price is no longer enough: you have to manage models, budgets and agent-driven workflows.
Coding agents: why the `codexui-android` incident means securing AI tools like production
The `codexui-android` incident shows that coding agent tools are no longer mere developer gadgets. When they access repositories, terminals and authentication tokens, they must be audited, isolated and monitored like production components.
Coding agents: the sandbox becomes baseline infrastructure, not an option
Development agents are no longer just a productivity interface. As soon as they run commands, read files and call tools, their sandbox becomes an architecture decision.
GitHub Copilot and AI Credits: taking back control of coding agent costs
Since June 1, 2026, GitHub's assistant bills many advanced uses in GitHub AI Credits. For freelancers and product teams, the point isn't to drop the tool, but to measure and budget its use, then reserve agents for the right workflows.
Copilot becomes a variable cost: govern your dev agents before the billing surprise
Since June 1, 2026, GitHub Copilot bills advanced uses through GitHub AI Credits. For product teams, freelancers and technical founders, the topic goes beyond productivity: it's about governing the costs of agents, automated code review and frontier models.
AI development agents in 2026: choosing between SaaS, CLI/IDE and controlled infrastructure
In 2026, the real decision is no longer whether an AI agent can code, but where to run it, with which permissions, which logs, which secrets and which cost model.
GitHub Actions: test Node 24 before the June 2026 switch
GitHub Actions will start running JavaScript actions on Node 24 by default from June 16, 2026. Here's what to check now, whether you maintain an action or depend on third-party actions in production.
AI-assisted development: what really changes
Beyond autocomplete: how AI agents are changing a developer's daily work, and how to benefit from them without losing control.