Feature Requests

Summary: Today, publishing any orb version (including dev/alpha) requires a personal API token from an org owner; using a project API token results in AUTHORIZATION_FAILURE, even for dev orbs.[Ticket 167650] This forces teams to expose an owner’s personal token (or a bot owner token) via contexts so non‑owners can publish, which is a security and operational concern.[Non‑owner orb publish] Requested change: Support using project API tokens to publish development (dev/alpha) orb versions, while keeping production SemVer publishing restricted to org owners. Why this matters: Let's non‑owner developers independently publish dev/alpha orbs for testing. Keeps production orb releases under org‑owner control. Avoids sharing owner‑level personal tokens in contexts accessible to non‑owners. Reduces overhead of managing bot owner accounts just for orb publishing.[Ticket 167650] This would provide a clearer security boundary between development and production orb workflows.

Direct Image Display in CircleCI UI Add native image visualization and comparison capabilities to the CircleCI UI for Visual Regression Testing (VRT) workflows. This would eliminate manual workflow steps - no more uploading to external storage or manual PR comments. The ideal approach is a built-in comparison view showing expected vs. actual images, with highlighting of pixel differences, and basic zoom/pan controls for detailed inspection.

Hi everyone, When we talk about CI/CD and cloud performance, we often focus on build times and pipeline efficiency. However, the "human element" in the development cycle is just as critical. Maintaining deep focus and sharp reaction times is essential when debugging complex yaml configurations or managing urgent deployments. I’ve been using a minimalist, physics-based simulation as a mental "calibration" tool to stay sharp during long coding sessions. It’s called Slice Master . From a technical standpoint, I find it useful for testing browser input latency and frame-rate consistency on different machine setups. Because it requires millisecond-perfect timing to flip and land objects correctly, it acts as a great rhythmic exercise to reset my focus between intensive tasks. It’s a simple way to ensure my own "internal latency" is as low as my pipeline’s execution time. Do you have any specific tools or exercises you use to maintain peak concentration or to benchmark your system's responsiveness during the workday? Best regards,

Hi everyone, When we are configuring pipelines and working within high-load cloud environments, we often focus on build times and resource allocation. However, for those of us managing complex web-based dashboards and interactive tools, the "perceived latency" of the browser’s execution engine is just as critical. Ensuring that JavaScript event loops and GPU rendering remain deterministic under load is a constant challenge. I’ve been using a high-precision, physics-driven "Video Game Entity" as a practical way to benchmark input responsiveness and rendering consistency. It is called Slice Master . Because the simulation requires millisecond-accurate timing for its physics-based mechanics, it’s an excellent qualitative tool for detecting micro-stutters or scheduling delays in the browser's main thread. If you are testing hardware acceleration on different endpoint configurations or verifying the smoothness of a virtualized desktop environment, a few minutes with this simulation can reveal bottlenecks that synthetic logs might miss. It’s a great way to verify that your environment is truly optimized for real-time interaction. Have any of you used interactive physics simulations like this to stress-test your local rendering environments or to measure input-to-pixel latency beyond standard profiling tools? Best regards,

when you expand to show more pipelines, then interact with a pipeline, the show more state is lost. thus, if you scroll to a pipeline far down and then want to do multiple actions on it, the user experience is pretty rough.

One of the most important aspects of a modern CI/CD platform is the speed and clarity of feedback. When developers push code, they need to know quickly whether a build succeeded, failed, or requires attention. Slow or unclear feedback loops increase context switching and reduce overall productivity. In cloud-based CI/CD systems, even small improvements—such as clearer error messages, faster job startup times, or more granular pipeline statuses—can have a significant impact on developer experience. Features like instant log streaming, better failure categorization, and lightweight retries help developers understand issues without digging through excessive output. This concept is very similar to how well-designed interactive systems work in other domains. For example, simple games like Slice Master rely on immediate response and clear visual feedback to keep users engaged. Every action results in an instant outcome, allowing players to adjust their next move without confusion. You can see this design . While it’s a game, the underlying principle—fast feedback enabling quick iteration—is exactly what developers need in CI pipelines. Applying this mindset to CircleCI Cloud could mean features such as real-time failure hints, smarter test result summaries, or clearer signals about which step actually caused a pipeline to fail. These improvements would reduce friction, shorten debugging time, and make CI feel more responsive and intuitive. Ultimately, CI/CD tools succeed when they help developers iterate quickly and confidently. By prioritizing immediate, actionable feedback, CircleCI can further enhance developer productivity and make cloud pipelines feel as smooth and satisfying as any well-designed interactive system.

As requested by many security team, we need to bring all build execution logs to a centralized logging solution. (splunk, ES, ... ). If we could have a plugin to export build exection to a file, or directly to logging server. It will be easier to keep circleci as our main build orchestrator solution.

Hey all, Is there any means to turn our public orb to private orb please ?

The project, pipelines and overview pages load slow for Bitbucket orgs with many repositories. Even with an active archival strategy and limiting read permissions for users, loading can take an unbearably long time or even time out. It would be great to improve this experience for Bitbucket orgs on the platform.

Could be a project level API key with publishing permissions, or use team membership like contexts do. Some means to expand the population of folks who can deploy prod versions of orbs without giving them global admin rights in GH. CCI-I-1108