# Define the directory containing the chat files
$directory = "docs/chats/"

# Get all markdown files in the directory
$files = Get-ChildItem -Path $directory -Filter "Codeium Chat - *.md"

foreach ($file in $files) {
    # Get the full path of the file
    $filepath = Join-Path $directory $file.Name

    # Get the last modification time of the file
    $fileModificationDateTime = (Get-Item $filepath).LastWriteTime

    # If the file was modified within the last 24 hours, skip it
    if ((Get-Date) - $fileModificationDateTime -lt [TimeSpan]::FromDays(1)) {
        continue
    }

    # Read the content of the file
    $content = Get-Content $filepath -Raw

    # Look for the first occurrence of the datetime pattern and convert it to a datetime object
    $datetimePattern = '\d{1,2}:\d{2} [ap]m, [A-Z][a-z]{2} \d{1,2}, \d{4}'
    $dateStr = [Regex]::Match($content, $datetimePattern).Value
    if ($dateStr) {
        # Parse the datetime string into a datetime object
        $dateObj = [DateTime]::ParseExact($dateStr, "h:mm tt, MMM d, yyyy", $null)
    }

    # Truncate the content if necessary (not shown in this example)

    # Send the content to an API to obtain a summary (not shown in this example)

    # Construct the new content with the summary and original content
    $newContent = "---`n"
    $newContent += "original file name: " + $file.Name + "`n"
    $newContent += "summary: " + $summary + "`n"
    $newContent += "date: " + $dateObj.ToString("yyyy-MM-ddTHH:mm") + "`n"
    $newContent += "---`n`n"
    $newContent += $content

    # Write the new content back to the file
    Set-Content -Path $filepath -Value $newContent

    # Rename the file with a new name based on the summary and date
    $title = $title.ToLower().Replace(' ', '-').Replace('_', '-')
    $title = [Regex]::Replace($title, "[^\w\-]", "")
    $newFilename = $dateObj.ToString("yyyy-MM-dd") + "-" + $title + ".md"
    Write-Host "Renaming $($file.Name) to $newFilename"
    Rename-Item -Path $filepath -NewName $newFilename
}

# Assuming your OpenAI API key is stored in the environment variable "OPENAI_API_KEY"
$openAiApiKey = [System.Environment]::GetEnvironmentVariable("OPENAI_API_KEY", "User")

# Define the OpenAI API URL for the chat completions endpoint
$openAiUrl = "https://api.openai.com/v1/engines/gpt-3.5-turbo/completions"

# Prepare the headers with the authorization
$headers = @{
    "Authorization" = "Bearer $openAiApiKey"
    "Content-Type" = "application/json"
}

# Define the data payload for the API request
$body = @{
    model = "gpt-3.5-turbo"
    messages = @(
        @{
            role = "system"
            content = "You are a helpful assistant."
        },
        @{
            role = "user"
            content = "Summarize this chat:"
        },
        @{
            role = "assistant"
            content = $truncatedContent # Your chat content here
        }
    )
} | ConvertTo-Json

# Make the API request and capture the response
$response = Invoke-RestMethod -Method Post -Uri $openAiUrl -Headers $headers -Body $body

# Extract the summary from the response
$summary = $response.choices[0].message.content

# Now you can use $summary in your script as needed

# Sample content with quotes and backticks
$content = @"
This is a sample content with "quotes" and `backticks`.
"@

# The data payload for the API request
$body = @{
    model = "gpt-3.5-turbo"
    messages = @(
        @{
            role = "system"
            content = "You are a helpful assistant."
        },
        @{
            role = "user"
            content = "Summarize this chat:"
        },
        @{
            role = "assistant"
            content = $content 
        }
    )
} | ConvertTo-Json -Depth 10

# Output the JSON to see the escaped characters
Write-Host $body

Invoke-RestMethod: C:\Users\xgenx\source\repos\handex.io\dev-scripts\summarize-chats.ps1:71:17          
Line |
 71 | … $response = Invoke-RestMethod -Method Post -Uri $openAiUrl -Headers $ …
   |        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   | {  "error": {   "message": "Unrecognized request argument supplied: messages",   "type":
   | "invalid_request_error",   "param": null,   "code": null  } }

{
 "messages": [
  {
   "role": "system",
   "content": "You are a helpful assistant."
  },
  {
   "role": "user",
   "content": "Summarize this chat:"
  },
  {
   "role": "assistant",
   "content": "# Codeium Chat Conversation\n\nNote: _This is purely the output of the chat conversation and does not contain any raw data, codebase snippets, etc. used to generate the output._\n\n**User** _at 9:05 pm, May 9, 2024_\n\nExplain problem: `JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists.`\n\n---\n\n**Codeium** _at 9:05 pm, May 9, 2024_\n\nThe issue \"JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists\" occurs because the JSX element `<use>` is not a standard HTML element and therefore TypeScript doesn't have a predefined type for it in the `JSX.IntrinsicElements` interface.\n\nTo resolve this, you can create an interface for the custom SVG elements you are using in your project. Here's an example of how you can define an interface for the `use` element:\n\n```tsx\ndeclare global {\n namespace JSX {\n  interface IntrinsicElements {\n   'use': React.SVGProps<SVGUseElement>;\n  }\n }\n}\n```\n\nYou can add this declaration at the beginning of your file or in a separate file to provide TypeScript with the necessary type information for the custom SVG elements like `<use>` that you are using in your JSX code.\n\nThis declaration tells TypeScript that the `<use>` element in your JSX code should be treated as an SVG element with properties that match `SVGUseElement` from the React typings.\n\n---\n\n**User** _at 9:29 pm, May 9, 2024_\n\nWhat file would I put that in?\n\n---\n\n**Codeium** _at 9:29 pm, May 9, 2024_\n\nYou can put the interface declaration in a TypeScript declaration file (`.d.ts`) that is included in your project. For example, you can create a file named `svg.d.ts` in your project with the following content:\n\n```typescript\n// svg.d.ts\ndeclare global {\n namespace JSX {\n  interface IntrinsicElements {\n   'use': React.SVGProps<SVGUseElement>;\n  }\n }\n}\n\nexport {};\n```\n\nMake sure that this declaration file is included in your TypeScript compilation context by either being in a directory covered by your `tsconfig.json` file or by explicitly including it in the `files` or `include` arrays of that config file.\n\nAfterwards, TypeScript will use this declaration along with its built-in JSX type definitions to type check your JSX code. If you add this to a `.d.ts` file that's already part of your project's type declaration structure, it should be picked up automatically by the TypeScript compiler."
  }
 ]
}

# Assuming the `$content` variable contains your chat content

# The data payload for the API request
$body = @{
    model = "gpt-3.5-turbo"
    prompt = $content  # Replace 'messages' with 'prompt'
    max_tokens = 150   # Adjust as needed
    temperature = 0.7  # Adjust as needed
} | ConvertTo-Json -Depth 10

# Now, make the API request with the corrected `$body`
$response = Invoke-RestMethod -Method Post -Uri $openAiUrl -Headers $headers -Body $body

# Extract the summary from the response
$summary = $response.choices[0].text

# Output the summary to check
Write-Host $summary

# The instruction to summarize the chat
$instruction = "Please summarize the following chat:"
# The chat content that needs to be summarized
$chatContent = $content  # Your chat content here

# Create the full prompt including the instruction and the chat content
$fullPrompt = $instruction + "`n`n" + $chatContent

# The data payload for the API request
$body = @{
    model = "gpt-3.5-turbo"
    prompt = $fullPrompt
    max_tokens = 150   # Adjust as needed
    temperature = 0.7  # Adjust as needed
} | ConvertTo-Json -Depth 10

# Now, make the API request with the `$body` containing the summarize instruction
$response = Invoke-RestMethod -Method Post -Uri $openAiUrl -Headers $headers -Body $body

# Extract the summary from the response
$summary = $response.choices[0].text

# Output the summary to check
Write-Host $summary