@clue-ai/cli 0.0.10 → 0.0.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@clue-ai/cli",
3
- "version": "0.0.10",
3
+ "version": "0.0.11",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "clue-ai": "bin/clue-cli.mjs"
@@ -567,7 +567,7 @@ const buildLifecyclePrompt = ({ request, files }) =>
567
567
  "Do not send raw email, raw person names, tokens, workspace names, organization names, or tenant names as lifecycle traits unless the repository already has an explicit Clue privacy policy allowing them.",
568
568
  "Prefer stable ids and non-PII booleans/counts for ClueIdentify and ClueSetAccount traits.",
569
569
  "Use environment variable names for Clue configuration values.",
570
- "For Python/FastAPI code, read CLUE_PROJECT_KEY, CLUE_ENVIRONMENT, CLUE_API_KEY, and CLUE_INGEST_ENDPOINT from environment variables.",
570
+ "For Python/FastAPI code, read CLUE_PROJECT_KEY, CLUE_ENVIRONMENT, CLUE_API_KEY, CLUE_API_BASE_URL, and CLUE_INGEST_ENDPOINT from environment variables.",
571
571
  "For browser code, read CLUE_PROJECT_KEY, CLUE_ENVIRONMENT, CLUE_SERVICE_KEY, and CLUE_INGEST_ENDPOINT from environment variables through the target framework's safe client config mechanism. Do not hard-code a Next.js-only prefix.",
572
572
  "Never place CLUE_API_KEY in frontend code, frontend env files, browser bundles, or client-readable config.",
573
573
  "When browser SDK ingest is configured, implement a backend-owned browser token endpoint that reads server-side CLUE_API_KEY and requests POST /api/v1/ingest/browser-tokens from Clue.",
@@ -173,6 +173,9 @@ const buildServiceEnvBlock = ({ target, setupContext }) => {
173
173
  name: "CLUE_INGEST_ENDPOINT",
174
174
  value: buildEndpoint(setupContext.clue_api_base_url, ingestPath),
175
175
  },
176
+ ...(target.kind === "backend"
177
+ ? [{ name: "CLUE_API_BASE_URL", value: setupContext.clue_api_base_url }]
178
+ : []),
176
179
  { name: "CLUE_PROJECT_KEY", value: setupContext.project_key },
177
180
  { name: "CLUE_ENVIRONMENT", value: setupContext.environment },
178
181
  { name: "CLUE_SERVICE_KEY", value: target.service_key },
@@ -271,7 +271,7 @@ const skillBody = (name) => {
271
271
  "When browser SDK ingest is configured, implement a backend-owned browser token endpoint that reads server-side `CLUE_API_KEY` and requests `POST /api/v1/ingest/browser-tokens` from Clue.",
272
272
  "Configure frontend `ClueInit` with `browserTokenProvider` that calls the local backend token endpoint and returns the token string.",
273
273
  "The browser token request must include project key, environment, service key, and the current browser origin; the backend must attach `x-clue-api-key` server-side when calling Clue.",
274
- "For FastAPI code, add `clue-fastapi-sdk` to the backend dependency file when missing, import `clue_init_fastapi` plus `ClueIdentify`, `ClueSetAccount`, and `ClueLogout` where needed, and use `CLUE_PROJECT_KEY`, `CLUE_ENVIRONMENT`, `CLUE_API_KEY`, and `CLUE_INGEST_ENDPOINT`.",
274
+ "For FastAPI code, add `clue-fastapi-sdk` to the backend dependency file when missing, import `clue_init_fastapi` plus `ClueIdentify`, `ClueSetAccount`, and `ClueLogout` where needed, and use `CLUE_PROJECT_KEY`, `CLUE_ENVIRONMENT`, `CLUE_API_KEY`, `CLUE_API_BASE_URL`, and `CLUE_INGEST_ENDPOINT`.",
275
275
  "Use `CLUE_SERVICE_KEY` as the canonical local service identifier. Do not ask the user to manage a separate producer id; SDKs should send producer id as the service key for setup verification compatibility.",
276
276
  "For frontend code, pass `serviceKey` from `CLUE_SERVICE_KEY` to `ClueInit`. Do not require a separate producer id unless the repository already has one for compatibility.",
277
277
  "For Django code, use `clue-django-sdk` only after package-manager or registry verification confirms it is installable; if it is not published or cannot be verified, report a blocker instead of adding a guessed dependency or import.",