chore: release cli v0.5.25

Author: dannyshmueli

README.md

@@ -9,10 +9,10 @@ Analytics your AI agent can actually use — track, analyze, experiment, optimiz
 Try the seeded public demo without signing in:
 
 ```bash
-npx --yes @agent-analytics/cli@0.5.24 demo
-npx --yes @agent-analytics/cli@0.5.24 --demo projects
-npx --yes @agent-analytics/cli@0.5.24 --demo funnel agentanalytics-demo --steps "page_view,signup_started,signup"
-npx --yes @agent-analytics/cli@0.5.24 --demo experiments list agentanalytics-demo
+npx --yes @agent-analytics/cli@0.5.25 demo
+npx --yes @agent-analytics/cli@0.5.25 --demo projects
+npx --yes @agent-analytics/cli@0.5.25 --demo funnel agentanalytics-demo --steps "page_view,signup_started,signup"
+npx --yes @agent-analytics/cli@0.5.25 --demo experiments list agentanalytics-demo
 ```
 
 Demo mode fetches a short-lived read-only `aas_*` session from the hosted API. It does not expose a raw `aak_*` API key, does not write local CLI config, and blocks mutating commands before making API requests.
@@ -21,19 +21,19 @@ Get the fastest path to useful analytics before installing events:
 
 ```bash
 # 1. Preview what your agent should track first
-npx --yes @agent-analytics/cli@0.5.24 scan https://mysite.com --json
+npx --yes @agent-analytics/cli@0.5.25 scan https://mysite.com --json
 
 # 2. Sign in when you want the full instrumentation plan
-npx --yes @agent-analytics/cli@0.5.24 login
+npx --yes @agent-analytics/cli@0.5.25 login
 
 # 3. Create or identify the project domain
-npx --yes @agent-analytics/cli@0.5.24 create my-site --domain https://mysite.com
+npx --yes @agent-analytics/cli@0.5.25 create my-site --domain https://mysite.com
 
 # 4. Run the full signed-in analysis for that project domain
-npx --yes @agent-analytics/cli@0.5.24 scan https://mysite.com --full --project my-site --json
+npx --yes @agent-analytics/cli@0.5.25 scan https://mysite.com --full --project my-site --json
 
 # Or resume and upgrade the anonymous analysis after login
-npx --yes @agent-analytics/cli@0.5.24 scan \
+npx --yes @agent-analytics/cli@0.5.25 scan \
   --resume <analysis_id> \
   --resume-token <resume_token> \
   --full \
@@ -45,19 +45,19 @@ Anonymous `scan` returns a one-analysis `rst_*` resume token, not an `aas_*` age
 
 ```bash
 # 1. Start agent login or signup in the browser
-npx --yes @agent-analytics/cli@0.5.24 login
+npx --yes @agent-analytics/cli@0.5.25 login
 
 # 2. Create a project
-npx --yes @agent-analytics/cli@0.5.24 create my-site --domain https://mysite.com
+npx --yes @agent-analytics/cli@0.5.25 create my-site --domain https://mysite.com
 
 # 3. Watch it live
-npx --yes @agent-analytics/cli@0.5.24 live
+npx --yes @agent-analytics/cli@0.5.25 live
 
 # Optional detached login for remote or issue-based agent work
-npx --yes @agent-analytics/cli@0.5.24 login --detached
+npx --yes @agent-analytics/cli@0.5.25 login --detached
 
 # Optional: clear your saved local auth later
-npx --yes @agent-analytics/cli@0.5.24 logout
+npx --yes @agent-analytics/cli@0.5.25 logout
 ```
 
 ## Commands
@@ -134,17 +134,17 @@ The CLI is agent-session-first. It stores a renewable Agent Analytics session lo
 When a free account hits a Pro-only analytics task, run an explicit upgrade handoff:
 
 ```bash
-npx --yes @agent-analytics/cli@0.5.24 upgrade-link --detached \
+npx --yes @agent-analytics/cli@0.5.25 upgrade-link --detached \
   --reason "Need funnel and retention reads for this analysis" \
-  --command "npx --yes @agent-analytics/cli@0.5.24 funnel my-site --steps page_view,signup,purchase"
+  --command "npx --yes @agent-analytics/cli@0.5.25 funnel my-site --steps page_view,signup,purchase"
 ```
 
 The CLI prints an `app.agentanalytics.sh` link. The human confirms the logged-in dashboard account, pays in Lemon Squeezy, and returns to the agent after Pro activates. Use `upgrade-link --wait` when the local shell should keep polling for activation.
 
 Project management commands accept exact project names or project IDs. For local browser QA, update origins through the CLI while keeping the production origin:
 
 ```bash
-npx --yes @agent-analytics/cli@0.5.24 update stylio --origins 'https://stylio.app,http://lvh.me:3101'
+npx --yes @agent-analytics/cli@0.5.25 update stylio --origins 'https://stylio.app,http://lvh.me:3101'
 ```
 
 Use `scan` before tracker installation when you want judgment instead of generic event lists. The preview is intentionally small: prioritized minimum viable instrumentation, what each event unlocks, current blind spots, and what not to track yet. The stable JSON is designed for agent skills to install only the high-priority events first and verify the first useful recommended event.
@@ -157,13 +157,13 @@ Bounce metrics (`insights`, `pages`, `sessions`) treat a session as a bounce whe
 `query` keeps `/events` raw and lossless, but `/query` uses activation-safe dedupe (`session_then_user`) as the default for `event_count`: session-backed rows count by session, no-session rows fall back to `user_id` only when that user has no session-backed row in the same filtered/grouped result set, and fully anonymous rows fall back to event `id`. For recent signup or ingestion debugging, check `events <project> --event <actual_event_name>` first, then use `query` after verifying the raw event names the project emits. `--count-mode` only affects `event_count`. Use `--count-mode raw` when you need the old ingested-row count for debugging or audit work:
 
 ```bash
-npx --yes @agent-analytics/cli@0.5.24 query my-site --metrics event_count --count-mode raw
+npx --yes @agent-analytics/cli@0.5.25 query my-site --metrics event_count --count-mode raw
 ```
 
 Property filters must use canonical `properties.*` fields. Built-in filter fields are only `event`, `user_id`, `date`, `country`, `session_id`, and `timestamp`. Example:
 
 ```bash
-npx --yes @agent-analytics/cli@0.5.24 query my-site --filter '[{"field":"properties.referrer","op":"contains","value":"clawflows.com"}]'
+npx --yes @agent-analytics/cli@0.5.25 query my-site --filter '[{"field":"properties.referrer","op":"contains","value":"clawflows.com"}]'
 ```
 
 Invalid filter fields now fail loudly and return property discovery guidance instead of being silently ignored.
@@ -177,9 +177,9 @@ Use annotations for major product changes that could explain later graph movemen
 Before setting or refreshing the glossary, inspect the project's current event names:
 
 ```bash
-npx --yes @agent-analytics/cli@0.5.24 properties my-site
-npx --yes @agent-analytics/cli@0.5.24 properties-received my-site
-npx --yes @agent-analytics/cli@0.5.24 context set my-site --json '{
+npx --yes @agent-analytics/cli@0.5.25 properties my-site
+npx --yes @agent-analytics/cli@0.5.25 properties-received my-site
+npx --yes @agent-analytics/cli@0.5.25 context set my-site --json '{
   "goals": ["Increase activated Agent Analytics accounts"],
   "activation_events": ["signup_completed", "project_created", "first_event_received"],
   "glossary": [
@@ -204,7 +204,7 @@ npx --yes @agent-analytics/cli@0.5.24 context set my-site --json '{
 Use the CLI feedback command when Agent Analytics was confusing, a task took too long, or the agent had to do manual analysis that the product should have handled:
 
 ```bash
-npx --yes @agent-analytics/cli@0.5.24 feedback \
+npx --yes @agent-analytics/cli@0.5.25 feedback \
   --message "The agent had to calculate the funnel drop-off manually" \
   --project my-site \
   --command "agent-analytics funnel my-site --steps page_view,signup,purchase" \
@@ -221,24 +221,24 @@ Claude Code, OpenClaw, Cursor, Codex — any AI agent that can run `npx`. Or add
 claude mcp add agent-analytics --transport http https://mcp.agentanalytics.sh/mcp
 ```
 
-For managed, issue-based, or remote runtimes that cannot receive a localhost callback or keep a long-running process alive, use `npx --yes @agent-analytics/cli@0.5.24 login --detached`. It prints the approval URL and exits. After browser approval, resume with the printed `login --auth-request <id> --exchange-code <code>` command.
+For managed, issue-based, or remote runtimes that cannot receive a localhost callback or keep a long-running process alive, use `npx --yes @agent-analytics/cli@0.5.25 login --detached`. It prints the approval URL and exits. After browser approval, resume with the printed `login --auth-request <id> --exchange-code <code>` command.
 
 For managed runtimes where the default home config path may not persist, point auth storage at a persistent runtime/workspace directory:
 
 ```bash
 export AGENT_ANALYTICS_CONFIG_DIR="$PWD/.openclaw/agent-analytics"
-npx --yes @agent-analytics/cli@0.5.24 login --detached
-npx --yes @agent-analytics/cli@0.5.24 auth status
+npx --yes @agent-analytics/cli@0.5.25 login --detached
+npx --yes @agent-analytics/cli@0.5.25 auth status
 ```
 
 For one-off commands, use `--config-dir "$PWD/.openclaw/agent-analytics"` before or after the command. The CLI stores the same `config.json` file in that directory and does not migrate credentials from the default path.
 
-For a local shell where it is useful to keep waiting, use `npx --yes @agent-analytics/cli@0.5.24 login --detached --wait`.
+For a local shell where it is useful to keep waiting, use `npx --yes @agent-analytics/cli@0.5.25 login --detached --wait`.
 
 If your saved session predates CLI `0.5.9`, run a fresh login before calling `projects`. Older saved agent-session tokens were minted without `projects:read`, so they will keep failing until you re-authenticate. Verify with:
 
 ```bash
-npx --yes @agent-analytics/cli@0.5.24 projects
+npx --yes @agent-analytics/cli@0.5.25 projects
 ```
 
 ## Agent Skill

bin/cli.mjs

@@ -249,7 +249,7 @@ function printUpgradeLinkHint(err) {
   warn('This needs Pro for the full agent analytics loop.');
   if (auth?.api_key) {
     log(`Upgrade links require browser-approved CLI login, not a raw API key.`);
-    log(`  ${CYAN}${cliInvocationWithConfig()} login --detached${RESET}`);
+    log(`  ${CYAN}${cliInvocationWithConfig()} login${RESET}`);
     return;
   }
   log(`Ask the human to approve payment with one explicit command:`);
@@ -293,7 +293,8 @@ function unauthenticatedWebsiteAnalysisCliMessage() {
   return [
     `Website analysis preview is only available anonymously on the web: ${websiteAnalysisWebPreviewUrl()}`,
     `In CLI, sign in first, then scan sites for projects you own or manage.`,
-    `Next step: npx @agent-analytics/cli login --detached`,
+    `Next step: npx @agent-analytics/cli login`,
+    `For Paperclip, OpenClaw, or issue-based runtimes, use: npx @agent-analytics/cli login --detached`,
   ].join('\n');
 }
 
@@ -481,10 +482,10 @@ async function cmdUpgradeLink({ detached, wait, reason, blockedCommand }) {
 
   const auth = getStoredAuth();
   if (!auth) {
-    error('Not logged in. Run: npx @agent-analytics/cli login --detached');
+    error('Not logged in. Run: npx @agent-analytics/cli login');
   }
   if (auth.api_key) {
-    error('upgrade-link requires browser-approved CLI login, not a raw API key. Run: npx @agent-analytics/cli login --detached');
+    error('upgrade-link requires browser-approved CLI login, not a raw API key. Run: npx @agent-analytics/cli login');
   }
 
   const api = createApiClient(auth);

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-analytics/cli",
-  "version": "0.5.24",
+  "version": "0.5.25",
   "description": "Stop juggling dashboards. Let your agent do it. Analytics your AI agent can actually use — track, analyze, experiment, optimize.",
   "bin": {
     "agent-analytics": "bin/cli.mjs"

test/cli.test.mjs

@@ -259,6 +259,7 @@ describe('CLI', () => {
 
         assert.notEqual(code, 0);
         assert.ok(stripAnsi(stdout).includes('requires browser-approved CLI login'));
+        assert.ok(stripAnsi(stdout).includes('Run: npx @agent-analytics/cli login'));
       } finally {
         config.cleanup();
       }
@@ -1534,6 +1535,8 @@ describe('CLI', () => {
         assert.match(plain, /Website analysis preview is only available anonymously on the web/i);
         assert.match(plain, /https:\/\/agentanalytics\.sh\/analysis\//i);
         assert.match(plain, /sign in first/i);
+        assert.match(plain, /Next step: npx @agent-analytics\/cli login/i);
+        assert.match(plain, /Paperclip, OpenClaw, or issue-based runtimes/i);
         assert.match(plain, /login --detached/i);
       } finally {
         await server.close();