MarlBurroW/kinbot

AI Summary: The KinBot project is seeking community assistance to test its 24 built-in provider integrations. Contributors are asked to pick an untested provider, configure it in the KinBot settings, and test its specific capabilities (LLM, Embedding, Image, Search, Rerank). Feedback should be provided by commenting on the issue if the provider works, or by opening a new issue if it's broken.

AI Summary: This GitHub issue requests the addition of Spanish (es) as a new language translation for KinBot to significantly broaden its accessibility. It outlines a contribution process involving translating approximately 1250 keys, registering the locale, and testing, with tips for maintaining a casual tone and allowing partial contributions. The goal is to have a complete `es.json` file and functional Spanish UI.

AI Summary: This issue aims to add a German (de) translation to KinBot, expanding its reach to the German self-hosting community. It primarily involves translating approximately 1250 UI keys from English, registering the new locale, and ensuring the UI remains functional and visually appealing despite potentially longer German words. Partial contributions are encouraged, allowing for collaborative completion.

AI Summary: The `scheduleJob` function in `crons.ts` incorrectly casts a `Date` object to a `string` when creating a new Cron job. While this doesn't cause a runtime error because the underlying library `croner` accepts both types, it undermines TypeScript's type safety and could lead to issues if the library's API changes. The suggested fix is to remove the unnecessary type assertion.

AI Summary: This issue identifies an unused variable `targetKinId` within the `triggerCron` function in `src/server/services/crons.ts`. The variable is computed but never utilized, as the `spawnTask` function directly uses `cron.targetKinId`. The suggested fix is to simply remove the unnecessary variable declaration.

AI Summary: This bug report highlights a lack of server-side validation for the `title` field in quick session creation and the `memorySummary` field when closing a session. The current implementation allows for empty or excessively long strings, potentially leading to data integrity issues. The suggested fix involves adding trimming, whitespace-only checks, and length limits to these fields.

AI Summary: This bug report highlights that all three quick session hooks (`useQuickChat`, `useQuickSession`, `useQuickSessionHistory`) contain empty `catch` blocks, causing errors to be silently ignored. This prevents users from receiving any feedback when operations like sending messages, fetching data, or creating/closing sessions fail.

AI Summary: The API endpoint for creating webhooks incorrectly accepts a `kinId` that does not exist in the database. While a foreign key constraint prevents the insertion, the error message is generic and unhelpful. The suggested fix involves adding a check to verify the `kinId`'s existence before attempting to create the webhook, returning a clear 'Kin not found' error.

AI Summary: This enhancement request aims to improve the user experience by making it easier to visually distinguish between active and inactive webhooks in a list. Currently, only the switch position indicates inactivity, making it difficult for users to quickly scan and identify disabled webhooks. The suggested solution involves visually dimming the card, adding an 'Inactive' badge, or changing the webhook icon's color.

AI Summary: The webhook form in the application silently swallows API errors during submission. When a network error or server-side error occurs, the loading spinner stops, but no feedback is provided to the user, leaving them unaware of the failure. The suggested fix involves adding a `catch` block to display an error message to the user.

AI Summary: The server incorrectly accepts webhook names that consist only of whitespace. This is because the validation logic for the POST endpoint only checks for a falsy name, and the PATCH endpoint has no name validation. The suggested fix involves trimming whitespace from the name and ensuring it's not empty after trimming, returning a 400 error if it is.

AI Summary: This issue proposes enhancing the cron schedule input form to provide more helpful feedback to users. Currently, it only shows a generic error for invalid expressions. The suggested improvements include displaying the next three scheduled run times for valid expressions and providing more specific error messages when the expression is invalid, leveraging the capabilities of the `croner` library.

AI Summary: This issue proposes adding emoji reactions to messages in a web chat UI, allowing users to quickly acknowledge or rate responses. The implementation involves displaying preset reactions on hover, storing them in the database, and synchronizing them in real-time for multi-user instances. This feature aims to improve user feedback and potentially inform future AI memory.

AI Summary: This issue proposes adding a "System Info" panel to the application's settings. This panel will display crucial runtime details such as KinBot and Bun versions, OS information, database size, memory usage, server uptime, and connection statistics. The goal is to provide self-hosters with an easy way to monitor their instance's health without needing server access.

AI Summary: This issue proposes adding a `/health` HTTP endpoint to the application and a `HEALTHCHECK` instruction to the Dockerfile. This will improve container orchestration by allowing tools to verify the application's readiness and health status.

AI Summary: This issue proposes adding functionality to export and import Kin configurations as JSON files. This will allow users to back up, restore, and share their Kin setups, facilitating easier management and community sharing of custom Kin templates. The feature will involve UI elements for export and import, with specific exclusions for memory and conversation data.

AI Summary: This issue proposes adding a keyboard shortcuts help dialog to KinBot. The dialog will be accessible via the '?' key or a help button and will list all available shortcuts, categorized for better discoverability. It should be styled consistently with the existing design and be dismissible via the 'Escape' key or by clicking outside.

AI Summary: This issue proposes adding static screenshots to the project's README file to improve its visual appeal and user onboarding. The screenshots will showcase key features like the dashboard, conversation view, kin settings, and memory browser, aiming to provide a better first impression for potential users, especially those browsing on mobile or with video autoplay disabled.