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

Prompt

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?

Outcome
success
Cost
$38.0823
excludes embeddings
Latency
190.0 s
Query attempts
3
Rows returned
5
Tokens
4,496,428 / 33,077
in / out

Request

request_id
5a7ed0d9-45a8-4f02-81db-59884ddd1b05
When
2026-09-27 12:47
Tool
ask
User
gerty.bester@dext.com · Gerty Bester
Identity
google
Session
de953512-dbbe-4472-a744-34e140fddb60
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: All new Dext user signups counted as distinct User CRNs; the indexed topic has no signup SSO-provide, Completed months from Apr through Aug 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 signup_users AS (
  SELECT DISTINCT
    DATE_TRUNC('MONTH', omni_dbt__eds_calendar_day."DATE_DAY") AS "Signup Month",
    parent_users."USER_CRN" AS user_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"
  LEFT JOIN PROD."DEXT_ACCOUNT_USER_MEMBERSHIPS" AS parent_dext_account_user_memberships
    ON omni_dbt__eds_all_accounts."ACCOUNT_CRN" = parent_dext_account_user_memberships."ACCOUNT_CRN" AND omni_dbt__eds_calendar_day."DATE_DAY" >= parent_dext_account_user_memberships."VALID_FROM" AND omni_dbt__eds_calendar_day."DATE_DAY" <= parent_dext_account_user_memberships."VALID_TO"
  LEFT JOIN PROD."EDS_ALL_USERS" AS parent_users
    ON parent_dext_account_user_memberships."USER_CRN" = parent_users."USER_CRN" AND omni_dbt__eds_calendar_day."DATE_DAY" >= parent_users."VALID_FROM" AND omni_dbt__eds_calendar_day."DATE_DAY" <= parent_users."VALID_TO"
  WHERE omni_dbt__eds_calendar_day."DATE_DAY" >= '2026-04-01'
    AND omni_dbt__eds_calendar_day."DATE_DAY" < '2026-09-01'
    AND omni_dbt__eds_calendar_day."DATE_DAY" = DATE_TRUNC('MONTH', omni_dbt__eds_calendar_day."DATE_DAY" + INTERVAL '1 MONTH') - INTERVAL '1 DAY'
    AND DATE_TRUNC('MONTH', parent_users."USER_CREATED_AT") = DATE_TRUNC('MONTH', omni_dbt__eds_calendar_day."DATE_DAY")
    AND parent_users."USER_CREATED_AT" >= '2026-04-01'
    AND parent_users."USER_CREATED_AT" < '2026-09-01'
    AND parent_users."USER_CRN" IS NOT NULL
    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
)
SELECT
  "Signup Month" AS "Signup Month",
  COUNT(DISTINCT user_crn) AS "All New Signups"
FROM signup_users
GROUP BY "Signup Month"
ORDER BY "Signup Month"
LIMIT 100

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.