From 19f774eb53dec17c65ee9fda5f10a222a3b70e4f Mon Sep 17 00:00:00 2001 From: DannyBaanks Date: Wed, 2 Sep 2026 22:02:05 -0600 Subject: [PATCH 1/2] docs: clarify account provisioning requirement for first-time CLI auth --- docs/install/CALL-E-installation-guide.md | 11 +++++++++++ docs/install/install-guide.md | 11 +++++++++++ 2 files changed, 22 insertions(+) diff --git a/docs/install/CALL-E-installation-guide.md b/docs/install/CALL-E-installation-guide.md index 7fcd7e9..ea71d3c 100644 --- a/docs/install/CALL-E-installation-guide.md +++ b/docs/install/CALL-E-installation-guide.md @@ -59,6 +59,17 @@ After the user confirms authorization is complete, finish the pending login: env CALLE_SOURCE=skills_sh CALLE_INTEGRATION=skills_sh_skill CALLE_INTEGRATION_VERSION=0.1.0 calle auth login --no-browser-open ``` +## Step 3.5 New Users Need A Provisioned Account + +`calle auth login` authenticates an **existing** CALL-E account. The brokered +redirect currently lands on a dashboard login page that accepts only +Account/Password credentials and shows no visible signup path, so first-time +users without a provisioned account cannot complete onboarding from it. + +While a product-side account-provisioning route is being added, see +[#103](https://github.com/CALLE-AI/call-e-integrations/issues/103) for the +current status and supported new-user path. + ## Step 4 Verify ```bash diff --git a/docs/install/install-guide.md b/docs/install/install-guide.md index f1496ca..a341a2e 100644 --- a/docs/install/install-guide.md +++ b/docs/install/install-guide.md @@ -186,6 +186,17 @@ The Codex, Claude Code, Cursor plugin, OpenClaw, and skills.sh skills use the repository-local CLI when available, then a global `calle`, then the npm fallback. +### New Users Without A Provisioned Account + +`calle auth login` authenticates an **existing** CALL-E account. The brokered +redirect currently lands on a dashboard login page that accepts only +Account/Password credentials and shows no visible signup path, so first-time +users without a provisioned account cannot complete onboarding from it. + +While a product-side account-provisioning route is being added, see +[#103](https://github.com/CALLE-AI/call-e-integrations/issues/103) for the +current status and supported new-user path. + ## Safety CALL-E can place real outbound phone calls. Integrations must plan first, From 91d350e38f1fbe96f407babfa3e8ad718fecaadc Mon Sep 17 00:00:00 2001 From: DannyBaanks Date: Thu, 3 Sep 2026 22:28:31 -0600 Subject: [PATCH 2/2] docs(install): replace stale no-signup note with verified first-time Google flow per #103 maintainer update --- docs/install/CALL-E-installation-guide.md | 27 ++++++++++++++--------- docs/install/install-guide.md | 27 ++++++++++++++--------- 2 files changed, 34 insertions(+), 20 deletions(-) diff --git a/docs/install/CALL-E-installation-guide.md b/docs/install/CALL-E-installation-guide.md index ea71d3c..23d46cc 100644 --- a/docs/install/CALL-E-installation-guide.md +++ b/docs/install/CALL-E-installation-guide.md @@ -59,16 +59,23 @@ After the user confirms authorization is complete, finish the pending login: env CALLE_SOURCE=skills_sh CALLE_INTEGRATION=skills_sh_skill CALLE_INTEGRATION_VERSION=0.1.0 calle auth login --no-browser-open ``` -## Step 3.5 New Users Need A Provisioned Account - -`calle auth login` authenticates an **existing** CALL-E account. The brokered -redirect currently lands on a dashboard login page that accepts only -Account/Password credentials and shows no visible signup path, so first-time -users without a provisioned account cannot complete onboarding from it. - -While a product-side account-provisioning route is being added, see -[#103](https://github.com/CALLE-AI/call-e-integrations/issues/103) for the -current status and supported new-user path. +## Step 3.5 First-Time Users: Create The Account + +`calle auth login` authenticates the CALL-E account that the dashboard +provisions for you. The first-time-user path is: + +1. `calle auth login` opens the brokered dashboard sign-in. +2. On the sign-in page choose **Continue with Google** and complete Google + sign-in. +3. The dashboard provisions a workspace with the starter call entitlement. +4. The browser returns to the broker session; `calle auth login` completes + the token exchange. + +The earlier credential-only login page (without a signup path) is tracked in +[#103](https://github.com/CALLE-AI/call-e-integrations/issues/103). +The onboarding blocker is considered mitigated pending an anonymous-user +regression check; if you cannot complete step 2–4 with a fresh account, +reply there. ## Step 4 Verify diff --git a/docs/install/install-guide.md b/docs/install/install-guide.md index a341a2e..0694ec7 100644 --- a/docs/install/install-guide.md +++ b/docs/install/install-guide.md @@ -186,16 +186,23 @@ The Codex, Claude Code, Cursor plugin, OpenClaw, and skills.sh skills use the repository-local CLI when available, then a global `calle`, then the npm fallback. -### New Users Without A Provisioned Account - -`calle auth login` authenticates an **existing** CALL-E account. The brokered -redirect currently lands on a dashboard login page that accepts only -Account/Password credentials and shows no visible signup path, so first-time -users without a provisioned account cannot complete onboarding from it. - -While a product-side account-provisioning route is being added, see -[#103](https://github.com/CALLE-AI/call-e-integrations/issues/103) for the -current status and supported new-user path. +### First-Time Users: Create The Account + +`calle auth login` authenticates the CALL-E account that the dashboard +provisions for you. The first-time-user path is: + +1. `calle auth login` opens the brokered dashboard sign-in. +2. On the sign-in page choose **Continue with Google** and complete Google + sign-in. +3. The dashboard provisions a workspace with the starter call entitlement. +4. The browser returns to the broker session; `calle auth login` completes + the token exchange. + +The earlier credential-only login page (without a signup path) is tracked in +[#103](https://github.com/CALLE-AI/call-e-integrations/issues/103). +The onboarding blocker is considered mitigated pending an anonymous-user +regression check; if you cannot complete step 2–4 with a fresh account, +reply there. ## Safety