Bots are unable to view number of forks/stars on Github repos

Support Bug Reports
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

If you ask the bots to look at a link of github repo, or ask it to go to github to find a repo when it returns it will talk about how the repo is “untrustworthy” based on its inability to see the number of forks/stars the repo has. it can be corrected by sending it a screen shot for proof that it actually does.

i have my own internal filing system and auto mistake catch file saved on to my system if you guys would like me to get if for you guys if you cant recreate this bug. i have the bots put all mistakes/errors into a obsidian vault with its reasoning for the mistake, ways to fix the mistake so it doesnt happen in the future, what caused it, and i think a few other things. so any time an issue happens it immediately flags/saves it.

Steps to Reproduce

ask grok bot to look at github repo link or tell them to go to github to look at a repo

Expected Behavior

to not say a repo doesnt have something when it does

Operating System

Windows 10/11

Version Information

grokbot version 0.70.2

For AI issues: which model did you use?

none

Additional Information

i have the bots reasoning for what caused it if needed

Does this stop you from using Cursor

No - Cursor works, but with this issue

9

Hey @bee, thanks for the report!

We were able to reproduce this. When Grok Bot reads a GitHub repo page, the star and fork counts (and the README and file list) currently come through empty, so the bot sees “0 stars, 0 forks” even on popular repos. That’s why it called the repo untrustworthy. I’ve flagged this to the team.

In the meantime, you can ask the bot to check the numbers through the GitHub API from its computer instead of reading the web page, for example by running curl https://api.github.com/repos/OWNER/REPO. Asking it to open the repo in its browser also shows the real counts.

17

Yes, thank you.

I already have it doing that, every mistake or issue it makes I have it upload a detailed reason to why and what happened with the solution to correct it from not happening again. I even had it go back and look at every issue that has happened since I started using it and write summaries for every issue with its own fixes.

Appreciate your time.