diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..f85c6b1 --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +config.py \ No newline at end of file diff --git a/README.md b/README.md index 4f859c5..ebe1613 100644 --- a/README.md +++ b/README.md @@ -1,93 +1,5 @@ -# LeoGPT +Create a config.py file in the same directory as the leogpt.py file and configure the following: - - -## Getting started - -To make it easy for you to get started with GitLab, here's a list of recommended next steps. - -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! - -## Add your files - -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: - -``` -cd existing_repo -git remote add origin https://git.jisoonet.com/publicprojects/leogpt.git -git branch -M main -git push -uf origin main -``` - -## Integrate with your tools - -- [ ] [Set up project integrations](http://unraid:9080/publicprojects/leogpt/-/settings/integrations) - -## Collaborate with your team - -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) - -## Test and Deploy - -Use the built-in continuous integration in GitLab. - -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) - -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README - -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. +openai_api_key = 'YOUR_OPENAI_API_KEY' +discord_bot_token = 'YOUR_DISCORD_BOT_TOKEN' +assistant_id = 'YOUR_OPENAI_ASSISTANT_ID' \ No newline at end of file diff --git a/leogpt.py b/leogpt.py new file mode 100644 index 0000000..8ec5dfa --- /dev/null +++ b/leogpt.py @@ -0,0 +1,173 @@ +import discord +from discord.ext import commands +from openai import AsyncOpenAI +import logging +import asyncio +import time +import config +import os +from collections import defaultdict +from datetime import datetime, timedelta + +# Configuration +openai_api_key = os.getenv('OPENAI_API_KEY', config.openai_api_key) +discord_bot_token = os.getenv('DISCORD_BOT_TOKEN', config.discord_bot_token) +assistant_id = config.assistant_id + +# Setting up logging +logging.basicConfig(level=logging.INFO, format='%(asctime)s - %(levelname)s - %(message)s') + +# OpenAI Client Setup +openai_client = AsyncOpenAI(api_key=openai_api_key) + +# Discord Bot Setup +intents = discord.Intents.default() +bot = commands.Bot(command_prefix="!", intents=intents) + +# Thread Management +thread_ids = defaultdict(lambda: {"thread_id": None, "last_used": datetime.now()}) + +# Function to create a new thread +async def create_new_thread(identifier): + global thread_ids + try: + thread = await openai_client.beta.threads.create() + thread_ids[identifier] = {"thread_id": thread.id, "last_used": datetime.now()} + logging.info(f"New thread created for {identifier} with ID: {thread.id}") + except Exception as e: + logging.error(f"Error during thread creation for {identifier}: {e}") + raise + +# Function to send messages in chunks +async def send_in_chunks(channel, message): + logging.info("Sending message in chunks") + try: + chunk_size = 2000 + while message: + split_index = (message.rfind(' ', 0, chunk_size) + 1) if len(message) > chunk_size else len(message) + chunk = message[:split_index].strip() + await channel.send(chunk) + message = message[split_index:] + logging.info("All chunks sent successfully") + except Exception as e: + logging.error(f"Error sending message in chunks: {e}") + raise + +# Function to process incoming messages +async def process_message(message): + return discord.utils.remove_markdown(message.clean_content) + +# Function to send message to OpenAI +async def send_message_to_openai(clean_message, thread_id): + try: + await openai_client.beta.threads.messages.create( + thread_id=thread_id, + role="user", + content=clean_message + ) + except Exception as e: + logging.error(f"Error sending message to OpenAI: {e}") + raise + +# Function to check OpenAI response +async def check_openai_response(thread_id, run_id): + try: + start_time = time.time() + while True: + updated_run = await openai_client.beta.threads.runs.retrieve( + thread_id=thread_id, + run_id=run_id + ) + if updated_run.status == "completed": + break + + elapsed_time = time.time() - start_time + sleep_time = min(1 + elapsed_time / 10, 5) + await asyncio.sleep(sleep_time) + except Exception as e: + logging.error(f"Error checking OpenAI response: {e}") + raise + +# Function to retrieve the latest response from OpenAI +async def retrieve_latest_response(thread_id): + try: + messages = await openai_client.beta.threads.messages.list(thread_id=thread_id) + assistant_messages = [msg for msg in messages.data if msg.role == "assistant"] + if assistant_messages: + latest_message = max(assistant_messages, key=lambda x: x.created_at) + return latest_message.content[0].text.value + else: + return "No response from the assistant." + except Exception as e: + logging.error(f"Error retrieving response from OpenAI: {e}") + raise + +# Function to interact with OpenAI +async def interact_with_openai(clean_message, identifier): + global thread_ids + thread_info = thread_ids[identifier] + thread_id = thread_info["thread_id"] + if thread_id is None: + await create_new_thread(identifier) + thread_id = thread_ids[identifier]["thread_id"] + + try: + await send_message_to_openai(clean_message, thread_id) + + run = await openai_client.beta.threads.runs.create( + thread_id=thread_id, + assistant_id=assistant_id + ) + + await check_openai_response(thread_id, run.id) + return await retrieve_latest_response(thread_id) + + except Exception as e: + logging.error(f"Error during OpenAI interaction: {e}") + return "I'm having trouble processing your request right now." + +# Function for cleaning up old threads +def cleanup_old_threads(): + now = datetime.now() + for key, value in list(thread_ids.items()): + if now - value["last_used"] > timedelta(hours=1): + del thread_ids[key] + +# Bot event: on_ready +@bot.event +async def on_ready(): + try: + logging.info(f"Logged in as {bot.user.name}") + except Exception as e: + logging.error(f"Error in on_ready: {e}") + +# Bot event: on_message +@bot.event +async def on_message(message): + try: + if message.author == bot.user: + return + + # Check for @everyone or @here mentions and ignore such messages + if "@everyone" in message.content or "@here" in message.content: + return + + identifier = message.channel.id + thread_ids[identifier]["last_used"] = datetime.now() + + cleanup_old_threads() + + if bot.user.mentioned_in(message): + clean_message = await process_message(message) + logging.info(f"Received message from {message.author.name}: {clean_message}") + + async with message.channel.typing(): + response = await interact_with_openai(clean_message, identifier) + logging.info(f"OpenAI response: {response}") + + await send_in_chunks(message.channel, response) + except Exception as e: + logging.error(f"Error in on_message for {message.content}: {e}") + +# Running the bot +bot.run(discord_bot_token)