Skip to content
Agent Analytics

Connect to Instinct

Use Instinct to bring product and growth questions into the conversation where you already work. Agent Analytics provides the analytics data; Instinct runs the CLI, schedules the check, and delivers the brief.

This guide covers the shell-first CLI workflow. It requires an Instinct runtime that can run npx and retain its CLI configuration between tasks.

Prerequisites

Section titled “Prerequisites”
  • An Agent Analytics account and access to its Google or GitHub sign-in
  • Instinct access, with command execution and recurring tasks available in your runtime
  • A tracked project with real events for meaningful reports

If you still need instrumentation, follow First Project in 5 Minutes. Pageviews can verify that tracking works; signups, purchases, feature use, and other events tied to your goals make the daily report useful. Some analytics commands require Pro; your account’s usage limits apply.

Connect once with browser approval

Section titled “Connect once with browser approval”

Ask Instinct:

Connect to my Agent Analytics account using the official CLI pinned to 0.5.34. Start detached login, send me the approval URL, and wait for me to approve. Keep the saved login in persistent private storage so later scheduled tasks can use it. Do not ask me for an API key.

Instinct runs:

Terminal window
npx --yes @agent-analytics/cli@0.5.34 login --detached
  1. Open the approval URL Instinct sends you.
  2. Sign in with the Google or GitHub identity that owns your Agent Analytics projects and approve access.
  3. For this detached handoff, return the one-time finish code shown after approval to Instinct.
  4. Instinct completes the command printed by the CLI, using the original request ID and your code:
Terminal window
npx --yes @agent-analytics/cli@0.5.34 login --auth-request <request-id> --exchange-code <finish-code>

The CLI stores a renewable agent session. Keep credentials private; do not paste long-lived account API keys or saved tokens into chat. Later runs can reuse the session while it remains valid.

Verify access before scheduling

Section titled “Verify access before scheduling”
Terminal window
npx --yes @agent-analytics/cli@0.5.34 auth status
npx --yes @agent-analytics/cli@0.5.34 all-sites --period 7d
npx --yes @agent-analytics/cli@0.5.34 context get my-site

Replace my-site with your project. The all-sites command gives an account overview; inspect individual projects and their context before drawing conclusions. Check the current CLI reference for commands and plan requirements.

Ask for a daily brief

Section titled “Ask for a daily brief”

Copy this prompt and set the time and timezone you want:

Every day at 09:00 Asia/Jerusalem, read my Agent Analytics projects and send me a short report here. Confirm the schedule, timezone, delivery destination, and next run before calling it set up. Run one report now to verify it.


Read each project's goals, activation events, and relevant annotations. Use existing portfolio context only for related projects; do not group every site automatically or change stored goals.


Compare the last completed day with the previous day and the latest completed seven days with the previous seven. State the exact date ranges and data timezone. Use matching periods and definitions, separate bot traffic where supported, and show counts alongside percentages. Flag small samples, missing events, plan limits, and failed reads instead of guessing.


Summarize what changed, which goal it affects, and one follow-up question or experiment worth considering. If nothing meaningful changed, say so briefly. Do not change my product, tracking, experiments, or account settings as part of this reporting task.

Instinct owns this schedule; connecting Agent Analytics alone does not create a recurring job. Ask Instinct to confirm it saved the task and reused the login successfully.

all-sites --period 7d is an overview, not an exact completed-day comparison. For bounded comparisons, the CLI’s query command supports --from and --to ISO timestamps. Instinct should check the date-boundary behavior, use non-overlapping completed windows, and state any timezone limitations. Do not compare a partial current day against a full previous day.

Give the report context

Section titled “Give the report context”

Project context stores each project’s goals, activation events, event glossary, and meaningful change annotations. Ask Instinct to propose missing goals and get your confirmation before storing initial durable context. Read existing context first so an update preserves useful information.

Portfolio context describes a shared growth system for intentionally related projects. Membership and identity grouping are separate from those interpretation notes. Neither should replace a project’s own goals or activation definition. See Projects, surfaces, and portfolios and Project context.

A daily brief should distinguish observed changes from hypotheses. More feature events alone do not prove that returning users are more engaged or explain why signups fell.

Reconnect, stop, or troubleshoot

Section titled “Reconnect, stop, or troubleshoot”
  • No projects: check that the approved identity owns the expected account.
  • Login disappears between runs: use a private persistent directory through AGENT_ANALYTICS_CONFIG_DIR or --config-dir, consistently for login and every scheduled command. Do not put saved credentials in a shared repository.
  • Session expired or revoked: repeat detached login and browser approval. The CLI refreshes valid sessions automatically; a failed read can also be a network or usage-limit issue, so inspect the error first.
  • Stop reports: ask Instinct to cancel its recurring task and confirm cancellation.
  • Revoke access: revoke the session in Agent Analytics Dashboard Settings / Agent Sessions. Cancel the Instinct task too, to avoid repeated failed reads.
Section titled “Related”