> ## Documentation Index > Fetch the complete documentation index at: https://docs.cimento.ai/llms.txt > Use this file to discover all available pages before exploring further. # How the Agent Hub endpoint agent works > Components, data flow, scheduling, identity resolution, egress, fail-open behavior and code signing of the Cimento endpoint agent. The endpoint agent is two small signed binaries and a configuration profile. Neither binary runs as a resident daemon. ## Components | Component | Role | | - | - | | `cimento-telemetry-hook` | Invoked by the coding agent on each hook event. Projects the payload onto a fixed allowlist, mints an event ID and appends one line to the local buffer. Holds no network code. | | `cimento-telemetry-drain` | Runs on a schedule. Resolves the user's identity, posts the buffer to Cimento, and re-asserts the hook configuration for any agent present on the device. | | Configuration profile (macOS) or machine policy (Windows) | Carries your tenant identifier, the ingest URL, and the per-device user email your MDM substitutes. | ## Data flow Cursor, Claude Code or Codex invokes the hook with the event payload on stdin. The hook keeps only the allowlisted fields described in [What data is collected](/agent-hub/data-collected) and appends the result to `~/.cimento/telemetry.ndjson`. Every five minutes, and once at login, the scheduler starts the drain. On macOS this is the LaunchAgent `ai.cimento.telemetry.drain`; on Windows, a per-user scheduled task. The drain stamps each event with the user email from the MDM-managed source. The hook never writes identity, so a spoofed hook payload cannot attribute events to someone else. The drain POSTs to `https://api.cimento.ai/api/agent-hub/telemetry/events` in server-capped chunks. Delivery is at-least-once and the server de-duplicates on event ID. On a network error, proxy failure, 429 or 5xx it leaves the buffer in place and backs off until the next run. The buffer is plain newline-delimited JSON and is bounded at 100,000 events or 64 MB, oldest trimmed first, which is sized to ride out a multi-day outage without losing events. ## Identity resolution The drain resolves `user_email` in fixed order and never trusts the hook payload for it: 1. **MDM-managed value.** macOS: the forced managed preference `user_email` in the `ai.cimento.telemetry` domain, delivered by the configuration profile. Windows: the machine-policy registry value `HKLM\SOFTWARE\Policies\Cimento\telemetry\user_email`, or the signed-in user's UPN when no explicit value is set. 2. **Identity file** written by the installer: `/Library/Application Support/Cimento/identity.json` on macOS, `%PROGRAMDATA%\Cimento\identity.json` on Windows. 3. **Unattributed.** Events still ship, carrying the device serial in place of an email, and show in the dashboard as an unattributed device. ## Where the hook is registered | Agent | Location | Managed by policy? | | - | - | - | | Claude Code | macOS: `/Library/Application Support/ClaudeCode/managed-settings.json` and `managed-settings.d/10-cimento-telemetry.json`. Windows: the same two files under `%ProgramFiles%\ClaudeCode`. | Yes. Claude Code merges managed hooks with the user's own and does not let a user setting disable them. The user's `settings.json` is never written. | | Codex | macOS: `/etc/codex/config.toml`. Windows: the Codex managed configuration under `%ProgramData%`. | Yes. Codex treats hooks from the system layer as administrator-managed and trusted by policy. If no `/etc/codex/requirements.toml` exists, the package creates one that keeps hooks enabled and allows managed hooks only. | | Cursor | `~/.cursor/hooks.json` | No. Cursor has no managed layer, so the entry is per-user. The drain re-asserts it before every run. | If a managed location cannot be written, the installer falls back to the per-user file so the device still reports. ## Fail-open by design The hook always exits 0 and always returns an allow response to permission-style hooks, including on malformed input, an unwritable disk, or an internal error. It never blocks, slows or alters what the coding agent does. Setting the environment variable `CIMENTO_TELEMETRY_DISABLED=1` disables the hook, the drain and the reconcile. ## Updates and removal * **Updates.** On each release Cimento updates the package in place in your MDM, so devices upgrade through the same assignment without anyone re-uploading anything. * **Removal.** Clicking **Disconnect** on the integration runs an uninstall across the targeted devices and removes the objects Cimento created in your MDM before deleting the stored credential. ## Code signing * **macOS.** The `.pkg` is signed and notarized. * **Windows.** The hook, the drain and the install and uninstall scripts are Authenticode-signed through Azure Artifact Signing with an RFC 3161 timestamp. The signing certificate rotates daily, so do not pin its thumbprint. For WDAC or signature-based detection rules, pin the durable identity EKU `1.3.6.1.4.1.311.97.707736870.60106188.709977328.172420691`. ### Windows install details Binaries install to `C:\ProgramData\Cimento\bin`. The installer writes its log to `C:\ProgramData\Cimento\logs\install.log`, and the detection value Intune checks is the registry string `HKLM\SOFTWARE\Cimento\Telemetry\Version`. Installation needs an interactive user session because the scheduled task and Cursor's per-user hook configuration are created in that session; if Intune installs at the login screen the installer exits nonzero and Intune retries later.