v3.2.0

Change to not use mcp due to it not working and rewrite to use chat completions with actually working functions (must be defined locally tho at least currently) and update to rust 1.93 and add reqwest and urlencoding libraries for interaction with search engine and add search engine function call.

Full Changelog: v3.1.0...v3.2.0

v3.1.0

Some prevalent changes:

• rewrite textgen to use responses api so i can use mcp for tool calls
• debug collects the version automatically from the crate so i only have to write the version in one place now smh

Full Changelog: v3.0.4...v3.1.0

v3.0.4

Update dependencies, go back to docker slim, and fix object id being null.

Full Changelog: v3.0.3...v3.0.4

v3.0.3

change dependency versions again lmfao

Full Changelog: v3.0.2...v3.0.3

v3.0.2

Update dependency versions

Full Changelog: v3.0.1...v3.0.2

v3.0.1

Add graceful shutdown and change docker base image versions

Full Changelog: v3.0.0...v3.0.1

v3.0.0

I'm gonna try to actually version this (probably not gonna do much but ok lol)

1. Rewrote to Rust from Typescript from Python
2. whatever else...

Full Changelog: v0.1.0...v3.0.0

v0.1.0

Agent Kitten Release Notes - Version 0.1.0

Released on October 3, 2024

Full Changelog: https://github.com/ClowderTech/agent-kitten-v2/commits/v0.1.0

Overview
This version marks the initial release of Agent Kitten, a powerful and versatile bot designed to streamline tasks and operations.

Highlights:

• Initial setup for running the bot within a Docker container.
• Basic functionality to generate MongoDB database names based on bot names.
• Integration with Deno for executing the bot's main logic (src/index.ts).
• Setup for pushing images to GitHub Container Registry (GHCR).

Features Added:

1. MongoDB Database Name Generation: A utility function generateDatabaseName in utils/mongohelper.ts has been implemented to ensure database names are compliant with MongoDB naming conventions.
2. Dockerfile Configuration: The Dockerfile is configured to run the bot using Deno and includes necessary dependencies for running it.
3. GitHub Actions Setup: A GitHub Workflow (docker-publish.yml) is in place to automate the build, push, and sign processes of Docker images.

Known Issues:

• This release is still in its early stages and may have some bugs or limitations. Please report any issues you encounter so we can address them quickly.
• The bot's functionality for running tasks or interacting with services has not been fully developed yet and will be added in future releases.

Next Steps:

1. Test the Bot: Ensure that the bot runs smoothly within the Docker container.
2. Expand Functionality: Start adding more features to enhance the bot’s capabilities.
3. Improve Documentation: Add detailed documentation for users on how to run and configure the bot.

If you have any questions or need assistance, feel free to reach out to our support team.