Docs Activity

Your account · 01

Activity

Activity is your log of the tool calls AI clients make through your Suits, refused ones included: when each one ended, how it ended and how long it took. Tuxedo never stores a call's arguments or results.

What Activity records

Each time a client calls a tool through one of your Suits, Tuxedo writes one entry, even when it refuses the call. An entry holds:

  • when the call ended
  • the Suit, and the Connection whose tool it named, if the Suit had one by that name
  • the called name: the name the client called, cut to its first 160 characters, such as github__search_issues, and the tool's own name on the server
  • how it ended
  • how the client got in: OAuth, Bearer token or Signed URL
  • the client's name, cut to its first 100 characters: the name of the token it used, or, for OAuth, the name the app registered with. A signed URL carries no name.
  • how long the call took

Tuxedo never stores a call's arguments or results

Nor anything the server said. The part of Tuxedo that writes an entry is never given them, so it can't keep them.

Open Activity from the sidebar. On the Suits page, a Suit's menu has View activity, which opens Activity with only that Suit's calls.

What never reaches Activity

Tuxedo checks a request's credential and the rate limit before it looks at the call, and a request stopped there leaves no entry. Neither does anything other than a tool call:

  • a request with a missing or wrong credential, such as a revoked token, a signed URL from before you rotated it, or a credential for another access mode
  • a request over the rate limit of 120 a minute for each credential
  • connecting, and listing a Suit's tools

How a call can end

Every entry has one of these statuses, which the Status filter offers by the same names.

  • OK: the server answered without an error.
  • Error: the server answered with an error, or Tuxedo couldn't get an answer from it that it could pass on.
  • Refused: Tuxedo refused the call and didn't send it on. The log says why, as below.
  • Timed out: Tuxedo stopped waiting before the call could finish. It allows 10 seconds to connect to a server, and 55 seconds for the whole call.
  • Needs sign-in: the call couldn't be made with the Connection as it's set up. Its details offer the fix.
  • Weekly limit: your account had used its tool calls for the week, so Tuxedo didn't send the call on. The log shows it as Refused · weekly limit.

Free includes 2,000 tool calls a week. Plans and billing explains what counts and when the week starts again.

Why a call was refused

An entry doesn't record why Tuxedo refused a call, so the log works it out from the entry and the Suit as it is now:

  • Refused · no name: the client didn't name a tool.
  • Refused · unknown tool: none of the Suit's Connections had a tool by that name when the call was made.
  • Refused · tool off: the tool is switched off in the Suit. The log says so only while it's still off.
  • Refused: anything else. It has been switched on since, the Suit no longer has it, or the call's arguments weren't a JSON object.

Tools explains the switches.

Filters and range

Above the log are three filters: Suit, Connection and Status. Each filter's menu can drop that filter again, and Clear drops them all.

The range sets how far back the log looks: 1h or 24h on Free, and 1h, 24h, 2d or 7d on Pro. It starts at 24h, and stays as it is when you clear the filters.

The filters and the range are kept in the page's address, so you can bookmark a filtered view. A filter that doesn't name one of your own Suits or Connections is ignored.

When the page says “No matching activity”, it offers Clear filters when a filter is set and, when calls from earlier in your plan's longest range would match, Show the last 24 hours on Free or Show the last 7 days on Pro.

The figures

The four figures above the log count the calls that match your filters in the range, and each label names the range, as in “Calls · 24h”.

  • Calls: every entry, refused ones included.
  • Errors: calls whose status is Error, Timed out or Needs sign-in, with their share of all the calls.
  • Median: the middle duration of the calls.
  • Refused: calls whose status is Refused or Weekly limit, whatever the reason.

A Suit's overview counts errors differently

Its Errors · 24h counts every call that didn't end OK, so refusals and the weekly limit count as errors there. On Activity, Errors leaves them out, and Refused counts them.

Reading the log

The log lists the newest calls first, a page at a time, grouped by day: Today, Yesterday, then the date. Each day says how many of its calls match and, if any weren't OK, how many.

Each row shows:

  • an icon for how the call ended, and the time
  • the called name, or No name when the client sent none
  • underneath, the Suit, the Connection (if the name matched one) and the client, or how the client got in when it has no name, such as Signed URL
  • how the call ended, when it wasn't OK: errors in red, and sign-in, timeouts and the weekly limit in amber
  • how long the call took

A call whose Suit you've since deleted shows Deleted Suit, and one whose Connection you've since deleted shows Deleted Connection.

Live updates

While the page is open, it checks for new calls every 5 seconds and says “Live · updated” with the time it last did. Pause holds the list still while you read it, and says “Paused · updated” instead; Resume starts the updates again.

Times in your time zone

Activity shows times and days in your browser's time zone. Until your browser has said which zone it's in, times are in UTC.

Each day names its offset from UTC, such as UTC+08:00, and gives both offsets on a day the clocks change. Hover over a time to see its full date.

A call's details

Click a row to open its details. On a wide screen they open beside the log, and on a narrower one over it. The open call is in the page's address too, so its link opens it again, even when it's outside the range you're looking at. Only your own calls open.

The details show how the call ended and when, to the second, the called name, and everything the entry holds:

  • Suit
  • Connection, with its account when it has one
  • Client, or Not named
  • Via: OAuth, Bearer token or Signed URL
  • Server's name: the tool's own name on the server
  • Duration

At their foot they say: “Tuxedo never stores a call's arguments or results.”

Fixing a call

When a call didn't end OK, its details say what happened, and offer the fix when there is one. Below, Suit and Connection stand for the names of yours.

  • A tool that's off. The details say “This tool is off in Suit” and offer Switch on in Suit, which flips the same switch as the Suit's tools page, then says “Switched on in Suit”. It's offered only while the tool is still off: once it's on, the call reads plain Refused and there is nothing to switch. Open Suit's tools takes you to the switches.
  • Any other refusal. The details explain it, and link to the Suit's tools unless the call named nothing.
  • Needs sign-in. Reconnect Connection starts signing it in again or, for a Connection that doesn't sign in with OAuth, opens its page. When a Connection needs you says more.
  • Timed out and Error. Open Connection shows its status, and Refresh tools reloads its tools, as its own page does, and tells you how that went. Tuxedo doesn't keep what the server said, so the details can't show it.
  • Weekly limit. On Free, the details say when your tool calls reset and offer Upgrade to Pro. Once you're on Pro, they say your Suits have no weekly limit.

A fix that needs the call's Suit or Connection isn't offered once you've deleted it.

How long Activity is kept

Tuxedo keeps activity for 1 day on Free and 7 days on Pro, and a daily clean-up deletes older entries.

Deleting a Suit or a Connection keeps its calls in Activity, shown as Deleted Suit or Deleted Connection. Deleting your account deletes all your activity with it. Security and privacy covers what else Tuxedo keeps.