Reply Tracker

.cursorrules

@@ -208,4 +208,13 @@ export const POST = withError(async (request: Request) => {
 
   return NextResponse.json(result);
 });
-```
+```
+
+## Utility Functions
+
+- Use lodash utilities for common operations (arrays, objects, strings)
+- Import specific lodash functions to minimize bundle size:
+  ```ts
+  import groupBy from "lodash/groupBy";
+  ```
+- Create utility functions in `utils/` folder for reusable logic

ARCHITECTURE.md

@@ -160,6 +160,32 @@ The project extensively uses environment variables for configuration. These vari
 - Admin email addresses.
 - Webhook URLs and API keys for internal communication.
 
-## Conclusion
+## Features
 
-Inbox Zero exhibits a well-structured and modular architecture, leveraging a monorepo approach and modern technologies like Next.js, Prisma, and serverless functions. The architecture is designed for scalability, maintainability, and extensibility, with clear separation of concerns between the frontend, backend, and supporting services. The use of queues and background processing ensures efficient handling of asynchronous tasks like AI processing and email actions. The extensive use of environment variables promotes configuration flexibility and security. This architecture is well-suited for a complex SaaS application like Inbox Zero, providing a solid foundation for future development and feature enhancements.
+### AI Personal Assistant
+
+The user can set a prompt file which gets converted to individual rules in our database.
+What is ultimately passed to the LLM is the database rules and not the prompt file.
+We have a two way sync system between the db rules and the prompt file. This is messy, and maybe it would be better to just have one-way data flow via the prompt file.
+
+The benefit to having database rules:
+
+- In most cases, the AI is only deciding if conditions are matched.
+- We have specific entries for each rule, so we can track how often each is called. If it were fully prompt based this wouldn't be possible. This is a potentially minor benefit to the user however.
+- Because actions are static (unless using templates), the user can precisely define how the actions work without any LLM interference.
+
+The current structure of the AI personal assistant is due to the product evolving. Had it been designed from scratch it would likely have been structured a little differently to avoid the two-way sync issues. This architecture may be changed in the future.
+
+Another downside of not using the prompt file as the source of truth for the LLM is that some information included in the prompt file will not be passed to the LLM. Not something the user expects. For example, the user might write style guidelines at the top of the prompt file, but there's no natural way for this to be moved into the rules, as this information applies to all rules. We do have an `about` section that can be used for this on the `Settings` page, but this is separate.
+
+### Reply Tracking
+
+This feature is built off of the AI personal assistant.
+There's a special type of rule for reply tracking.
+I considered making it a separate feature similar to the cold email blocker. It makes things a little messy having this special type of rule, but the benefit is it integrates with the existing assistant and all the features built around that now.
+This means each user has their own reply tracking prompt (but this is also annoying, because it makes it hard for us to do a global update for all users for the prompt, which is something we can do for the cold email blocker prompt).
+
+### Cold email blocker
+
+The cold email blocker monitors for incoming emails, if the user has never sent us an email before we run it through an LLM to decide if it's a cold email or not.
+This feature is not connected to the AI personal assistant.

apps/web/__tests__/ai-choose-args.test.ts

@@ -163,12 +163,6 @@ function getAction(action: Partial<Action> = {}): Action {
     cc: null,
     bcc: null,
     url: null,
-    labelPrompt: null,
-    subjectPrompt: null,
-    contentPrompt: null,
-    toPrompt: null,
-    ccPrompt: null,
-    bccPrompt: null,
     ...action,
   };
 }
@@ -196,6 +190,7 @@ function getRule(
     categoryFilterType: null,
     conditionalOperator: LogicalOperator.AND,
     type: null,
+    trackReplies: null,
   };
 }
 

apps/web/__tests__/ai-choose-rule.test.ts

@@ -74,13 +74,6 @@ describe.skipIf(!isAiTest)("aiChooseRule", () => {
         cc: null,
         bcc: null,
         url: null,
-
-        labelPrompt: null,
-        subjectPrompt: null,
-        contentPrompt: null,
-        toPrompt: null,
-        ccPrompt: null,
-        bccPrompt: null,
       },
     ]);
 

apps/web/__tests__/ai-process-user-request.test.ts

@@ -451,6 +451,7 @@ function getRule(rule: Partial<RuleWithRelations>): RuleWithRelations {
     type: RuleType.AI,
     createdAt: new Date(),
     updatedAt: new Date(),
+    trackReplies: null,
     ...rule,
   };
 }

apps/web/app/(app)/cold-email-blocker/ColdEmailList.tsx

@@ -2,8 +2,6 @@
 
 import { useCallback, useState } from "react";
 import useSWR from "swr";
-import Link from "next/link";
-import { ExternalLinkIcon } from "lucide-react";
 import { useSession } from "next-auth/react";
 import { LoadingContent } from "@/components/LoadingContent";
 import type { ColdEmailsResponse } from "@/app/api/user/cold-email/route";
@@ -18,21 +16,16 @@ import {
 import { DateCell } from "@/app/(app)/automation/ExecutedRulesTable";
 import { TablePagination } from "@/components/TablePagination";
 import { AlertBasic } from "@/components/Alert";
-import { Avatar, AvatarFallback } from "@/components/ui/avatar";
-import { getGmailSearchUrl } from "@/utils/url";
 import { Button } from "@/components/ui/button";
 import { useSearchParams } from "next/navigation";
 import { markNotColdEmailAction } from "@/utils/actions/cold-email";
-import { SectionDescription } from "@/components/Typography";
 import { Checkbox } from "@/components/Checkbox";
 import { useToggleSelect } from "@/hooks/useToggleSelect";
 import { handleActionResult } from "@/utils/server-action";
 import { useUser } from "@/hooks/useUser";
 import { ViewEmailButton } from "@/components/ViewEmailButton";
-import {
-  EmailMessageCell,
-  EmailMessageCellWithData,
-} from "@/components/EmailMessageCell";
+import { EmailMessageCellWithData } from "@/components/EmailMessageCell";
+import { EnableFeatureCard } from "@/components/EnableFeatureCard";
 
 export function ColdEmailList() {
   const searchParams = useSearchParams();
@@ -213,16 +206,15 @@ function NoColdEmails() {
 
   if (!data?.coldEmailBlocker || data?.coldEmailBlocker === "DISABLED") {
     return (
-      <div className="mx-auto my-8 px-4 text-center">
-        <SectionDescription>
-          Cold email blocker is disabled. Enable it to start blocking cold
-          emails.
-        </SectionDescription>
-        <Button className="mt-4" asChild>
-          <Link href="/cold-email-blocker?tab=settings">
-            Enable Cold Email Blocker
-          </Link>
-        </Button>
+      <div className="mb-10">
+        <EnableFeatureCard
+          title="Cold Email Blocker"
+          description="Block unwanted cold emails automatically. Our AI identifies and filters out unsolicited sales emails before they reach your inbox."
+          imageSrc="https://illustrations.popsy.co/amber/calling-help.svg"
+          imageAlt="Cold email blocker"
+          buttonText="Set Up"
+          href="/cold-email-blocker?tab=settings"
+        />
       </div>
     );
   }

apps/web/app/(app)/cold-email-blocker/ColdEmailPromptForm.tsx

@@ -55,7 +55,7 @@ export function ColdEmailPromptForm(props: {
   );
 
   return (
-    <form onSubmit={handleSubmit(onSubmit)} className="mt-2">
+    <form onSubmit={handleSubmit(onSubmit)}>
       <Input
         type="text"
         autosizeTextarea

apps/web/app/(app)/cold-email-blocker/ColdEmailSettings.tsx

@@ -24,13 +24,13 @@ export function ColdEmailSettings() {
   return (
     <LoadingContent loading={isLoading} error={error}>
       {data && (
-        <>
+        <div className="space-y-10">
           <ColdEmailForm coldEmailBlocker={data.coldEmailBlocker} />
           <ColdEmailPromptForm
             coldEmailPrompt={data.coldEmailPrompt}
             onSuccess={mutate}
           />
-        </>
+        </div>
       )}
     </LoadingContent>
   );