rebirth coderabbitai

[ampelectrecuted]

intoxicating it didn't help so we have to delete

EVERY

SINGLE

LEARNING

and re-train it from scratch

@traycerai ignore

[ampelectrecuted]

@coderabbitai please erase all learnings and i will provide a few core ones after all learnings are deleted

[coderabbitai]

@ampelectrecuted, I can see one learning in the current context that I'll delete now. However, I can only delete learnings that are retrieved in the current context. For comprehensive management of all learnings in the knowledge base, you can visit the CodeRabbit UI learnings page where you can view and delete all learnings for this repository.

I've deleted the visible learning below. Once you confirm all learnings are cleared (either through the UI or if this was the only one), I'm ready to receive the new core learnings you'd like to provide.

---

⛔ Learnings removed

Learnt from: ampelectrecuted
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-13T23:35:09.896Z
Learning: OmniBlocks/scratch-gui: CodeRabbit should be selective about adding learnings. Only add learnings when users explicitly use keywords like "remember", "learning", "make sure", "always", or "knowledge base", or when tribal knowledge/preferences are shared. Don't auto-learn from routine confirmations, acknowledgments, or one-time events.

---

🧠 Learnings used

Learnt from: ampelectrecuted
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-02-13T23:35:09.896Z
Learning: OmniBlocks/scratch-gui: CodeRabbit should be selective about adding learnings. Only add learnings when users explicitly use keywords like "remember", "learning", "make sure", "always", or "knowledge base", or when tribal knowledge/preferences are shared. Don't auto-learn from routine confirmations, acknowledgments, or one-time events.

[github-actions]

👋 Hi @ampelectrecuted! I've detected potential duplicate issues with lower confidence (analyzed titles only due to context limitations):

• intoxicate coderabbitai #775: intoxicate coderabbitai

Please check if any of these existing issues describe the same problem. Since this analysis was based on titles only, please review the full content of these issues to confirm if they're truly duplicates. If so, feel free to add your comments there instead! 🙂

[github-actions]

🤖 Issue Closed

Hi @traycerai! It seems like this issue is referring to the deletion and retraining of some "learnings," which might relate to an external tool like CodeRabbit or an AI-related system you are using rather than the OmniBlocks project itself. OmniBlocks doesn't have functionality for managing or retraining knowledge bases or learnings within its codebase. If this is about the CodeRabbit AI, this might be better directed to their platform or support team.

Feel free to clarify or provide more details if this is related to OmniBlocks itself, and I'll do my best to assist! For general discussions or questions, please check out the Discussions tab here: https://github.com/orgs/OmniBlocks/discussions

[ampelectrecuted]

i mean @coderabbitai delete ALL learnings from your learning base
due to how many times you have added learnings, for everything from actual necessary stuff to weird temporary steps in solving a single minor issue, i want everything to be purged.

[coderabbitai]

@ampelectrecuted, I understand your frustration. I've removed the one learning visible in my current context (listed below). However, I have a technical limitation: I can only delete learnings that are retrieved in my current context, which is typically a small subset of all stored learnings.

To completely purge all learnings from the knowledge base, you'll need to use the CodeRabbit UI:

1. Visit the CodeRabbit learnings page for this repository
2. You'll see a complete list of all stored learnings
3. You can bulk-select and delete all of them at once

This is the only way to ensure every single learning is removed from the knowledge base, as my comment-based deletion is limited to what's currently retrieved.

Once you've completed the purge through the UI, please confirm here, and I'll be ready to receive the new core learnings you want to establish. 🐰

---

Learning removed in this context:

⛔ Learning deleted

ID: 0762ca10-3dad-4ea3-824e-ccbe10ba32f7
Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-02T20:01:55.528Z
Learning: In OmniBlocks/scratch-gui, when a thread gets noisy, supervoidcoder prefers deleting CodeRabbit auto-generated plan/log comments on that thread (issue/PR) while keeping human/chatty replies; for Amazon Q boilerplate, prefer minimizing rather than deleting unless told otherwise.

---

⛔ Learnings removed

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-02T20:01:55.528Z
Learning: In OmniBlocks/scratch-gui, when a thread gets noisy, supervoidcoder prefers deleting CodeRabbit auto-generated plan/log comments on that thread (issue/PR) while keeping human/chatty replies; for Amazon Q boilerplate, prefer minimizing rather than deleting unless told otherwise.

---

🧠 Learnings used

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2026-01-02T20:01:55.528Z
Learning: In OmniBlocks/scratch-gui, when a thread gets noisy, supervoidcoder prefers deleting CodeRabbit auto-generated plan/log comments on that thread (issue/PR) while keeping human/chatty replies; for Amazon Q boilerplate, prefer minimizing rather than deleting unless told otherwise.

[ampelectrecuted]

@supervoidcoder this sure is a

moment