What gets recorded

NibWP writes down every MCP tool call it runs, so "what did the assistant actually do" is a question with an answer. You will find it under NibWP → Audit Log.

What a row contains

• The timestamp, in your site's own timezone and date format.
• The tool that was called, and whether it ended in success or error.
• How long it took, in milliseconds.
• The WordPress account the call arrived as. On an OAuth connection the connected client is named alongside it; application passwords carry no client identity, so that stays empty.
• The IP address the request came from.

The arguments the call was given are stored with the row as well. Keep that in mind when you share a log: whatever was passed is in there, file contents and PHP source included.

Retention

Logging is on by default and entries are kept for 30 days. Both are in NibWP → Settings under Audit Log, and a daily cleanup removes anything older. The log screen also has a Clear entries older than box for doing it now.

When something unexpected happened

1. Set the status filter to Error and read from the top. The four counters — total calls, today's calls, error rate, most used tool — usually tell you whether it was one bad call or a pattern.
2. Type part of a tool name into the filter box to follow a single tool.
3. Ask your assistant instead. The nibwp/read-audit-log ability returns entries oldest first with the arguments each call was given, which is the order things actually happened in.

Full guide: How to: read the Audit Log