WakaTime, without opening WakaTime.
Read-only coding activity, projects and goals for the people who connect it.
In your channel
Ask Ray for something in WakaTime and it posts this card in the thread. One click, and the task you asked for carries on where it left off.
What Ray can and cannot do in WakaTime
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in WakaTime
- Get current user status bar today
- Get goals
- Get insights
- Get user
- Get users all time since today
- Get user stats
- Get user stats by range
- Get user summaries
- List user projects
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What Ray answers with
Ray reads WakaTime and answers from it in the thread. Writing to WakaTime is not switched on yet, so there is nothing here to approve.
How Ray works with WakaTime
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect WakaTime
One click, right where you asked. Ray posts a connect card, you authorise WakaTime 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
Ray answers where you asked
Ray only reads WakaTime, so there is nothing here to approve. It looks up what it needs and replies in the thread.
Priya
@Ray the checkout bug is back. Take a look in WakaTime, and tell Dana it is being looked at.
Ray
Checked WakaTime. The spec was last edited on Tuesday and the open question about refunds is still unanswered.
What does connecting WakaTime to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect WakaTime and it can do the WakaTime 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 WakaTime account, so Ray can only reach what that person can already reach, and the history in WakaTime shows who actually asked.
Security and permissions
- You authorise WakaTime 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 WakaTime in a message, or uninstall Ray and every connection it held is revoked.
Works with these too
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in WakaTime.
Free to start, no credit card, and it asks before it acts.