Semaphore Uncut

Semaphore

Semaphore Uncut takes you behind the scenes of building AI-native Semaphore CI/CD. Tune in for CI/CD best practices for AI-driven software development, product updates, and learnings from our engineering team. semaphoreio.substack.com

  1. Building an AI-Native CICD Experience with sem-ai

    May 27

    Building an AI-Native CICD Experience with sem-ai

    We’ve been talking a lot recently about AI-native developer workflows and where CICD is heading. This week, we shared one of our most exciting demos yet: a look at how SEMai is changing the way developers interact with CICD systems. In the demo, Marcos starts with a completely clean repository: no CI configuration, no GitHub Actions workflows, nothing. Then, inside Claude Code, he runs a single command: /sem-ai init From there, sem-ai analyzes the repository, detects the tech stack, and generates a tailored CICD pipeline automatically. It recommends: * Linting * Security scanning * Matrix testing * Pipeline topology improvements But the most interesting part comes afterward. Marcos tells the agent: “Work until the pipeline is green.” The system monitors the pipeline, analyzes failures, applies fixes, reruns workflows, and eventually gets the build passing successfully while summarizing everything it changed along the way. Nick also shares lessons learned while building the onboarding experience itself, including why slash commands became critical for reliable agent workflows and how improving contextual skills dramatically increased success rates. This is what we mean when we talk about AI-native CICD:not AI bolted onto existing tooling, but a fundamentally different developer experience built around collaboration between developers and agents. In the full demo, Marko, Marcos, and Nick walk through: * AI-assisted CICD onboarding * Slash command workflows * Self-healing pipelines * Pipeline optimization * The evolution of SEMai skills and agent context We’re excited about where this is heading and look forward to sharing more soon. Pete Miloravachttps://semaphore.io This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit semaphoreio.substack.com

    3 min
  2. Introducing Semaphore for AI Agents

    May 14

    Introducing Semaphore for AI Agents

    Developers are increasingly working inside AI-powered coding tools like Claude Code, Cursor, and Codex. The workflow is changing. Instead of constantly switching between dashboards, logs, terminals, and configuration files, developers are starting to collaborate directly with coding agents using natural language. We think CI/CD should evolve alongside that shift. Today, we’re introducing Semaphore for AI Agents — a new open-source CLI and agentic interface designed to make Semaphore fully accessible from AI coding agents. This is the first step toward what we call the AI-native Semaphore experience. What is Semaphore for AI Agents? Semaphore for AI Agents gives coding assistants a structured way to interact with Semaphore. Instead of manually navigating CI/CD systems, developers can simply ask: * “Why is my CI failing?” * “What tests are flaky?” * “Show me the critical path in this pipeline.” * “Summarize the health of this project.” And their coding agent can retrieve, analyze, and act on that information directly through Semaphore. The first release includes: * Pipeline diagnostics * Flaky test detection * Critical path analysis * Organization-wide CI/CD insights * MCP support * Claude Code integrations * Remote execution workflows on Semaphore infrastructure We also demonstrate how developers can provision ephemeral machines for agent-driven workflows, remote testing, and scalable execution. Built for Agentic Workflows Semaphore for AI Agents was designed specifically for AI-native development workflows. The project ships with: * Agent-oriented commands * Structured JSON outputs * Claude Code skills * Generic agent skills * A local MCP server This allows coding assistants to interact directly with Semaphore while developers stay inside their coding environment. Fully Open Source Semaphore for AI Agents is fully open source. Developers can inspect how it works, extend workflows, contribute new commands, and build their own automations. We believe AI-powered developer tooling should remain transparent, inspectable, and developer-controlled. This Is Just the Beginning Semaphore for AI Agents is the foundation for a broader direction we’re building toward at Semaphore: * Developers define intent * Agents handle repetitive execution * Semaphore provides the infrastructure and orchestration layer Over the coming weeks, we’ll continue shipping new workflows, MCP capabilities, testing automation, and scalable agent execution features. Watch the Demo We recorded a full walkthrough showing: * CI/CD debugging workflows * MCP integrations * Claude Code usage * Organization-wide insights * Remote execution on Semaphore infrastructure → [Read the full blog post] Thanks for following along. Till the next product update. Pete Miloravachttps://semaphore.io This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit semaphoreio.substack.com

    3 min
  3. Introducing .NET Support on Semaphore

    Apr 7

    Introducing .NET Support on Semaphore

    Modern development teams don’t all build on the same stack and they should not have to. Today, we are expanding Semaphore’s capabilities to better support teams building on the Microsoft ecosystem, with first class support for the .NET framework and Microsoft Edge in CI pipelines. This marks an important step toward making Semaphore a truly flexible platform for all developers, regardless of their technology choices. Supporting More Developers, Where They Work Until now, Semaphore has primarily focused on Linux native tooling and ecosystems. With this update, we are extending that foundation to support developers working with the Microsoft stack. This includes: * .NET SDK support for building and compiling applications in CI * Microsoft Edge browser support for running end to end and UI tests * Full compatibility within Semaphore pipelines running on Linux By enabling these tools, teams can now build, test, and validate .NET applications directly within Semaphore, without workarounds or custom environments. Built on a Familiar, Reliable Foundation This new support is already available in production, as part of our latest updates (see the changelog), and works on our latest Ubuntu 24.04 image. You can learn more about the environment here. By leveraging Linux compatible tooling for the Microsoft ecosystem, we are making it possible to run .NET workloads in the same scalable, reliable CI/CD environment teams already use for other stacks. This approach keeps things simple: * No need to manage separate CI systems * No need to maintain custom infrastructure * No disruption to existing workflows Just a consistent, unified pipeline experience. Why This Matters As development ecosystems continue to evolve, teams are increasingly working across multiple stacks and technologies. Supporting .NET is not just about adding another SDK. It is about expanding what developers can do within a single CI/CD platform. This aligns directly with our broader vision: * Reduce friction in software delivery * Automate the repetitive work behind building and testing * Let developers focus on what actually matters As outlined in our 2026 product strategy, our goal is to remove unnecessary toil and make the right thing the easy thing inside CI/CD . Bringing .NET into Semaphore is one more step toward that goal. What’s Next We have also prepared a simple demo project showcasing how to build and test a .NET application on Semaphore. You can access it here. Alongside that, documentation updates and image changes are already available, and we will continue improving the experience based on feedback. This is just the beginning. As we continue expanding language and ecosystem support, our focus remains the same. Helping developers ship high quality software faster, with less manual effort. Happy building!Pete Miloravac Semaphorehttps://semaphore.io This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit semaphoreio.substack.com

    1 min
  4. OAuth for MCP Servers — Lessons from Building for AI Agents

    Mar 19

    OAuth for MCP Servers — Lessons from Building for AI Agents

    As AI agents become part of everyday development workflows, authentication is becoming a critical piece of the puzzle. In our latest product update, we’re sharing a behind-the-scenes look at how we implemented OAuth for Semaphore’s MCP server—and what we learned along the way. You’ll get a practical perspective on: * Why OAuth is essential for MCP and AI agents * The challenges of working with evolving specs and inconsistent agent behavior * What actually works in real-world implementations * Key lessons for building secure, reliable integrations This isn’t theory—it’s a real engineering deep dive from our team. 👉 Read the full blog post👉 Watch the full video This work is part of a broader shift at Semaphore, where we’re extending CICD with AI-powered workflows—while keeping developers in control and reducing manual work. If you’re building with MCP or exploring agent-driven workflows, this one’s worth your time. — Pete MiloravacThe Semaphore Teamhttps://semaphore.io This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit semaphoreio.substack.com

    16 min
  5. Semaphore’s New Pricing Model: Built for the AI Era of CICD

    Mar 16

    Semaphore’s New Pricing Model: Built for the AI Era of CICD

    Today we’re introducing an important change to how Semaphore pricing works. CICD is no longer something that runs occasionally during development. For many teams, it’s now always-on infrastructure that powers software delivery. To support this shift, we’re introducing a new Semaphore pricing model designed to keep CICD fast, scalable, and affordable as usage grows. What’s changing The new model separates compute infrastructure from support and success services, giving teams more transparency and flexibility in how they use Semaphore. Key updates include: Lower machine pricing Semaphore’s fastest runners are now available at significantly reduced prices, starting at $0.0075 per minute. Our new f1 machines replace the previous e1 and e2 runners, focusing the platform on high-performance compute optimized for CICD workloads. Usage-based pricing for self-hosted agents Self-hosted agents are no longer billed per developer seat.Instead, usage is priced purely based on compute time at $0.0025 per minute. Support and success plans are now separate Infrastructure pricing now reflects compute consumption only.Teams can choose optional Support and Success plans depending on their operational needs and level of optimization guidance. A modular approach to CICD Teams can now combine: * Compute infrastructure * Support plans for operational reliability * Success plans for performance optimization * On-demand engineering assistance This modular model makes it easier to scale Semaphore alongside your CICD usage. For existing customers Nothing changes immediately. You can continue using your current plan as-is, and when you’re ready, you’ll be able to switch to the new pricing structure directly in the app. Learn more You can explore the full pricing details here: 👉 Pricing page👉 Try out Semaphore If you have any questions, drop us an email at support@semaphore.io The Semaphore Team This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit semaphoreio.substack.com

    3 min
  6. OAuth Authentication for the Semaphore MCP Server

    Mar 6

    OAuth Authentication for the Semaphore MCP Server

    We’re preparing a new update for the Semaphore MCP server that will make it easier for developers to connect AI agents and developer tools. The focus of this update is authentication. Today, connecting an agent to the MCP server typically requires using a long-lived API token. While this works well, it also means developers need to generate credentials, store them in configuration files, and manage them manually. In our next release, coming next week, we’re introducing OAuth authentication support for the MCP server. This will make connecting agents and developer tools significantly simpler. Instead of generating and storing API tokens, developers will be able to authenticate through a familiar OAuth flow. When configuring an agent, a browser window opens, you log in, and approve access to the MCP server. Once approved, the connection is established automatically. This approach removes the need to manage long-lived credentials and makes integrations easier to set up. It also improves compatibility with modern agentic development tools. Some tools have limitations when working with static API tokens, and OAuth removes those barriers. Read more on our blog. Pete Miloravac The Semaphore Team https://semaphore.io This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit semaphoreio.substack.com

    2 min
  7. AI-Driven Onboarding and Workflow Automation in Semaphore

    Mar 2

    AI-Driven Onboarding and Workflow Automation in Semaphore

    🚀 We’re introducing AI-driven onboarding and workflow automation in Semaphore. Our new assistive agent helps teams generate pipeline configurations, understand failed jobs, re-run workflows, and refine CI/CD setups using natural language — all while keeping developers fully in control. This is the beginning of Agent-Driven Semaphore: CI/CD at the core, AI handling the repetitive work. Watch to see what’s coming next. Give Semaphore a spin:https://semaphore.io/ This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit semaphoreio.substack.com

    3 min
  8. Extending CI/CD and What’s Next for Semaphore

    Feb 19

    Extending CI/CD and What’s Next for Semaphore

    Over the past few weeks, we’ve been refining our roadmap for 2026 and focusing on where Semaphore can deliver the most value. Our direction is clear: extend CI/CD beyond execution — and help developers ship software faster. Here’s what’s coming next. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit semaphoreio.substack.com

    3 min
See All (158)

Ratings & Reviews

5
out of 5
2 Ratings

About

Semaphore Uncut takes you behind the scenes of building AI-native Semaphore CI/CD. Tune in for CI/CD best practices for AI-driven software development, product updates, and learnings from our engineering team. semaphoreio.substack.com

Information

  • Creator
    Semaphore
  • Years Active
    2019 - 2026
  • Episodes
    158
  • Rating
    Clean
  • Copyright
    © Semaphore
  • Show Website
    Semaphore Uncut

You Might Also Like