LogForge plugin support

LogForge is a product of 17811365 Canada Incorporated.

Contact adan@logforge.dev for support or verified account/data deletion. Include your plugin version and username or connection identifier. Never send passwords, API keys, relay tokens or unredacted diagnostics.

The hosted plugin connects through OAuth at https://usage.logforge.dev/mcp. Manage linked instances at your LogForge account. The gateway account is separate from your Central administrator account. Username sign-in currently has no email password recovery; save your password securely.

Private instances connect using the bundled outbound HTTPS relay. No inbound workstation port is needed. Desktop setup supports Python 3.10+, local Docker telemetry and remote Linux Docker agents through authorized SSH. A web-only client can inspect linked data and guide an operator through setup. Docker, virtualization, privileges and network changes depend on the target system.

Explicitly share project directories before reading their reports remotely. The relay start command survives chat exit; it does not automatically install a reboot startup service. Relay credentials expire after 30 days and can be revoked immediately from the account page.

Privacy and data handling ยท Terms

Usage reporting controls

Local aggregate reporting is on by default in Codex 0.5.2, Claude 0.2.0 and Perplexity 0.5.2. To turn it off before first use, set LOGFORGE_USAGE_DISABLED=1, or use the installed package's reporting disable command for a persistent choice. The full package command is python scripts/logforge_usage.py disable. Diagnostics continue to work. See the payload, retention and deletion disclosure.

Optional hosted aggregate reporting

Hosted gateway reporting defaults on for authenticated requests and executed tool handlers. It records UTC day, server environment (production or development), a bounded configured client label or unknown, public tool name, and request/success/error counts. Analytics contain no account IDs, OAuth client IDs, prompts, tool arguments or results, source code, filenames, tags, credentials, or raw errors. Client labels come from configured authenticated OAuth registrations; discovery clientInfo is not used. These are operational counts, separate from local plugin reports and marketplace installation receipts.

Before your first hosted query, use the reporting checkbox on the authorization page, or sign in at your LogForge account and turn off Share hosted aggregate usage. The choice persists for that account across reconnections and releases. Preference storage identifies the account so its choice can be honored; account identity is excluded from aggregate counters. Turning off stops future optional collection; a request already in flight may finish. Existing merged aggregates cannot be associated with an individual account or removed per account. Daily aggregate counters are retained for 400 days. Counters use a bounded memory buffer and may lose unflushed counts on process termination. Required authentication, rate limits, and processing your requested queries continue. Local plugin reporting has its own separate controls.