Systems | Development | Analytics | API | Testing

You’ve probably encountered the online conversations about GitHub’s AI scaling challenges. A lot of the chatter is about how forgiving (or not) users should be to GitHub in light of inexorable traffic increases but also GitHub’s own decision-making. There is certainly irony in the fact that it was a swashbuckling GitHub, against the objections of many open source developers, that pressed Copilot on the industry.

How you store a streamed AI response decides what a client sees when the client joins partway through. A human agent taking over a support conversation, a refreshed browser, and a second device all need the response generated so far, and depending on how the response was stored, that late joiner gets the full response, fragments, or nothing. This article compares four common ways to store a streamed response, what each one gives a late joiner, and what each one costs your team.

Agentic AI governance is the structured management of the authority an organization hands to autonomous AI systems that plan and take action on its behalf. It covers what an AI agent is allowed to do, which systems it can touch, and how those permissions are monitored, limited, and revoked using robust autonomous AI governance controls.

Sidekiq is a background job framework for Ruby that processes jobs concurrently on threads, backed by Redis. In Rails, add gem "sidekiq", set config.active_job.queue_adapter = :sidekiq, enqueue with perform_async, and run the sidekiq process alongside your app server. Sidekiq 8 requires Ruby 3.2+ and Redis 7+. That answer covers the mechanics.

This year, AI agents have been writing more code than ever, and we've seen the slow part of shipping move from writing code to building and releasing it. You've probably felt it in your own team too. So this quarter we focused on making sure all that extra code doesn't turn into extra waiting for you. Here are the 20+ updates we shipped across Bitrise in Q3.