Supported AI tools
Every AI tool Joring captures, and which part of Joring you need installed to capture it.
Which component you need depends on where the tool runs, so this table is worth checking before a rollout.
In the browser
The browser extension covers these. Nothing else is needed.
| Tool | |
|---|---|
| ChatGPT | Claude |
| Google Gemini | Microsoft Copilot |
| Perplexity | Grok |
| DeepSeek | Meta AI |
| Mistral | Amazon Nova |
| Manus | Reka |
| Rovo (Atlassian) | Kimi |
| Qwen |
In the terminal
These need the desktop agent. The browser extension cannot see them, which is the single most common gap in a rollout that only deployed the extension.
| Tool | How it is captured |
|---|---|
| Claude Code | Signed, source-scoped network capture |
| Codex | Signed, source-scoped network capture |
In desktop apps
These need the desktop app, which captures traffic from native applications.
| Tool | How it is captured |
|---|---|
| Claude Desktop | Signed, source-scoped network capture |
| Microsoft 365 Copilot and Teams | Signed, source-scoped network capture |
| Slack AI | Signed, source-scoped network capture |
Cowork is not currently supported by the desktop agent. Joring does not fall back to reading Cowork files.
Slack AI is not a Slack app
Joring reads Slack's AI assistant through the desktop app rather than by installing anything into your Slack workspace. There is no Slack app to approve, and Joring does not read channels or direct messages — only turns with the AI assistant.
Coverage in practice
Most organizations deploy the extension first because it covers the widest audience for the least effort, then add the desktop agent for native and terminal tools. If your engineers are the heaviest AI users and you only measure the browser, your adoption numbers will understate them badly.
NextRoll out to your teamDeploy the extension through MDM and add terminal coverage where it matters.