Chandler usage · question

Prompt

Percentage of Solo items with AI Assist guidance applied, last 90 days

Outcome

success

Cost

$25.3795

excludes embeddings

Latency

119.1 s

Query attempts

Rows returned

Tokens

3,051,576 / 13,371

in / out

Request

request_id: 2d90d406-a063-42a6-a1d6-c3416698cf12
When: 2026-09-29 10:45
Tool: ask
User: gerty.bester@dext.com · Gerty Bester
Identity: google
Session: 1a1c71b9-6cb4-41fd-81f0-42e16996bc9a
Model: gpt-5.6-sol

Route taken

Topic

Product Usage - Accounts

Omni model

e407bba6-4fae-4079-ac4e-cd6cf8fdf6f8

Match method

agent loop

Nudge shown

—

Question shape

lookup

Caveat raised

degenerate_column

Sharper question offered

—

Shown to user

Basis: Solo items with AI Assist suggestions applied divided by all Solo items; the item-activity fields ar, Last 90 days, 2 Jul-29 Sep 2026. Governed filters applied.
Every row's «Percentage With AI Assist Applied» came back empty. That is usually a wrong field or join rather than missing data.

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

SELECT
  MIN(omni_dbt__eds_calendar_day."DATE_DAY") AS "First Date",
  MAX(omni_dbt__eds_calendar_day."DATE_DAY") AS "Last Date",
  COUNT(DISTINCT omni_dbt__eds_calendar_day."DATE_DAY") AS "Days Covered",
  COUNT(DISTINCT omni_dbt__eds_all_accounts."DERIVED_ACCOUNT_ID") AS "Distinct Solo Accounts",
  CAST(NULL AS NUMBER) AS "Solo Items",
  CAST(NULL AS NUMBER) AS "Solo Items With AI Assist Applied",
  CAST(NULL AS NUMBER(18, 6)) AS "Percentage With AI Assist Applied"
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."DATE_DAY" >= '2026-07-02'
  AND omni_dbt__eds_calendar_day."DATE_DAY" <= '2026-09-29'
  AND omni_dbt__eds_all_accounts."IS_SOLO" = 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'
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.