Cloudflare shipped an agentic CLI for its API ⚡️
Cloudflare launched
This is a practical alternative to collecting one-off curl commands in a wiki or maintaining small admin scripts for every service. The CLI gives humans and coding agents one command-line entry point for Cloudflare operations.
Where it fits✅ :
• Inspect and change Cloudflare resources while debugging a service.
• Give an agent a constrained operational interface instead of raw dashboard access.
• Turn repeatable incident steps into checked-in commands and runbooks.
Do not hand an agent broad production credentials because it has a nice CLI. Use scoped tokens, separate environments, and audit the resulting changes.
[ Blog ] :
https://blog.cloudflare.com/cloudflare-cf-cli-launch
〰️〰️〰️〰️〰️〰️
#Cloudflare #CLI #DevOps #Agents #LLM
@ProgrammingTip
Cloudflare launched
cf, an agentic CLI for its full API surface.This is a practical alternative to collecting one-off curl commands in a wiki or maintaining small admin scripts for every service. The CLI gives humans and coding agents one command-line entry point for Cloudflare operations.
Where it fits
• Inspect and change Cloudflare resources while debugging a service.
• Give an agent a constrained operational interface instead of raw dashboard access.
• Turn repeatable incident steps into checked-in commands and runbooks.
Do not hand an agent broad production credentials because it has a nice CLI. Use scoped tokens, separate environments, and audit the resulting changes.
[ Blog ] :
https://blog.cloudflare.com/cloudflare-cf-cli-launch
〰️〰️〰️〰️〰️〰️
#Cloudflare #CLI #DevOps #Agents #LLM
@ProgrammingTip
Please open Telegram to view this post
VIEW IN TELEGRAM
Cloudflare Blog
Introducing cf: the agentic CLI for the entire Cloudflare API
We are releasing cf, our new command-line tool that mirrors the entire Cloudflare API and supports programmatic TypeScript configuration. We are also open-sourcing Forge, our internal SDK generator.
GitHub is rebuilding Git storage for agent-scale work ⚡️
GitHub explained the storage work behind Git at agent scale. More coding agents means more branches, refs, fetches, pushes, and short-lived repositories hitting the platform at once.
What changed:
• Repository storage moved to Azure as part of the platform migration.
• Per-reference write quorums help coordinate Git ref updates.
• Virtual replicas backed by object storage reduce the need to copy every repository everywhere.
This is infrastructure work, but .NET teams feel it directly. When CI, bots, Copilot-style agents, and developer machines all create refs concurrently, a normal Git workflow becomes a distributed-systems workload.
Worth reading if your build automation creates branches or tags and you still treat a failed push as "just retry it."
[ Blog ] :
https://github.blog/engineering/architecture-optimization/the-bridge-to-agent-scale-git-infrastructure/
〰〰〰〰〰〰
#dotnet #GitHub #Git #DevOps
@ProgrammingTip
GitHub explained the storage work behind Git at agent scale. More coding agents means more branches, refs, fetches, pushes, and short-lived repositories hitting the platform at once.
What changed:
• Repository storage moved to Azure as part of the platform migration.
• Per-reference write quorums help coordinate Git ref updates.
• Virtual replicas backed by object storage reduce the need to copy every repository everywhere.
This is infrastructure work, but .NET teams feel it directly. When CI, bots, Copilot-style agents, and developer machines all create refs concurrently, a normal Git workflow becomes a distributed-systems workload.
Worth reading if your build automation creates branches or tags and you still treat a failed push as "just retry it."
[ Blog ] :
https://github.blog/engineering/architecture-optimization/the-bridge-to-agent-scale-git-infrastructure/
〰〰〰〰〰〰
#dotnet #GitHub #Git #DevOps
@ProgrammingTip
The GitHub Blog
The bridge to agent-scale Git infrastructure
We moved a copy of 99.99999% of GitHub's repositories to Azure. Here's how per-reference quorums will bring over the rest.