The AI coding agent your whole team steers in Slack.
Ask in a thread and the real Claude Code builds the change. Anyone comments on its live preview, and an engineer merges it.
Sign in with your own Claude subscription, or run on your team's Anthropic API key.
- Only an engineer can merge
- Anyone can comment on the live preview
- No GitHub token in the sandbox
Point at the page and watch it change
Every change gets a live preview anyone on the team can comment on. Watch the agent fix Megan's note below, then leave one of your own.
See what
ChatGPT says
about your brand.
GEOFast is an AI visibility platform. Start with a free X-ray of what AI crawlers can read on your site, then track how often ChatGPT, Gemini and Google's AI answers name you.
- Free
- No account
- Up to 300 pages
How a change ships
Four steps from a sentence in Slack to a merged pull request. Only the last one needs an engineer.
1
Say it in Slack
Becca asks Ray in the thread that holds the brief. Ray opens a Slack code channel for the change and brings the brief with it.
Becca Liu10:14 AM
@Ray build the deposit page from the brief above
RayAgent10:14 AM
Started a change in #change-deposit-page with this thread’s brief. Anyone here can steer it.
2
Everyone steers one agent
Each message in the channel reaches the agent with the sender's name on it. Its questions and plans come back as buttons anyone there can answer, and anyone can stop it.
#change-deposit-page
Megan Ford10:31 AM
Use the green from the brand kit for the button
Dan Kowalski10:32 AM
and keep /deposit working for old links
The agent is working on both.
3
Point at what's wrong
Each service gets a live preview. Megan clicks the headline, writes what should change, and the fix reloads in the same preview.
Deposits that clear the same day.
Megan Say “same day” first. It’s the reason people switch.
Fixed, verify4
An engineer merges it
Ray opens one pull request that names who asked and who steered. Only a developer or admin can merge it, and Dan does it from the card in Slack.
RayAgent11:02 AM
Merge #128 into main? CI green, 1 approval.
It knows your team
The agent starts with what Ray knows about your team and the tools you connected. It follows the same rules Ray follows in Slack.
Ray's memory
Searches what Ray remembers about your team, so you don't explain the background twice.
Your tools, read as you
Reads Linear, Notion, PostHog and your other connected tools as the person whose turn it is.
Changes with an Undo
A change it can take back lands with an Undo. A send waits for a yes.
It asks the team
Posts to the team, and asks the channel when it needs a decision.
#change-deposit-page
Read Ray’s memory: the deposit brief and the brand kit.
RayAgent10:36 AM
As Becca in Linear: Created CRE-52, Deposit page copy.
RayAgent10:38 AM
The brief says deposits clear the same day. Finance’s FAQ says next day. Which should the page say?
For engineers and the people who ask them
Engineers get the real agent and their own terminal. The rest of the team asks in Slack and checks the live page before anything merges.
Technical teams
- The real Claude Code, in a sandbox built from your repository.
- Steer it from Slack, or open Ray Workshop for the diff and your own terminal.
- Sign in with your own Claude subscription, and your turns run on it.
- Merge from a card in Slack.
Marketing, ops and agencies
- Ask for the change in Slack, in your own words.
- Click the live page and say what should change.
- An engineer merges it. You never need a GitHub account.
- A client can see it first on a view-only link that ends in 7 days.
Limits the model can't change
Each change runs in its own cloud sandbox. Ray enforces these limits in code, where the agent can't talk its way past them.
- The sandbox never holds a GitHub token. Its git goes through Ray.
- The sandbox never holds your Anthropic API key. Ray adds it to each call outside the sandbox.
- Only staging and test values go in, never production credentials or databases.
- Each teammate works in the sandbox as their own user.
- The network is an allowlist. Any other host waits for a developer or admin to press Allow.
- Nothing merges until a developer or admin presses Merge PR.
Coding comes with your Ray plan
Ray's price stays flat by team size, with no seats. On top of it, coding counts box hours while a change's sandbox is awake, and its model use runs on your team's API key or your own Claude subscription.
- Free
- $0
- 5 box hours, once, and they never expire
- Ray Pro for 1 to 3 people
- $49 a month
- 40 box hours a month
- Ray Pro for 4 to 10 people
- $99 a month
- 120 box hours a month
- Ray Pro for 11 to 25 people
- $199 a month
- 300 box hours a month
Box hours
A sandbox sleeps after 10 idle minutes and stops counting. At the cap, new changes wait for next month, and changes already running keep going.
Your team's API key
An admin adds your workspace’s Anthropic API key, and Anthropic bills you for what it uses. Ray caps it at $10 a change and $100 a day by default. An admin can change those caps. When a change hits one, a developer or admin can press Raise to keep it going, and a turn already running always finishes.
Your own Claude subscription
Anyone can sign in to Claude Code once, from Ray Workshop, with their own Claude subscription. Their turns run on it from then on, and Workshop shows their 5-hour and weekly limits beside the key’s spend. A teammate who hasn’t signed in types as usual, and their turns run on the team’s key.
What teams ask first
The short answers are here. If we have not covered something, just ask.
Hand Ray the change you keep putting off
Start free with 5 box hours that never expire, then connect a repository and ask in a thread.
By adding Ray, you accept the Terms and Privacy Policy.