t1385.10: Add Nextcloud Talk bot integration subagent#2772
t1385.10: Add Nextcloud Talk bot integration subagent#2772marcusquinn wants to merge 0 commit intomainfrom
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📥 CommitsReviewing files that changed from the base of the PR and between 7e385b9 and 446034936480fa4f467f06d925f3bb1280d69a97. 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report �[0;34m[INFO]�[0m Latest Quality Status: �[0;34m[INFO]�[0m Recent monitoring activity: 📈 Current Quality Metrics
Generated on: Tue Mar 3 04:59:45 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request adds a new subagent for integrating with Nextcloud Talk bots. It provides detailed documentation and configuration instructions for setting up a bot that can interact with Nextcloud Talk through webhooks, offering features like messaging, reactions, and integration with other services like Matterbridge. The subagent emphasizes privacy and security by leveraging Nextcloud's self-hosting capabilities and encryption options. Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
|
5c8abe3 to
4460349
Compare
There was a problem hiding this comment.
Code Review
This pull request introduces a new subagent definition for Nextcloud Talk integration. The documentation is comprehensive, covering architecture, setup, security, and usage examples. My review focuses on improving the robustness of the provided bash script examples. I've suggested changes to the signature verification and user allowlist functions to make them more resilient to edge cases and safer in practice.
Note: Security Review has been skipped due to the limited scope of the PR.
| local body="$4" | ||
|
|
||
| local expected | ||
| expected=$(printf '%s%s' "$random_header" "$body" | openssl dgst -sha256 -hmac "$secret" -hex | awk '{print $2}') |
There was a problem hiding this comment.
The use of awk '{print $2}' to extract the HMAC signature is a bit fragile as it assumes the signature will always be the second space-separated field in the openssl dgst output. While this is often true, the output format can vary between openssl versions or configurations. A more robust approach is to extract the last field, for instance using sed 's/.* //' which will work regardless of the number of fields before the signature.
| expected=$(printf '%s%s' "$random_header" "$body" | openssl dgst -sha256 -hmac "$secret" -hex | awk '{print $2}') | |
| expected=$(printf '%s%s' "$random_header" "$body" | openssl dgst -sha256 -hmac "$secret" -hex | sed 's/.* //') |
| check_allowed() { | ||
| local sender="$1" | ||
| local user | ||
| for user in ${ALLOWED_USERS//,/ }; do | ||
| if [ "$user" = "$sender" ]; then | ||
| return 0 | ||
| fi | ||
| done | ||
| return 1 | ||
| } |
There was a problem hiding this comment.
The current implementation of check_allowed uses a for loop over a space-separated string, which relies on word splitting. This is not fully robust as it could fail if user IDs contain spaces or other characters present in IFS. A safer and more concise method is to check for the substring within a comma-delimited list. This avoids word splitting issues and also prevents partial matches (e.g., a user 'dev' matching 'developer1'). The function's exit code will correctly reflect the result of the check.
| check_allowed() { | |
| local sender="$1" | |
| local user | |
| for user in ${ALLOWED_USERS//,/ }; do | |
| if [ "$user" = "$sender" ]; then | |
| return 0 | |
| fi | |
| done | |
| return 1 | |
| } | |
| check_allowed() { | |
| local sender="$1" | |
| # This safely checks if the sender is in the comma-separated ALLOWED_USERS list. | |
| [[ ",${ALLOWED_USERS}," == *",${sender},"* ]] | |
| } |
4460349 to
7e385b9
Compare
|
This PR was superseded by the batch merge in PR #2771 (feat: t1385 — add 11 chat platform integration agents), which merged all the content from this branch. Closing as the content is already in main. |



Summary
.agents/services/communications/nextcloud-talk.mdcovering the Nextcloud Talk Bot API (webhook-based, OCC CLI registration)Closes #2757