Feature Requests

Users who run several AI coding agent sessions at once (for example multiple Claude Code processes, or a laptop plus a cloud workstation) share one Harness MCP sign-in. When one session signs in again, the other sessions can lose their access and have to re-authenticate, often well before they would expect, which interrupts long-running work. Please support multiple concurrent Hosted MCP sessions per user, so signing in from one process or machine does not end the others. This matters for teams that work on several tasks in parallel with AI agents: today they either serialize their sessions or re-authenticate repeatedly.

Hi Harness Team, We would like to request an enhancement to the Pipeline Execution UI to improve the user experience when monitoring pipelines with a large number of stages. Currently, the execution view displays all stages defined in the pipeline, including stages that have not started yet. For large pipelines, this can make the execution interface visually cluttered and make it harder for users to quickly identify the stage that is currently running or waiting for an action, such as an approval. We would like to have an option to hide stages that have not started yet, displaying only stages that are currently running or have already been executed. Ideally, this could be implemented as a configurable UI option or toggle: Show pending stages: On / Off. Completed stages Failed stages Running stages Stages waiting for user interaction, such as Harness Approval As the pipeline progresses, the next stage would automatically become visible when its execution starts. This would be especially useful for pipelines containing many sequential stages, making the execution page cleaner and allowing users to focus on the current execution context. Expected benefit: Improve pipeline execution visibility and overall user experience, especially for developers and application teams consuming standardized enterprise pipelines.

SMTP Configuration in account level need to add Fire and Forget option. becuase some time our organization email server gateways has high queue and latency and delay for acknowledgement. so we need default option in SMTP Configuration so that all approval email and notification email will not timeout and will be delivery email in queue.

Description Currently, custom Service Discovery Collector images must be configured individually for each Discovery Agent. This can introduce additional maintenance overhead for organizations managing multiple agents across different projects and environments. While Resilience Testing provides centralized custom image configuration for its components, the Service Discovery Collector is managed separately, making it more difficult to maintain consistent image versions across related components. Proposed Enhancement Introduce an optional mechanism for Discovery Agents to use centrally managed custom images from the Resilience Testing Image Registry. This could include: Centralized image configuration: Add support for specifying a custom Service Discovery Collector image in the Resilience Testing Image Registry. Opt-in configuration: Allow Discovery Agents to optionally inherit the centrally configured collector image. Independent configuration: Preserve existing per-agent custom image overrides for Discovery Agents that do not use the centralized configuration. Simplified updates: Allow administrators to update the centrally configured image without manually modifying each participating Discovery Agent. Benefits Simplifies custom image management across multiple Discovery Agents. Reduces manual configuration and maintenance overhead. Helps maintain consistent image versions across Resilience Testing components. Supports environments requiring customized container images, such as those containing internal certificates. Preserves flexibility for Discovery Agents used independently by other Harness modules.

I have to manage many projects and many things inside each of the workspaces. In order to open up multiple projects to check configurations across or to have on screen open to monitor while I do other admin work, I have to duplicate the tab and navigate around the UI via about 5 - 7 clicks to get to another area. If I was able to from the projects fly out menu (among other place), right click and open in a new tab, my job would be so much easier. I don't know why it needs to be high jacked or prescribed for me to not be able to open anything in the app in a new tab.

We are requesting support for the s390x architecture for both the Harness Delegate and the GitOps Agent. Currently, neither is available for s390x. Please add s390x as a supported architecture for Delegate and GitOps Agent deployments.

We would like to have Harness emit pipeline events directly to Dynatrace rather than having to handle the events ourselves via webhooks. This would allow the same Event emission to Dynatrace that Harness already supports for Datadog. e.g. https://www.harness.io/blog/harness-pipeline-notifications-for-datadog

Persist Ask AI widget position across modules, page refreshes, and re-logins

Scroll Option in the left navigation bar is not very intuitive and there is no scroll bar to tell that. Took me days to identify that it is not access issue and we need to scroll down to see rest of the options. Was trying to find project Settings which only appears when we scroll down.

Priority: P1 / High Module: Platform, Governance (Policy as Code), Delegates, RBAC Type: Feature request / product gap Account: jLOlhyHHQ0yh8snNBDPL0A ( paypal.harness.io ) Problem We publish certified account-level golden templates. App teams cherry-pick stages from them, rename them, inline the YAML, or skip templates entirely. Some even use a production connector or delegate inside a “pre-prod” stage. We let teams experiment freely in lower environments. Anything that promotes or deploys to higher or production environments must come from a certified template. Harness gives us no way to enforce this. Requirement Restrict specific connectors and delegates (our prod and higher-env ones) to: stages or pipelines built from approved templates (templateRef + versionLabel), or an allow-list of orgs, projects or pipelines, with a Warn mode first and an Error/Block mode after. Current gaps Connector OPA runs On Save only. Nothing fires when a connector is used. Delegates aren’t an OPA entity. There’s no hook w