chrome.exe

CI Agent Executable (ci-agent-exe)

CPU Usage
N/A
Memory
N/A
Location
N/A
Publisher
N/A

Memory Impact
Each active job reserves workspace and may spawn child processes; plan for 2-4 GB of RAM per parallel job on typical Windows/Linux runners, with headroom for artifact handling.
Cpu Recommendation
On busy runners, allocate 1-2 CPU cores per active job and cap total concurrent jobs to prevent saturation; monitor CPU churn during peak windows.

What is chrome.exe?

ci-agent-exe is the core executable used by the CI Agent on a build runner. It authenticates to the CI server, fetches queued jobs, and coordinates per-job worker processes. It manages workspace setup, artifact transfer, and telemetry, ensuring pipelines run in isolation and results are sent back to the server.

The process runs as a service/daemon, spawning child processes for each pipeline step, coordinating workspaces, and using TLS to communicate with the CI server for task retrieval and result submission.

Is ci-agent-exe Safe?

ci-agent-exe is the legitimate CI Agent binary commonly deployed on build runners by reputable CI vendors. On a properly provisioned machine, it runs as a service with restricted permissions, communicates with the CI server over encrypted channels, and performs only pipeline-related tasks such as job execution, artifact transfer, and log collection. If you observe unexpected prompts, unsigned executables, or activity outside normal CI behavior, stop the agent, verify the vendor and path, and perform a security review before proceeding.

Is ci-agent-exe a Virus?

Under normal conditions, ci-agent-exe is not a virus; it is a signed binary provided by your CI vendor to run pipelines. However, attackers can disguise malware as an agent. Always verify the publisher, path, and hash, and ensure the executable resides in the expected directory. If you notice unsigned files, anomalous network activity, or executable paths outside your standard CI folders, treat it as potential malware and investigate immediately.

How to Verify Legitimacy

  1. Check File Location: Verify the executable is located at C:\Program Files\CI Systems\ci-agent\ci-agent.exe (or the vendor's standard path). Do not rely on a random download location.
  2. Verify Digital Signature: Open file properties and confirm the signer is a trusted CI vendor (e.g., CI Systems LLC). Ensure the certificate chain is valid and not expired.
  3. Check File Hash: Compute the SHA-256 hash of the file and compare it to the vendor-provided value for ci-agent.exe.
  4. Scan for Malware: Run an up-to-date malware scan on the executable and its directory to detect any tampering or malicious variants.

Red Flags: Red flags include the binary being located in an unexpected folder, a mismatched or missing digital signature, a hash that does not match the vendor, or suspicious network activity from the agent without active CI jobs.

Why is it Running?

Reasons it's running:

Disabling ci-agent-exe on a runner

Common Problems

Common Causes & Solutions

Frequently Asked Questions

Related Processes