Human Mode watches common AI entry points without a browser extension and without cloud telemetry. Detection is useful, not magical.
The native bridge checks known install paths and running process signatures.
macOS examples:
/Applications/{App}.app~/Applications/{App}.app- process executable paths containing
.app/Contents/MacOS
Installed means the app exists on disk. Running means a process matched a known signature.
CLI targets are matched from process names and command-line arguments. Known app helper processes are excluded where possible so an app bundle does not appear as a separate terminal agent.
Examples:
codexclaudegeminiaideropencode
Human Mode does not use a browser extension. It reads browser tab metadata only through supported OS/browser APIs.
macOS V1:
- Safari through AppleScript.
- Chrome, Edge, Brave, and Arc through AppleScript.
If the browser or OS denies access, Human Mode should show a permission state instead of pretending the site is not open.
Editor AI extensions are detected by scanning common extension directories. This can tell whether a tool such as Copilot, Cline, Roo Code, Continue, Tabnine, Codeium/Windsurf, Cody, Qodo, Supermaven, or Augment appears installed.
It does not prove that the extension is actively answering a prompt.
Local model tools are matched by app, command, or process signature.
Examples:
- Ollama
- LM Studio
- Jan
- GPT4All
- AnythingLLM
- Open WebUI
- llama.cpp
- LocalAI
- vLLM
Port-based detection may be added later, but it should be treated as a weak signal unless tied to a known process.
Human Mode separates detected-open time from active-use time.
Detected-open means a watched target is running or a watched web tab exists. Active-use means the matching app, browser, or terminal appears foreground while the user has recent input.
Without a browser extension, Human Mode cannot reliably know whether a user sent a message inside a web AI chat. Stats are therefore OS-level estimates.
These are intentionally not primary signals:
- IP matching.
- Route-table edits.
- CDN hostnames.
- DNS-over-HTTPS traffic.
Those approaches are brittle, invasive, or hard to explain safely.