Everything an AI or a terminal does through GBrain is written down as it happens. Not a sample, not a summary: every action, refusals included, and every change to access.
Where to read the record
Activity, in Tools, is everything across your account, newest first, with the last week drawn over it: what your AIs and terminals did with your applications and in a workspace, and every change to what they can use. Press a bar to see that hour, or narrow the list by application, action, connection, outcome, or whether it came over MCP or the command line. The number over the list counts the actions in it, and the Tools overview gives the same number for the same week.
An AI’s or a terminal’s Activity tab is everything that one did, wherever it is plugged in.
An application’s Activity tab is everything that reached that one account, whichever AI or terminal asked.
A workspace’s Tools page has an Activity tab too: what your applications did in that workspace, and what an AI or a terminal of yours did there, with its memory and its schedules included. An action is listed under the workspace it happened in, so an AI that reaches two workspaces has a row in each for what it did in each.
Open any row for the action in full: what it was, which application it was on, which connection took it and when, how it went, and why it was allowed or refused. Under that is the request as GBrain recorded it. GBrain keeps the names of what was sent and never the contents, so a search is on the record as a search that was sent with a query, without the words searched for.
What a row tells you
The application it went through, so you can see which account answered when you have connected more than one. The action in plain language, not a function name. The connection that took it. The cost, where it was a metered lookup. And when: the day and the time, on your own clock.
An action that was refused is under the application it was aimed at, with why in the same line: “Refused: Gmail is off for Claude”. The line names the control that refused it, so a refused read of a workspace’s memory says “Refused: Memory is off for Claude”. A change to what a connection may do is one line that says what changed: “Gmail on Claude: Off to Read”, “Stripe removed from Claude”, “Claude deleted”. Connecting an application and disconnecting it are each a line too, and a disconnect names what it came off: “Stripe disconnected, which took it off Claude”. When a teammate’s AI uses an application you added to a workspace, the row is on both your records: yours says who used it, theirs says whose it was.
What to do with the record
Check a claim. An AI that says it sent something either has a row for it or does not.
Find the runaway. A job that loops shows as the same action repeating. That is usually what a limit caught before you noticed.
Decide what to turn down. An AI that has not done anything in a month probably does not need the access it has.
The log is yours and it is not editable. An AI can read its own history, which is how it answers “what did you already do today,” but it cannot remove a row from it. From a terminal, gbrainio activity ls reads the same rows.