Add posthog logs for assistant

[elie222]

Summary by CodeRabbit

• New Features

  • Enhanced AI assistant interaction tracking now logs tool usage and process events, helping to provide a smoother and more reliable experience.

• Chores

  • Updated user account management to require valid, unique email addresses for improved data integrity and security.
  • Refined environment-specific suffix logic for the assistant email construction.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
inbox-zero	✅ Ready (Inspect)	Visit Preview	Feb 9, 2025 0:13am

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update modifies the data structure for user-related fields by replacing UserAIFields with UserEmailWithAI in various files. Changes include updated type declarations in both API and utility functions, enhanced database schema constraints to enforce non-null and unique requirements on user emails, and additional tracking functionality using posthogCaptureEvent with proper error handling. The modifications refine type usage and improve event logging and error management during tool calls.

Changes

File(s)	Change Summary
apps/web/app/api/google/webhook/types.ts apps/web/utils/categorize/senders/categorize.ts	Replaced UserAIFields with UserEmailWithAI in type declarations and removed deprecated import statements.
apps/web/utils/ai/assistant/process-user-request.ts	Replaced UserAIFields with UserEmailWithAI; added trackToolCall function and integrated multiple posthogCaptureEvent calls for logging start, tool calls, and completion events.
apps/web/prisma/migrations/20250209113928_non_null_email/migration.sql apps/web/prisma/schema.prisma	Updated database schema: set email as non-null and unique in User, and added a unique constraint on Account.userId.
apps/web/utils/posthog.ts	Enhanced posthogCaptureEvent with try-catch error handling and an early return if the NEXT_PUBLIC_POSTHOG_KEY is missing.
apps/web/utils/assistant/is-assistant-email.ts	Modified the logic for constructing ASSISTANT_SUFFIX to append -test only in the development environment.

Sequence Diagram(s)

sequenceDiagram
    participant User as User
    participant Assistant as ProcessUserRequest
    participant Tracker as TrackToolCall
    participant PostHog as PosthogCaptureEvent

    User->>Assistant: Submit request
    Assistant->>PostHog: Log start event ("process started")
    Assistant->>Tracker: Invoke trackToolCall(tool, userEmail)
    Tracker->>PostHog: Capture tool call event
    Note over Assistant: Processing various tool calls...
    Assistant->>PostHog: Log completion event ("process ended")

Loading

Possibly related PRs

• Refactor components to process tab (instead of test tab) #290: Involves updates to user-related data structures similar to the main PR.
• Persona onboarding for AI assistant #292: Related to the modifications of the UserAIFields type, which has been replaced by UserEmailWithAI.
• Allow AI to use Smart Categories and Webhook when creating rules #295: Features changes in categorizeSender function's parameter types, aligning with the main PR's focus on user data structure updates.

Poem

I'm a little rabbit on a code-filled spree,
Hopping through changes so wild and free.
With types renewed and logs in sight,
My whiskers twitch at this coding delight.
Carrots and code, in perfect harmony!
Hop, hop – the changes make me smile!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6f72b25 and ec16002.

📒 Files selected for processing (1)

• apps/web/utils/assistant/is-assistant-email.ts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.