agentmail 0.1.5 → 0.1.6

package/dist/llms-full.txt

@@ -171,7 +171,7 @@ This guide will walk you through installing the AgentMail SDK, authenticating wi
   <Step title="Create an API Key">
     Now that you're in the console, you'll need to create an API key to
     authenticate your requests. Navigate to the API Keys section in your console
-    dashboard. ![API Key Creation Screenshot](file:70efc386-e5f7-4897-a497-515e32142b26) Click
+    dashboard. ![API Key Creation Screenshot](file:f8c5320f-b15c-44e7-a569-670c5f1d2a88) Click
     "Create New API Key" and give it a descriptive name. Once created, copy the
     API key and store it securely. Create a `.env` file in your project's root
     directory and add your key to it. We recommend using environment variables to
@@ -312,7 +312,7 @@ Unlike traditional email providers that are designed for human scale, AgentMail
 
 As the diagram below illustrates, your `organization` is the top-level container that holds all your resources. You can provision many `Inboxes` within your `organization`, each with its own `Threads`, `Messages`, and `Attachments`, allowing you to manage a large fleet of agents seamlessly.
 
-<img src="file:2d3ffce3-a340-42d2-9a67-f0be52f7500d" alt="AgentMail Organizational Hierarchy" />
+<img src="file:ac426e5d-2c1a-40b1-bf52-5c97883187df" alt="AgentMail Organizational Hierarchy" />
 
 <Steps>
   <Step title="Organization">
@@ -732,7 +732,7 @@ Here is an example of a well-structured and styled HTML header:
 </CodeBlocks>
 
 <Frame caption="Look how pretty this message looks!">
-  <img src="file:42af328f-ce02-484c-a5b5-1566ac786ee2" alt="rendered css" />
+  <img src="file:3e435f8a-5583-4ddd-83a3-c3f87c5f3aac" alt="rendered css" />
 </Frame>
 
 ## Receiving `Messages`
@@ -1759,7 +1759,7 @@ Configuring your domain is a three-step process: add the domain via API, copy th
     After creating your domain in the AgentMail Console, click the "Download BIND Zone File" button to get the complete zone file.
 
     <Frame caption="Downloading BIND zone file from AgentMail Console">
-      <img src="file:b3ff2a02-c596-4554-be3d-1e54811dfa55" alt="Download BIND Zone File from Console" />
+      <img src="file:fdcf475d-78f0-49a1-aa38-5bd877368f56" alt="Download BIND Zone File from Console" />
     </Frame>
 
     <Tabs>
@@ -1770,13 +1770,13 @@ Configuring your domain is a three-step process: add the domain via API, copy th
         2. Click **"Import zone file"** in the top right corner
 
         <Frame caption="Importing BIND zone file in AWS Route 53">
-          <img src="file:e7101e7a-5590-4fe1-b1d4-733c24ec310f" alt="AWS Route 53 BIND Import" />
+          <img src="file:01476e8c-76ae-4414-b008-0547631c47f1" alt="AWS Route 53 BIND Import" />
         </Frame>
 
         3. Paste the CONTENTS of downloaded BIND zone file
 
         <Frame caption="Open the file with text editor and paste the contents. It should look similar to what we have in this image.">
-          <img src="file:fe2e9d0f-f350-479c-b634-5477599d3053" alt="AWS Route 53 BIND Import" />
+          <img src="file:86767929-19ef-4ded-b528-ed42ede218fe" alt="AWS Route 53 BIND Import" />
         </Frame>
 
         4. Review the records and click **"Import"**
@@ -1789,13 +1789,13 @@ Configuring your domain is a three-step process: add the domain via API, copy th
         2. Navigate to **DNS > Records**
 
         <Frame caption="This is what the page looks like">
-          <img src="file:b8cfed63-5fea-420f-ac7f-9731a80e840d" alt="Cloudflare BIND Import" />
+          <img src="file:1886368e-04ae-4bfe-a117-83246de25118" alt="Cloudflare BIND Import" />
         </Frame>
 
         3. Click **"Import and Export"**
 
         <Frame caption="You should be able to just drop the file in">
-          <img src="file:d8762904-358d-432e-99cf-4e4b4763fed5" alt="Cloudflare BIND Import" />
+          <img src="file:b966738e-c0e6-425d-86d1-0ce95b9a326d" alt="Cloudflare BIND Import" />
         </Frame>
 
         4. Upload the downloaded BIND zone file as is
@@ -1808,13 +1808,13 @@ Configuring your domain is a three-step process: add the domain via API, copy th
         2. Navigate to the **DNS** subtab of the domain you want to send from
 
         <Frame caption="Click on this button!">
-          <img src="file:58e638a2-7862-451e-9c69-2705ad1f6022" alt="Porkbun DNS Management" />
+          <img src="file:57da42f8-9541-4e8a-9b20-7c81ca585355" alt="Porkbun DNS Management" />
         </Frame>
 
         3. Scroll down to the quick upload section
 
         <Frame caption="Upload your BIND zone file here">
-          <img src="file:a33096b6-9f1c-40f0-9e3d-71c7aa850d30" alt="Porkbun Zone File Import" />
+          <img src="file:2824bdf3-c4c7-4dfe-b67a-1373865ecf22" alt="Porkbun Zone File Import" />
         </Frame>
 
         4. Upload the downloaded BIND zone file as is
@@ -1898,7 +1898,7 @@ Configuring your domain is a three-step process: add the domain via API, copy th
               * **Value:** Can directly copy paste the `value` from the API response (e.g., `{random_letters_numbers}.dkim.amazonses.com`).
 
             <Frame caption="Example of adding a CNAME record in Route 53. Notice that AWS already appends the root domain (agentmail.cc) to the end of the name value!">
-              <img src="file:b6048450-c831-4d87-96bf-7f62d837ef90" alt="AWS Route 53 Record Configuration" />
+              <img src="file:62bea4af-5b5e-4f88-86ce-b569f26f8a74" alt="AWS Route 53 Record Configuration" />
             </Frame>
 
             * **TXT (DMARC/SPF):**
@@ -2008,7 +2008,7 @@ DNS can be tricky. Here are some common issues and how to resolve them.
 
 ## Best Practices for Domain Management
 
-Check out our guide on [Email Deliverability](/best-practices/email-deliverability) for tips on warming up your new domain and maintaining a healthy sender reputation.
+Check out our guide on [Email Deliverability](/email-deliverability) for tips on warming up your new domain and maintaining a healthy sender reputation.
 
 
 # Managing Your Domains
@@ -2434,13 +2434,13 @@ Ngrok creates a secure tunnel from a public URL to your local development server
 
 Visit [ngrok.com](https://ngrok.com/) and click "Sign up" to create a free account.
 
-<img src="file:2b9efd50-bc45-4c1d-be5d-0a0e2451fc05" alt="Ngrok homepage" />
+<img src="file:845efbdc-7a3b-44be-b7b6-d85c15baabfd" alt="Ngrok homepage" />
 
 ### 1.2 Choose your platform and install
 
 After logging in, ngrok will guide you through the setup process. Select your operating system and follow the installation instructions.
 
-<img src="file:53878264-f22e-45d0-b6e5-3deace921b2d" alt="Ngrok setup instructions" />
+<img src="file:6bf31cc4-f08c-4b45-9abd-b93966def3ab" alt="Ngrok setup instructions" />
 
 For macOS, you can install ngrok via Homebrew:
 
@@ -2486,7 +2486,7 @@ ngrok http 3000
 
 You should see output similar to this:
 
-<img src="file:da7bae5a-8b4d-4657-9da6-ffe312457580" alt="Ngrok terminal output" />
+<img src="file:190c3920-7025-4399-8718-b2b9a4895382" alt="Ngrok terminal output" />
 
 Copy the **Forwarding URL** (e.g., `https://your-subdomain.ngrok-free.app`). This is the public URL that AgentMail will use to send webhooks.
 
@@ -2583,7 +2583,7 @@ python webhook_receiver.py
 
 Open your browser and visit `http://127.0.0.1:3000` to see the status page confirming your webhook receiver is running:
 
-<img src="file:a246e89b-1dc2-4f91-b1b7-ebe6527efb10" alt="Webhook receiver status page" />
+<img src="file:933ee151-1684-4e56-b2a9-4dd7e81f9f5d" alt="Webhook receiver status page" />
 
 ## Testing Your Setup
 
@@ -2705,7 +2705,7 @@ How you send your emails is just as important as what you send. If you're sendin
     more natural to email providers. AgentMail's ability to create inboxes at
     scale makes this strategy easy to implement.
 
-    <img src="file:1c500820-48d4-480b-8df5-7f6b0c12fc34" alt="Diagram comparing one inbox sending 1000 emails vs. five inboxes sending 200 each." />
+    <img src="file:256ac0e7-42b8-4fdd-a3f1-6136fbec2725" alt="Diagram comparing one inbox sending 1000 emails vs. five inboxes sending 200 each." />
   </Step>
 
   <Step title="Protect Your Reputation with Multiple Domains">
@@ -3293,6 +3293,7 @@ Create a file named `agent.py` and paste the following code:
   from flask import Flask, request, Response
   import ngrok
   from agentmail import AgentMail
+  import threading
 
   # Configuration
   PORT = 8080
@@ -3302,6 +3303,7 @@ Create a file named `agent.py` and paste the following code:
   # Initialize Flask app and AgentMail client
   app = Flask(__name__)
   client = AgentMail()
+  processed_messages = set()  # Track processed message IDs to prevent duplicates
 
 
   def setup_agentmail():
@@ -3334,6 +3336,7 @@ Create a file named `agent.py` and paste the following code:
           webhook = client.webhooks.create(
               url=f"{listener.url()}/webhook/agentmail",
               event_types=["message.received"],
+              inbox_ids=[inbox.inbox_id],
               client_id=f"{INBOX_USERNAME}-webhook"
           )
           print(f"✓ Webhook created")
@@ -3361,25 +3364,8 @@ Create a file named `agent.py` and paste the following code:
       )
 
 
-  @app.route('/webhook/agentmail', methods=['POST'])
-  def receive_webhook():
-      """Webhook endpoint to receive incoming email notifications."""
-      payload = request.json
-      event_type = payload.get('type') or payload.get('event_type')
-
-      # Ignore outgoing messages
-      if event_type == 'message.sent':
-          return Response(status=200)
-
-      message = payload.get('message', {})
-      message_id = message.get('message_id')
-      inbox_id = message.get('inbox_id')
-      from_field = message.get('from_', '') or message.get('from', '')
-
-      # Validate required fields
-      if not message_id or not inbox_id or not from_field:
-          return Response(status=200)
-
+  def process_and_reply(message_id, inbox_id, from_field, subject, message):
+      """Process incoming message and send reply in background."""
       # Extract sender email and name
       if '<' in from_field and '>' in from_field:
           sender_email = from_field.split('<')[1].split('>')[0].strip()
@@ -3390,10 +3376,8 @@ Create a file named `agent.py` and paste the following code:
           sender_email = from_field.strip()
           sender_name = sender_email.split('@')[0].title() if '@' in sender_email else 'Friend'
 
-      subject = message.get('subject', '(no subject)')
-
       # Log incoming email
-      print(f"Email from {sender_email}: {subject}")
+      print(f"Processing email from {sender_email}: {subject}")
 
       # Generate and send auto-reply
       try:
@@ -3408,6 +3392,41 @@ Create a file named `agent.py` and paste the following code:
       except Exception as e:
           print(f"Error: {e}\n")
 
+
+  @app.route('/webhook/agentmail', methods=['POST'])
+  def receive_webhook():
+      """Webhook endpoint to receive incoming email notifications."""
+      payload = request.json
+      event_type = payload.get('type') or payload.get('event_type')
+
+      # Ignore outgoing messages
+      if event_type == 'message.sent':
+          return Response(status=200)
+
+      message = payload.get('message', {})
+      message_id = message.get('message_id')
+      inbox_id = message.get('inbox_id')
+      from_field = message.get('from_', '') or message.get('from', '')
+
+      # Validate required fields
+      if not message_id or not inbox_id or not from_field:
+          return Response(status=200)
+
+      # prevent duplicate
+      if message_id in processed_messages:
+          return Response(status=200)
+      processed_messages.add(message_id)
+
+      subject = message.get('subject', '(no subject)')
+
+      # Process in background thread and return immediately
+      thread = threading.Thread(
+          target=process_and_reply,
+          args=(message_id, inbox_id, from_field, subject, message)
+      )
+      thread.daemon = True
+      thread.start()
+
       return Response(status=200)
 
 
@@ -4705,7 +4724,7 @@ Done
 
 Go to your AgentMail inbox and filter by labels to organize your emails:
 
-<img src="file:879ff90e-9416-4b31-a009-2054c03d170d" alt="Test image" />
+<img src="file:0cf3d744-bb78-46de-acc7-e3de13a39cf9" alt="Test image" />
 
 **Filter by sentiment:**
 
@@ -4875,12 +4894,545 @@ Ready to build your own intelligent email agent? Check out our [quickstart guide
 </AccordionGroup>
 
 
+# Email Reply Extraction with Talon
+
+> Learn how to use Talon to extract new content from email replies, removing quoted text with 93.8% accuracy.
+
+## Why Talon?
+
+Email threads accumulate quoted replies that clutter the actual content. When processing emails programmatically, you need just the new message, not the entire conversation history.
+
+**Talon solves this problem** by extracting clean reply content through sophisticated pattern matching and structural analysis.
+
+### Use Cases
+
+* **AI Email Agents**: Extract new user messages without processing entire thread history
+* **Email Automation**: Parse replies to identify actionable content
+* **Thread Analysis**: Build conversation flows by isolating individual contributions
+* **Inbox Management**: Process only new information from replies
+
+### Why Choose Talon?
+
+<CardGroup cols={2}>
+  <Card title="HTML Email Support" icon="fa-regular fa-file-code">
+    Handles Gmail, Outlook, Apple Mail, Thunderbird HTML structures
+  </Card>
+
+  <Card title="High Accuracy" icon="fa-regular fa-bullseye">
+    93.8% success rate across 64 real-world test cases
+  </Card>
+
+  <Card title="Multi-language" icon="fa-regular fa-globe">
+    Supports English, Japanese, Swedish, Polish, Dutch, German
+  </Card>
+
+  <Card title="Fast Performance" icon="fa-regular fa-gauge-high">
+    1.92ms average processing time, 488 emails/second
+  </Card>
+</CardGroup>
+
+***
+
+## How Talon Works
+
+Talon uses two complementary approaches depending on email format:
+
+### Plain Text Processing (6-Stage Pipeline)
+
+1. **Line Classification**: Assigns markers to each line ('t'=text, 'm'=quote marker, 's'=splitter, 'e'=empty)
+2. **Pattern Matching**: Applies regex to marker sequences to identify quoted blocks
+3. **Content Extraction**: Removes quoted lines and returns clean text
+
+Recognizes patterns like:
+
+* Standard quote markers (`>`)
+* Reply headers ("On \[date] \[name] wrote:")
+* Forward indicators ("-----Original Message-----")
+
+### HTML Processing (8-Stage Pipeline)
+
+1. **Structural Removal**: Directly removes known quotation elements (Gmail divs, blockquotes, Outlook markup)
+2. **Checkpoint Fallback**: For non-standard HTML, maps elements to text lines, applies text patterns, removes corresponding HTML
+
+### Processing Systems
+
+**Quotation Removal** (Primary)
+
+* Removes quoted replies from thread
+* No initialization required
+* Rule-based pattern matching
+
+***
+
+## Getting Started
+
+<Steps>
+  <Step title="Install Talon">
+    Install via pip with required workaround for Python 3.11+:
+
+    <CodeBlocks>
+      ```bash
+      pip install talon
+      ```
+    </CodeBlocks>
+  </Step>
+
+  <Step title="Apply Python 3.11+ Workaround">
+    Required fix for cchardet dependency:
+
+    <CodeBlocks>
+      ```python
+      # Import workaround BEFORE importing talon
+      import sys
+      import chardet
+      sys.modules['cchardet'] = chardet
+
+      # Now safe to import talon
+      import talon
+      from talon import quotations
+      ```
+    </CodeBlocks>
+
+    <Callout intent="warn">
+      This workaround is **required** for Python 3.11+.
+    </Callout>
+  </Step>
+
+  <Step title="Extract Reply Content">
+    Basic usage for plain text and HTML:
+
+    <CodeBlocks>
+      ```python title="Plain Text"
+      from talon import quotations
+
+      email = """Great work on the project!
+
+      On Mon, Apr 11, 2011 at 6:54 PM, Bob wrote:
+      > Can you review the document?
+      > Need feedback by Friday.
+      """
+
+      clean_reply = quotations.extract_from_plain(email)
+      # Result: "Great work on the project!"
+      ```
+
+      ```python title="HTML"
+      from talon import quotations
+
+      html_email = """
+      <html><body>
+      <div>Thanks for the update!</div>
+      <div class="gmail_quote">
+        <div>On Mon, Alice wrote:</div>
+        <blockquote>Original message here</blockquote>
+      </div>
+      </body></html>
+      """
+
+      clean_html = quotations.extract_from_html(html_email)
+      # Returns: <html><body><div>Thanks for the update!</div></body></html>
+      ```
+    </CodeBlocks>
+  </Step>
+</Steps>
+
+***
+
+## Performance & Accuracy
+
+Talon has been tested on 64 real-world emails from various clients and languages.
+
+### Test Results Summary
+
+| Metric                  | Value               |
+| ----------------------- | ------------------- |
+| **Total Tests**         | 64 emails           |
+| **Passed**              | 60 (93.8%)          |
+| **Failed**              | 4 (6.2%)            |
+| **Avg Processing Time** | 1.92ms              |
+| **Throughput**          | 488.6 emails/second |
+| **Min/Max Time**        | 0.13ms - 21.55ms    |
+
+### Test Coverage
+
+* **22 HTML emails**: Gmail, Outlook, Apple Mail, Thunderbird, Mail.ru, Hotmail
+* **42 plain text emails**: Various formats and reply styles
+* **6+ languages**: English, Japanese, Swedish, Polish, Dutch, German
+* **Mobile clients**: iPhone, Android "Sent from" signatures
+
+### Processing Time by Complexity
+
+| Email Type         | Avg Time  | Complexity |
+| ------------------ | --------- | ---------- |
+| Simple text reply  | 0.2-0.5ms | Low        |
+| HTML Gmail/Outlook | 2-4ms     | Medium     |
+| Complex threads    | 4-22ms    | High       |
+
+### Speed vs Accuracy Tradeoff
+
+| Library      | Avg Processing Time | Accuracy | Best For                                |
+| ------------ | ------------------- | -------- | --------------------------------------- |
+| **Talon**    | 1.92ms              | 93.8%    | Production systems needing HTML support |
+| qutoequail   | 0.96ms              | \~85%    | Moderate accuracy requirements          |
+| Custom regex | 0.1ms               | \~70%    | Simple plain text, speed critical       |
+
+**Insight**: For production systems, 1.92ms average is negligible. Even at worst case (21.55ms), Talon is faster than most network requests.
+
+***
+
+## Known Limitations
+
+Talon failed 4 out of 64 test cases. Here's what didn't work:
+
+<AccordionGroup>
+  <Accordion title="Failed Test Cases (4 total)">
+    ### Test Case 1: Complex Email Thread with Mixed Content
+
+    **Input**:
+
+    ```text
+    Thank you, Sonya Johnson.
+
+    I have sent an invite for 10:30am Monday PDT (today). I
+    hope you can join.
+
+    Regards,
+
+    Christopher Edwards
+
+
+    On Mon, Jun 3, 2024 at 12:53 AM Cody Hart <omerritt@example.com> wrote:
+
+    > Hi Christopher Edwards,
+    >
+    > 10.30 AM pacific is good for me.
+    >
+    > Thanks & Regards,
+    >
+    > Cody Hart
+    ```
+
+    **Expected Output**: First 5 lines only (up to `Christopher Edwards`)
+
+    **Talon's Output**: Returns entire email including quoted text starting with "On Mon, Jun 3..." and all "> quoted text"
+
+    **Processing Time**: 2.55ms
+
+    **Issue**: Signature placement before quotes confuses detection logic
+
+    ***
+
+    ### Test Case 2: Inline Responses
+
+    **Input**:
+
+    ```text
+    On Tue, Apr 29, 2014 at 4:22 PM, Example Dev <sugar@example.com> wrote:
+
+    > okay. Well, here's some stuff I can write.
+    >
+    > And if I write a 2 second line you and maybe reply under this?
+    >
+    > Or if you didn't really feel like it, you could reply under this line.
+
+    I will reply under this one
+
+    >
+    > okay?
+    >
+
+    and under this.
+
+    >
+    > -- Tim
+    ```
+
+    **Expected Output**: Just the inline responses (`I will reply under this one` and `and under this.`)
+
+    **Talon's Output**: Returns everything including "On Tue, Apr 29..." header and all quoted lines
+
+    **Processing Time**: 0.48ms
+
+    **Issue**: Interleaved inline responses not recognized as the reply pattern
+
+    ***
+
+    ### Test Case 3: Gmail Forward HTML
+
+    **Input**:
+
+    ```html
+    <html><head></head><body><div dir="ltr">test<div><br /></div><div>blah</div>
+    <div><br /><div class="gmail_quote">---------- Forwarded message ----------<br />
+    From: <b class="gmail_sendername">Foo Bar</b>
+    <span dir="ltr">&lt;<a href="mailto:foo@bar.example">foo@bar.example</a>&gt;</span><br />
+    Date: Thu, Mar 24, 2016 at 5:17 PM<br />
+    Subject: The Subject<br />
+    To: John Doe &lt;<a href="mailto:john@doe.example">john@doe.example</a>&gt;<br />
+    <br /><br /><div dir="ltr">Some text<div><br /></div><div><br /></div></div>
+    </div><br /></div></div></body></html>
+    ```
+
+    **Expected Output**: Just `testblah` (before the forward marker)
+
+    **Talon's Output**: Includes "---------- Forwarded message ----------" and forwarded content
+
+    **Processing Time**: 3.41ms
+
+    **Issue**: HTML forward headers not removed by Gmail quote detection
+
+    ***
+
+    ### Test Case 4: Thunderbird Forward HTML
+
+    **Input**:
+
+    ```html
+    <html><body bgcolor="#FFFFFF" text="#000000">
+    <p><br /></p>
+    <div class="moz-forward-container"><br /><br />
+    -------- Forwarded Message --------
+    <table class="moz-email-headers-table">
+      <tbody>
+        <tr><th>Subject:</th><td>Re: Example subject</td></tr>
+        <tr><th>Date:</th><td>Tue, 3 May 2016 14:54:27 +0200 (CEST)</td></tr>
+        <tr><th>From:</th><td>John Doe &lt;johndoe@example.com&gt;</td></tr>
+      </tbody>
+    </table>
+    <br /><br />
+    <div>Dear John,</div>
+    <div><br /></div>
+    <div>This is a test.</div>
+    </div></body></html>
+    ```
+
+    **Expected Output**: Empty (no new content, just forward)
+
+    **Talon's Output**: Includes "-------- Forwarded Message --------" and forwarded content
+
+    **Processing Time**: 4.34ms
+
+    **Issue**: Thunderbird's `moz-forward-container` class not recognized
+
+    ***
+
+    **Summary**: 3 of 4 failures are forwarded messages. Regular replies work with 98%+ accuracy.
+  </Accordion>
+
+  <Accordion title="Success Examples">
+    ### Example 1: Simple Gmail Reply
+
+    **Input**:
+
+    ```text
+    Awesome! I haven't had another problem with it.
+
+    On Aug 22, 2011, at 7:37 PM, defunkt<reply@reply.github.com> wrote:
+
+
+
+
+    > Loader seems to be working well.
+    ```
+
+    **Talon's Output**: `Awesome! I haven't had another problem with it.`
+
+    **Processing Time**: 0.2ms
+
+    **What Worked**: Standard "On \[date] \[name] wrote:" pattern detected, quote marker (>) recognized
+
+    ***
+
+    ### Example 2: Outlook Reply with Separator
+
+    **Input**:
+
+    ```text
+    Outlook with a reply directly above line
+    ________________________________________
+    From: CRM Comments [crm-comment@example.com]
+    Sent: Friday, 23 March 2012 5:08 p.m.
+    To: John S. Greene
+    Subject: [contact:106] John Greene
+
+    A new comment has been added to the Contact named 'John Greene':
+
+    I am replying to a comment.
+    ```
+
+    **Talon's Output**: `Outlook with a reply directly above line`
+
+    **Processing Time**: 0.51ms
+
+    **What Worked**: Outlook separator line (underscores) and "From:"/"Sent:" headers detected as splitter
+
+    ***
+
+    ### Example 3: HTML Outlook Reply
+
+    **Input**:
+
+    ```html
+    <html>
+      <body>
+        <div>Reply</div>
+        <span id="OLK_SRC_BODY_SECTION">
+          <div>
+            <span>From: </span>Bob &lt;<a href="mailto:bob@example.com">bob@example.com</a>&gt;<br />
+            <span>Date: </span>Tue, 01 Nov 2011 18:54:39 -0700<br />
+            <span>To: </span>Rob &lt;<a href="mailto:rob@example.com">rob@example.com</a>&gt;<br />
+            <span>Subject: </span>Test<br />
+          </div>
+          <div>Hi</div>
+        </span>
+      </body>
+    </html>
+    ```
+
+    **Talon's Output**: `Reply`
+
+    **Processing Time**: 4.02ms
+
+    **What Worked**: Outlook's `OLK_SRC_BODY_SECTION` span ID detected and removed structurally
+  </Accordion>
+
+  <Accordion title="Performance vs Simpler Alternatives">
+    **Tradeoff**: Talon is more comprehensive but slower than plain-text-only libraries
+
+    * Talon: 1.92ms average (with HTML support)
+    * email-reply-parser: 0.03ms average (plain text only)
+
+    For production systems, 1.92ms average is negligible. Even at worst case (21.55ms), Talon is faster than most network requests.
+  </Accordion>
+
+  <Accordion title="Forwarded Messages">
+    As shown in test results, forwarded messages (especially HTML) are challenging:
+
+    * Plain text forwards: Generally work well
+    * HTML forwards: May retain forward headers
+    * Workaround: Use plain text extraction or post-process to remove forward markers
+  </Accordion>
+</AccordionGroup>
+
+***
+
+### Error Handling
+
+Always handle potential parsing failures:
+
+```python
+from talon import quotations
+
+def safe_extract(email_body, is_html=False):
+    try:
+        if is_html:
+            return quotations.extract_from_html(email_body)
+        else:
+            return quotations.extract_from_plain(email_body)
+    except Exception as e:
+        # Fallback to original message if extraction fails
+        print(f"Talon extraction failed: {e}")
+        return email_body
+```
+
+### Testing Recommendations
+
+Always test with your specific email formats:
+
+```python
+# Create a test suite with your actual email patterns (Gmail, Outlook, Apple Mail)
+test_emails = [
+    "path/to/gmail_reply.html",
+    "path/to/outlook_reply.txt",
+    "path/to/forward.html"
+]
+
+for email_file in test_emails:
+    with open(email_file) as f:
+        content = f.read()
+        result = quotations.extract_from(content)
+        print(f"{email_file}: {len(result)} chars extracted")
+```
+
+<Tip>
+  Test with real emails from your users' actual email clients. Talon's accuracy is based on diverse real-world samples, but your specific use case may have unique patterns.
+</Tip>
+
+***
+
+## JavaScript Version
+
+For TypeScript/JavaScript projects, use **[TalonJS](https://github.com/quentez/talonjs)** - a JavaScript port of Talon with similar functionality.
+
+### Performance Comparison
+
+| Solution         | Accuracy | Speed  | Best For                    |
+| ---------------- | -------- | ------ | --------------------------- |
+| **Python Talon** | 93.8%    | 1.92ms | Highest accuracy            |
+| **TalonJS**      | 90.6%    | 1.88ms | TypeScript/Node.js projects |
+
+TalonJS provides 90.6% accuracy with slightly faster performance (1.88ms), making it ideal for JavaScript/TypeScript environments without needing Python dependencies.
+
+### Quick Start
+
+<Steps>
+  <Step title="Install TalonJS">
+    ```bash
+    npm install talonjs
+    ```
+  </Step>
+
+  <Step title="Extract Replies">
+    <CodeBlocks>
+      ```typescript title="Plain Text"
+      import * as talon from 'talonjs';
+
+      const email = `Great work on the project!
+
+      On Mon, Apr 11, 2011 at 6:54 PM, Bob wrote:
+      > Can you review the document?
+      > Need feedback by Friday.
+      `;
+
+      const result = talon.quotations.extractFromPlain(email);
+      const cleanReply = result.body.trim();
+      // Output: "Great work on the project!"
+      ```
+
+      ```typescript title="HTML"
+      import * as talon from 'talonjs';
+
+      const htmlEmail = `
+        <div>Thanks for the update!</div>
+        <div class="gmail_quote">
+          On Mon, Alice wrote: <blockquote>Original</blockquote>
+        </div>
+      `;
+
+      const result = talon.quotations.extractFromHtml(htmlEmail);
+      const cleanReply = result.body.trim();
+      // Returns: "<div>Thanks for the update!</div>"
+      // Note: TalonJS returns clean HTML, not plain text
+      ```
+    </CodeBlocks>
+  </Step>
+</Steps>
+
+<Tip>
+  **When to use TalonJS vs Python Talon:**
+
+  * Use **TalonJS** if you're building in TypeScript/JavaScript and 90.6% accuracy is sufficient
+  * Use **Python Talon** if you need the highest accuracy (93.8%) or are in a Python environment
+  * The 3.2% accuracy difference is acceptable for most use cases
+</Tip>
+
+
 # Join the AgentMail Community
 
 > Connect with the AgentMail team and developers, share what you're building, and get support.
 
 <CardGroup>
-  <Card title="Join our Discord Server" href="https://discord.gg/your-invite-code" icon="fa-brands fa-discord">
+  <Card title="Join our Discord Server" href="https://discord.com/invite/hTYatWYWBc" icon="fa-brands fa-discord">
     The best place for real-time conversation, getting help with your code, and
     sharing what you're building with AgentMail.
   </Card>