GitHub, without opening GitHub.
Turn a bug someone described in chat into an issue on the repo.
- Free to start
- No card
- Every write waits for you
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own GitHub details, and Ray takes it from there.
@Ray open an issue on the api repo about the timeout.
@Ray what is open on the api repo with the bug label?
@Ray put Marco on that issue and label it urgent.
@Ray comment on the issue that the fix went out.
What Ray can and cannot do in GitHub
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
20 reads wired, 5 actions that wait for a human.
Runs on its own
What Ray reads in GitHub
- Issues and their comments
- Repositories your connection covers
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Create an issue
- Comment on an issue
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Push code, open pull requests, or merge anything
- Delete an issue or a comment
Exactly what Ray will ask you to approve.
Not a category of permission. These are the GitHub actions Ray can take, each one stopping in the thread with the real content before it happens.
- Create GitHub issue
- Update an issue
- Comment on a GitHub issue
- Add assignees to an issue
- Add labels to an issue
Create GitHub issue
Showing Title, Body, Owner, Repo, Labels and Assignees, each carrying the exact content that will land.
How Ray works with GitHub
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect GitHub
One click, right where you asked. Ray posts a connect card, you authorise GitHub with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in GitHub, and tell Dana it is being looked at.
Create GitHub issue
- Waiting on
- your approval
Ray uses GitHub together with the rest of your tools.
One ask can read GitHub, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
What does connecting GitHub to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect GitHub and it can do the GitHub part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own GitHub account, so Ray can only reach what that person can already reach, and the history in GitHub shows who actually asked.
Security and permissions
- You authorise GitHub on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect GitHub in a message, or uninstall Ray and every connection it held is revoked.
GitHub and Ray, answered
The questions teams ask before they connect GitHub. Every answer is how this integration is built rather than a promise about it.
More dev & deploys integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in GitHub.
Free to start, no credit card, and it asks before it acts.