Mojule Docs
FAQ
Short answers for security reviews, admin rollout planning, and first-connection troubleshooting.
Common questions
Does Mojule install anything on our machines?
No. Mojule consumes Anthropic's first-party OpenTelemetry. An Organization Admin points Claude Code and Claude Cowork's built-in OTEL export at Mojule's collector with a bearer token. There is no connector, agent, MCP sidecar, or curl|sh installer.
Does Mojule capture prompts or completions?
No. By default Mojule receives usage metadata only: session timing, model, surface, token counts, cost, and tool names. Prompt text, completion text, file contents, and tool arguments are not collected — and the ingest rejects any payload that carries prompt or response content (HTTP 422).
Which Claude surfaces are tracked?
Claude Code (CLI, VS Code, Cursor) and Claude Cowork only. Claude Web, plain Desktop chat, and Claude mobile emit no OpenTelemetry and are never tracked.
We use API keys, Bedrock, or Vertex. Does identity still work?
Those auth modes don't attach an organization id. Add mojule.tenant_id to OTEL_RESOURCE_ATTRIBUTES (the value is on your dashboard Connect page) so events stay attributed to your org.
Telemetry isn't arriving — what should I check?
Confirm the bearer token matches the one issued on your dashboard, and that your egress allowlist permits ingest.mojule.cloud under Capabilities → Network egress. Restricted egress silently drops exports.
How do we stop sending telemetry?
Remove the OTLP config from the Cowork Monitoring panel and the Claude Code managed-settings.json, or rotate the ingest token from the dashboard to immediately invalidate the old one.
Support
For the step-by-step OTEL setup, see Connect OTEL.