Skip to content
CortexDocs
Defender · App connections

Manage app connections

Connect an app, inspect its health, and recover changed settings from Defender Home.

App connections
  • HomeFind connected and available apps
  • App healthCheck configuration and recent activity
  • RecoveryReview settings before reconnecting

Use Home to manage the AI apps on this device. Connected contains configured connections; Available contains apps that can be connected or need attention. A connected app is not proof that a new test reached Atlas.

Find and connect an app

  1. Open Home. Connected groups apps by connection state; By surface groups them by capture surface.
  2. If the app appears under Available, select its Connect action when offered.
  3. Otherwise select Add connection, choose the app, and read its details.
  4. For a coding agent or desktop app, use View connection when offered. If the app has not been detected, follow the detection or installation instruction first.
  5. Complete the app's connection action, review any proposed configuration changes, and follow its restart instructions. Start a new session when requested and send a test prompt.

Web catalog entries describe supported sites. Configure them through Browser sync and the intended web app on Home. Model-provider entries describe coverage; connect a supported app that uses that provider. These entries do not themselves offer a provider connection action.

Connected and available apps in HomeManage devices in Cortex
Add an app connection from HomeManage devices in Cortex

The catalog can list an app whose installation has not been detected. Follow its detection or installation instruction; appearing in the catalog does not establish coverage. Use Supported AI tools to check the supported platform and capture surface.

Check connection health

Open the app on Home and select Check health. Review Sync status and the individual Health checks.

App sync status and connection healthManage devices in Cortex
ResultWhat to do
Connected or SyncingRun a fresh test and find the matching activity in Atlas.
Not connected or OffConnect or enable the intended app.
Needs attention or a failed checkFollow the action beside the failed check, then check again.
Checking, Not checked, or unavailableWait or retry. This is not a passing result.

Local activity and configuration checks answer different questions. Synced activity in a local app check identifies activity observed on the device; use Verify capture and sync to confirm delivery to the expected person in Atlas.

Recover changed settings

If a connection reports that its settings changed after setup, open it and review the failed Connection check. Select Review settings when offered. Keep intended configuration edits and correct unintended changes before reconnecting or checking again.

Review an app connection that needs attentionManage devices in Cortex

A successful reconnect does not prove a new capture. Restart the affected session when requested and repeat the test. If recovery fails, use Troubleshooting.

Turn off a connection

For a managed app connection, open its details and scroll to Danger zone. Select Disconnect when offered, review which settings or hooks change, confirm, and restart the app or session as instructed. History and web sources have their own controls; follow the action shown. Other apps keep their independent settings. To stop the device, follow Pause and stop capture.

Disconnect a managed app through its Danger zoneManage devices in Cortex
Was this helpful?