Logfire StrawberryRead every record log entry, draft every sql query, approve in one pass
A companion works the 2 operations your Logfire account exposes. It can run a SQL query, and every one of those waits on an approval card showing the record log entry before it changes.
Open the record log entry. Check it against something else. Write the change. Move to the next one. That is the Logfire afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a record log entry until you approve it.
What it can do is exactly what Logfire exposes to an account you authorise and nothing beyond it: 2 operations, 1 read and 1 write. In practice that means it can run a SQL query, and work across the record log entries and sql queries.
The Logfire API stops at Logfire. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the record log entries or ask you for them?
1 of the 2 operations is a read.
Your account, not a guess at it: a companion can record log entry, and the full list below is the whole list, with nothing inferred from Logfire's documentation.
The record log entries are what most of this inventory is about, alongside the sql queries. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of Logfire admin becomes a queue you review.
- Record Log Entry
Can it change a record log entry without asking?
The one write operation there is waits for you.
A companion can run a SQL query, and each one is staged on an approval card first: you see the record log entry, the field and the new value before it lands in Logfire.
Nothing in Logfire is sent, changed or deleted on your behalf without that click, and a rejected card leaves the record log entry exactly as it was. The gate is the same one on every surface, described at security.
- Run SQL Query
Does the record log entry sweep have to be asked for every time?
Yes.
Saved as a routine, the Logfire record log entries pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the busywork, the Logfire record log entries sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents