Legacy account preview under review. Personal account expansion and billing are deferred. Use the public tools or review existing-user access.
Teams and incidents
Set project policies and share incident metadata. Personal prompts and full reports remain private to their author.
Loading account…
Your account ID: . Share this ID with an organization administrator to join their team.
Project service keys
Keys access only incident metadata in this project. They cannot run models or read private reports. A member’s keys are revoked when their role changes or they leave.
Copy this key into your secret manager now. It is shown once.
Incidents
Most recent 200 events shown; up to 1,000 retained per project for 30 days. Events contain identifiers and counts only. Never put sensitive text in tool names or event IDs.
Connect a local guard
Use the metadata exporter in the Loop-Guard release examples. Set an explicit HTTPS endpoint https://runlog.cc/api/teams/ingest and a project key with incidents:write. The exporter never sends prompts, tool arguments, or outputs. Read events with a read-scoped key at /api/teams/feed. Retry the identical event ID and body for idempotent ingestion.
To retest an incident, run a private comparison, then explicitly share its run ID below the incident. Only model names, check counts, and cost are shared; teammates cannot open the private report.