Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

channel ID #7

Open
sigdie22 opened this issue May 15, 2023 · 1 comment
Open

channel ID #7

sigdie22 opened this issue May 15, 2023 · 1 comment

Comments

@sigdie22
Copy link

with the same config.js used in windows (working), it presents this error. in the config that I created from scratch in linux it presents the same error. thank you very much if you can help me! Error:
"found 0 vulnerabilities
Slaude is running at http://localhost:5004
Your CHANNEL might be wrong, please make sure you copy the channel ID of a channel you and Claude both have access to, like #random.
It looks like you might have put Claude's DM channel ID into the CHANNEL setting"

@PandarusAnon
Copy link
Owner

If your console said "found 0 vulnerabilities" that might be the problem. I know this is not exactly ideal but it should say it's found 3 vulnerabilities. See #4 for reference.

If you didn't run npm audit fix yourself the likely other reason is that your node or npm is massively outdated. Make sure you got the latest version of both, then run npm install again.

The warning about the channel ID might just be false positive but I'd double check it anyway. The only way these two warnings can trigger under normal circumstances is if you put something starting with a "D" into the CHANNEL field. I frankly don't see how they could get falsely triggered by outdated node the incorrect express package but I can't rule it out either.

Pasting the Claude DM channel ID into the CHANNEL field instead of an actual channel ID from a channel like #random or #general used to be a common mistake when switching from Spermack to Slaude as Spermack posted messages directly to Claude as DMs, whereas Slaude creates threads in any Slack channel where it's configured to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants