Chandler · usage
← Back to sessions

Session

User
gerty.bester@dext.com · Gerty Bester
Started
2026-09-27 12:42
Last activity
2026-09-27 12:47
Questions
5
Grouping
time_gap — inferred — consecutive questions from this user with no long gap
session_id
de953512-dbbe-4472-a744-34e140fddb60

Transcript

  1. 2026-09-27 12:44 ask success $33.0406 120.5 s full detail →
    What is the total cumulative value of payments processed through Dext Payments to date (GBP, all currencies converted), how many accounts/businesses have made a payment, and how much was processed in the last 30 days?
    Data answer — see full detail.
    1 row Product Usage - Accounts
  2. 2026-09-27 12:46 ask success $25.7711 121.2 s full detail →
    How many MTD for Income Tax quarterly updates have been successfully submitted to HMRC through Dext Solo to date, and how many practices and income sources are connected to HMRC?
    Data answer — see full detail.
    1 row Product Usage - Accounts
  3. 2026-09-27 12:47 ask success $38.0823 190.0 s full detail →
    Since April 2026, how many new Dext user signups used Google SSO or Microsoft SSO, and what share of all new signups is that, by month?
    Data answer — see full detail.
    5 rows Product Usage - Users
  4. 2026-09-27 12:49 ask success $153.8385 316.6 s full detail →
    How many sales invoices were created (raised) in Dext's sales invoice creation feature in the last 12 months, split by country (UK vs France)?
    Data answer — see full detail.
    1 row Product Usage - Users
  5. 2026-09-27 12:51 ask success $134.9833 214.1 s full detail →
    Number of sales invoices created in Dext by UK Solo accounts in 2026 to date
    Data answer — see full detail.
    1 row Product Usage - Users

Cost is the LLM completion spend LiteLLM priced for each call, summed per request. Chandler is running on the Codex CLI, which draws ChatGPT plan quota rather than per-token API billing, so this figure is not money paid — it is what the same traffic would have cost on the API, priced from the token counts Codex reports. Read it as the size of the bill avoided. Two known limits: embedding spend is not recorded, so retrieval and matching cost is missing, and because the figure is one sum per request it cannot be split by model within a request — a request's classifier and agent calls can use different models while llm_model holds only one name. Only authenticated calls are logged, USAGE_LOG_ENABLED can switch logging off, and log writes are fail-soft — this is not a complete record of traffic. Questions are grouped into sessions: a session is exact when the caller echoed its id back to us and otherwise inferred from a 30-minute gap in that user’s activity, so a grouping is only as good as the source shown on the session itself. A call with no attributable user gets no session at all; those questions are listed separately rather than dropped.