Idle Codex machine still paired

Last updated Oct 17, 2026 Preview Policies Sprawl & Lifecycle

AI summary

Rencore Governance detects developer machines not seen for 30 days that are still paired for remote control, helping you identify stale pairings that should be removed. Since these pairings are invisible to MDM, the ChatGPT inventory is where they appear.

Severity: Low Sprawl Preview

What it detects

Detects developer machines not seen for 30 days that are still paired for remote control.

Why it matters

A machine that has stopped checking in is either retired or forgotten, and in both cases the pairing should not survive. These endpoints are invisible to MDM in this context, so the ChatGPT inventory is the only place the stale pairing shows up at all.

The rule

Every ChatGPT Codex Machine where Last Seen is more than 30 days ago

In Rencore Governance

Details

Applies to	ChatGPT Codex machine
Connector	ChatGPT Enterprise
Severity	Low
Category	Sprawl
Recommended	No
Recommended automation	None
License type	Standard

Frequently asked questions

What does the idle Codex machine still paired policy detect?

The Idle Codex machine still paired policy detects developer machines not seen for 30 days that are still paired for remote control.

Which objects does the idle Codex machine still paired policy check?

The Idle Codex machine still paired policy checks ChatGPT Codex machine objects from the ChatGPT Enterprise inventory and reports each one that matches its rule as a violation.

How severe is a violation of the idle Codex machine still paired policy?

Violations of the Idle Codex machine still paired policy have Low severity. The policy is in the Sprawl category.

Which module includes the idle Codex machine still paired policy?

The Idle Codex machine still paired policy comes with the ChatGPT Enterprise connector (in preview) in the AI & Agents module of Rencore Governance, an add-on module on the Premium and Enterprise Plans.

Was this page helpful?