Chandler · usage
← Back to sessions ← Back to this session

Prompt

How many AI Assist suggestions were applied in total up to today?

Outcome
success
Cost
$38.8849
excludes embeddings
Latency
139.3 s
Query attempts
1
Rows returned
1
Tokens
4,735,739 / 13,460
in / out

Request

request_id
79191143-3507-4340-a756-7881977854bb
When
2026-09-27 14:58
Tool
ask
User
gerty.bester@dext.com · Gerty Bester
Identity
google
Session
f00d6c66-f511-4150-9295-0cce7ff2a5f3
Model
gpt-5.6-sol

Route taken

Topic
Product Usage - Users
Omni model
e407bba6-4fae-4079-ac4e-cd6cf8fdf6f8
Match method
agent loop
Nudge shown
—
Question shape
lookup
Caveat raised
—
Sharper question offered
—
Shown to user
Basis: Total AI Assist suggestions applied across eligible Dext accounts, including user-selected and autom, All recorded history through 27 Sep 2026. Governed filters applied.

Per-step detail — each LLM call, each Omni request, each rejected draft — is traced to stdout only and is not stored, so it cannot be shown here. Query attempts counts run_query executions, not model turns.

SQL that ran

WITH activity_by_account AS (
  SELECT
    omni_dbt__eds_prepare_account_user_event_activity."ACCOUNT_CRN" AS account_crn,
    MIN(omni_dbt__eds_prepare_account_user_event_activity."OCCURRED_DATE") AS first_activity_date,
    MAX(omni_dbt__eds_prepare_account_user_event_activity."OCCURRED_DATE") AS last_activity_date,
    SUM(omni_dbt__eds_prepare_account_user_event_activity."SUGGESTION_APPLIED_VOLUME") AS suggestions_applied
  FROM PROD."EDS_PREPARE_ACCOUNT_USER_EVENT_ACTIVITY" AS omni_dbt__eds_prepare_account_user_event_activity
  WHERE omni_dbt__eds_prepare_account_user_event_activity."OCCURRED_DATE" <= CURRENT_DATE()
    AND omni_dbt__eds_prepare_account_user_event_activity."SUGGESTION_APPLIED_VOLUME" > 0
  GROUP BY omni_dbt__eds_prepare_account_user_event_activity."ACCOUNT_CRN"
),
current_accounts AS (
  SELECT DISTINCT
    omni_dbt__eds_all_accounts."ACCOUNT_CRN" AS account_crn
  FROM PROD."EDS_ALL_ACCOUNTS" AS omni_dbt__eds_all_accounts
INNER JOIN PROD."EDS_CALENDAR_DAY" AS omni_dbt__eds_calendar_day
  ON omni_dbt__eds_calendar_day."DATE_DAY" >= omni_dbt__eds_all_accounts."VALID_FROM" AND omni_dbt__eds_calendar_day."DATE_DAY" <= omni_dbt__eds_all_accounts."VALID_TO"
  WHERE omni_dbt__eds_calendar_day."IS_LATEST_AVAILABLE_DATE" = TRUE
    AND (omni_dbt__eds_all_accounts."IS_DEXT_DEMO" = FALSE OR omni_dbt__eds_all_accounts."IS_DEXT_DEMO" IS NULL)
    AND omni_dbt__eds_all_accounts."IS_SUSPENDED_DEXT" = FALSE
    AND omni_dbt__eds_all_accounts."SALESFORCE_ACCOUNT_TYPE" <> 'Reseller'
    AND omni_dbt__eds_all_accounts."ACCOUNT_CRN" IS NOT NULL
)
SELECT
  MIN(activity_by_account.first_activity_date) AS "First AI Assist Suggestion Applied Date",
  MAX(activity_by_account.last_activity_date) AS "Latest AI Assist Suggestion Applied Date",
  COALESCE(SUM(activity_by_account.suggestions_applied), 0) AS "AI Assist Suggestions Applied"
FROM current_accounts
INNER JOIN activity_by_account
  ON current_accounts.account_crn = activity_by_account.account_crn
LIMIT 1

Feedback

No feedback linked to this request.

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.