Merged
Conversation
Issues: - The broken loop: LLM call fails. - Error handler logs: missing the re-queues the task trigger. - The agent picks up the wrong trigger, so it tries LLM again and fails again, and repeats forever (infinite spam). --------------------- Updated: Fix 1: First few failures (up to 5) The LLMInterface tracks consecutive failures. Each failure increments a counter. The error propagates normally; avoid spam call's. Fix 2: up to 5th consecutive failure LLMConsecutiveFailureError is raised. The agent catches it in _handle_react_error. Fix3: Task is cancelled, NOT re-queued Instead of scheduling another retry trigger, it calls mark_task_cancel(). The loop stops completely. One final error message is shown in the chat1.... Fix4: Event stream stays quiet If the LLM was also failing during event summarization (filling logs), the fallback now prunes the old events anyway , then summarize_if_needed() stops triggering on every log() call.
I noticed that Node.js sometimes gets stuck at 1/8, most likely due to intermittent hanging. This can occasionally block execution in certain terminal environments (like the VS Code terminal). So I added an handling "stdin=subprocess.DEVNULL," to prevent console blocking during process creation. This helps bypass issues when running Node.js and other CraftBot terminal processes during installation and runtime.
…ent action attached non-existing file
Three updates I made in LLM providers in CraftBot: 1. DeepSeek was available in the model configuration UI but not in the provider setup, so I added it and tested it. 2. Created the Grok endpoint to support CraftBot. 3. Added Grok to both the provider list and the model configuration UI. Please kindly note that to support Grok, I have modified the session cache and session routing.
feature:long-task and mission handling, bug:fix minor ui bug, enable …
Added STT (Speech-to-Text) to the chat area, which supports multiple languages.
feature:rate-limit, bug:fix caching and error spamming issue
key removied
Feature/exp
Feature/format.md
SOUL.md update
feature:implemented tasks and event stream persistent
Service py added.
Fixed and updated the following issues in branch **v1.2.2**: 1. Graceful Shutdown (#160) 2. Installation script stuck at 98% during most of the installation (#153) 3. Dashboard receiving data even when the user is not on the dashboard tab (#166) Additionally, service handlers have been added: ``` # Install dependencies, register auto-start on login, and start CraftBot python service.py install ``` ``` # Other service commands: python service.py start # Start CraftBot in background python service.py status # Check if it's running python service.py stop # Stop CraftBot python service.py restart # Restart CraftBot python service.py logs # View recent logs ``` Main goal of the service: 1. The service continues running in the background even if the user closes the terminal or CMD, so CraftBot does not stop. 2. Once started, the server keeps running in the background even if the system is locked or the user logs out. 3. sdded desktop shortcut feature
The installation is failing because the Japanese path (デスクトップ) breaks the PowerShell command. Adding a Unicode path handler to resolve this issue.
…d-party message handling - WhatsApp: graceful shutdown preserving sessions, stale Chromium cleanup, longer timeouts - Telegram: queue-based sending via live client, @username resolution, conversation history recording - Third-party messages: stronger "DO NOT ACT" prompt, forward to preferred platform - Platform routing: distinguish telegram_bot vs telegram_user for correct send action
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.