Before you start
- A Business plan
- A GitHub account with access to the repositories
Steps

Open fine-grained tokens
On GitHub, click your profile photo → Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token.
Name it and choose repositories
Name it Handyva, set an expiry, pick the Resource owner (you or your organisation) and under Repository access choose Only select repositories.
Set permissions
Under Repository permissions set Issues to Read and write (or Read-only if Handyva should never open or comment), Pull requests to Read-only. Metadata is added as Read-only automatically. Leave everything else as No access.
Generate and copy
Click Generate token and copy it (it starts with
github_pat_). Organisations may need to approve the token first.Paste it on handyva.com
Go to handyva.com/connect/github (or open GitHub from the dashboard's Connections page) and paste the details into the form. Never paste keys into the Telegram chat; Handyva will tell you to change them if you do.
All set
You're sent back to handyva.com and Handyva confirms in Telegram that GitHub is connected. Try asking it something straight away.
What Handyva can access
- Read issues and pull requests in the repositories you picked
- Open issues and add comments you've approved (if you allowed write)
Handyva only uses this access to do what you ask, never shares it, and always shows you messages, replies and posts before they go out.
Disconnect
In Handyva: dashboard → Connections → Disconnect, or tell the bot “disconnect my account”. On the platform: GitHub → Settings → Developer settings → Fine-grained tokens → Handyva → Delete.
Troubleshooting
Handyva sees no repositories
Check the token's resource owner and repository list. Organisation tokens can sit in “pending” until an owner approves them.
It stopped working
Fine-grained tokens expire. Generate a new one and paste it again.
Questions
Can Handyva change my code?
No. The token only covers issues, pull requests (read) and metadata.