From 19f774eb53dec17c65ee9fda5f10a222a3b70e4f Mon Sep 17 00:00:00 2001 From: DannyBaanks Date: Wed, 2 Sep 2026 22:02:05 -0600 Subject: [PATCH 1/4] 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/4] 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 From 2ef09b8894a2a456e2287286d3dcdb082b18d798 Mon Sep 17 00:00:00 2001 From: DannyBaanks Date: Sat, 5 Sep 2026 04:22:32 -0600 Subject: [PATCH 3/4] docs(install): narrow first-time-user guidance to verified flow, add sync markers --- docs/install/CALL-E-installation-guide.md | 22 +++++++--------------- docs/install/cli.md | 4 ++++ docs/install/install-guide.md | 22 +++++++++------------- 3 files changed, 20 insertions(+), 28 deletions(-) diff --git a/docs/install/CALL-E-installation-guide.md b/docs/install/CALL-E-installation-guide.md index 23d46cc..3ec99df 100644 --- a/docs/install/CALL-E-installation-guide.md +++ b/docs/install/CALL-E-installation-guide.md @@ -61,21 +61,13 @@ env CALLE_SOURCE=skills_sh CALLE_INTEGRATION=skills_sh_skill CALLE_INTEGRATION_V ## 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. + + +`calle auth login` uses the same flow for new and existing accounts: it opens +the brokered dashboard sign-in, where **Continue with Google** registers a new +account or signs in an existing one, then returns you to the same session to +finish. Full first-time-user detail: install-guide.md → +[First-Time Users](./install-guide.md#first-time-users-create-the-account). ## Step 4 Verify diff --git a/docs/install/cli.md b/docs/install/cli.md index 62cd5b1..82185b6 100644 --- a/docs/install/cli.md +++ b/docs/install/cli.md @@ -28,6 +28,10 @@ The command opens the brokered login URL, polls until authorization completes, exchanges the authorized session, and stores the token in a private local cache. The token is never printed to stdout. +First time? On the sign-in page choose **Continue with Google** to register a +new account and return to the same session; details in +[install-guide.md](./install-guide.md#first-time-users-create-the-account). + For agent integrations that need to show the authorization link before continuing: diff --git a/docs/install/install-guide.md b/docs/install/install-guide.md index 0694ec7..3fec5f1 100644 --- a/docs/install/install-guide.md +++ b/docs/install/install-guide.md @@ -188,21 +188,17 @@ npm fallback. ### 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: +`calle auth login` uses the same flow for new and existing accounts: 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. +2. On the sign-in page choose **Continue with Google**. For a new Google + identity this registers the account; for an existing account it signs in. +3. The dashboard shows that it is preparing your workspace, then returns you + to the same sign-in session so `calle auth login` can finish. + +The Google sign-in route and the preserved broker session are confirmed on +the deployed dashboard. If any step fails, see +[Troubleshooting](./troubleshooting.md). ## Safety From 93a59c66ddbe13f1979c0c337860868cb4f6e18b Mon Sep 17 00:00:00 2001 From: DannyBaanks Date: Sun, 6 Sep 2026 09:24:27 -0600 Subject: [PATCH 4/4] docs(install): remove return-to-session claim from first-time-user notes --- docs/install/CALL-E-installation-guide.md | 6 +++--- docs/install/cli.md | 4 ++-- docs/install/install-guide.md | 8 ++++---- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/install/CALL-E-installation-guide.md b/docs/install/CALL-E-installation-guide.md index 3ec99df..4b0b4dc 100644 --- a/docs/install/CALL-E-installation-guide.md +++ b/docs/install/CALL-E-installation-guide.md @@ -61,12 +61,12 @@ env CALLE_SOURCE=skills_sh CALLE_INTEGRATION=skills_sh_skill CALLE_INTEGRATION_V ## Step 3.5 First-Time Users: Create The Account - + `calle auth login` uses the same flow for new and existing accounts: it opens the brokered dashboard sign-in, where **Continue with Google** registers a new -account or signs in an existing one, then returns you to the same session to -finish. Full first-time-user detail: install-guide.md → +account or signs in an existing one while preserving the broker/MCP return +parameters. Full first-time-user detail: [First-Time Users](./install-guide.md#first-time-users-create-the-account). ## Step 4 Verify diff --git a/docs/install/cli.md b/docs/install/cli.md index 82185b6..8026f96 100644 --- a/docs/install/cli.md +++ b/docs/install/cli.md @@ -29,8 +29,8 @@ exchanges the authorized session, and stores the token in a private local cache. The token is never printed to stdout. First time? On the sign-in page choose **Continue with Google** to register a -new account and return to the same session; details in -[install-guide.md](./install-guide.md#first-time-users-create-the-account). +new account; the Google flow preserves the broker/MCP return parameters. +Details: [install-guide.md](./install-guide.md#first-time-users-create-the-account). For agent integrations that need to show the authorization link before continuing: diff --git a/docs/install/install-guide.md b/docs/install/install-guide.md index 3fec5f1..ad168d0 100644 --- a/docs/install/install-guide.md +++ b/docs/install/install-guide.md @@ -193,11 +193,11 @@ npm fallback. 1. `calle auth login` opens the brokered dashboard sign-in. 2. On the sign-in page choose **Continue with Google**. For a new Google identity this registers the account; for an existing account it signs in. -3. The dashboard shows that it is preparing your workspace, then returns you - to the same sign-in session so `calle auth login` can finish. +3. The dashboard shows that it is preparing your workspace. The Google flow + preserves the broker/MCP return parameters from the sign-in. -The Google sign-in route and the preserved broker session are confirmed on -the deployed dashboard. If any step fails, see +The Google sign-in route and the preserved broker/MCP return parameters are +confirmed on the deployed dashboard. If any step fails, see [Troubleshooting](./troubleshooting.md). ## Safety