Fixes you hand to your AI tool

Every finding on the Improvements page carries two things: a short recommendation in plain words, and one action button. The recommendation is the fix. It names the service, the field, or the metric, and it says what to change.

The workflow

1. Open Improvements and read a finding.
2. Copy the recommendation text.
3. Paste it into the AI coding tool that has your project open: Claude Code, Cursor, Codex, or Windsurf.
4. Let the agent change your logger, your instrumentation, or your collector config.
5. Loggerhead checks again on the next cycle. The finding clears when the telemetry changes.

The agent already has your source. Loggerhead has the evidence from the running app. The recommendation joins the two, so the agent edits the right file instead of guessing.

Let the agent read the finding itself

Your AI tool can call the MCP server and read the findings directly. Ask it to “check Loggerhead for telemetry problems and fix the top one”. Then you do not copy anything.

The action buttons

Action	What it does	Status
Create alert	Creates an alert rule for the service and the condition in the finding.	Works today
Add drop rule	Prepares a drop rule for the noisy line or the label.	Planned
Add sampling	Prepares a sampling rule for the low-signal logs.	Planned
Add redaction	Prepares a redaction rule for the sensitive field.	Planned
Add trace context	Shows where to attach the trace ID in your logger.	Guidance
Review	Opens the metric or the series so you can decide.	Guidance

Why a rule belongs in your project

Loggerhead does not change your app or your collector config. A drop, sample, or redact rule belongs on the branch that sends the data, or in your app’s logger. That file is in your repository, where your AI tool can edit it and where the change goes through review with the rest of your code.

Loopback data stays yours

No fix sends data anywhere. The recommendation is text on your Mac. You choose what to paste and where.