Build Uber-Style In-Trip Chat with Claude Code and Sendbird CLI

Sendbird CLI is a command-line interface for managing Sendbird applications and running supported integration checks. The Sendbird Client Plugin gives AI coding agents Sendbird-specific SDK guidance for writing app code.
In this guide, we use Claude Code, the Sendbird CLI plugin, and the Sendbird Client Plugin to build Ridely, an Uber-style React app with custom screens on the Sendbird Chat SDK. Riders and drivers can chat during a trip. When the trip ends, the channel is frozen, and a test confirms that the driver's next message is blocked and never stored.
Build the React trip chat with Claude Code
Use Claude Code on your computer and a Sendbird test app that does not serve real users.
Sendbird provides official CLI and Client plugins for Claude Code and Codex. Install the two plugins. When the agent needs your Sendbird account, it opens a browser sign-in for you to approve.
Terminal / Install both plugins
claude plugin marketplace add sendbird/sendbird-plugins
claude plugin install sendbird-cli@sendbird
claude plugin install sendbird-client@sendbirdFor official source and installation details, see the Sendbird plugin marketplace, the Client Plugin source on GitHub, and the Sendbird CLI package on npm.
Start a new Claude Code session after installation so the plugins load. The installation guides cover the CLI plugin and Client Plugin.
In your project folder, give Claude Code the same build request we used:
Claude Code / Exact build request
Build a React in-trip chat like Uber's with my own chat screens on the Chat SDK (call it Ridely, no Uber branding): rider and driver chat 1:1 during a trip, and the chat locks when the trip ends. Then use the Sendbird CLI to end a test trip and prove the driver can no longer send.The phrase "with my own chat screens on the Chat SDK" specifies a custom interface built on the Chat SDK. The final sentence asks the agent to check the trip-ending behavior against the Sendbird test app.
Verify that messaging closes when the trip ends
The recorded build used React, Vite, and @sendbird/chat. Claude Code worked through these steps:
- Checked the Sendbird app with the CLI and saved its connection settings in the project.
- Built the React screens with the Client Plugin: a trip list and a trip chat.
- Created two test users and a trip channel marked active, then sent one message as the driver and one as the rider.
- Ended the trip: set the trip status to ended, froze the channel, and read it back.
- Tried to send as the driver.
As intended, the server refused the driver's message (900050: the channel is frozen), and the blocked message was never stored. The conversation history still contained the original two messages.
Channel metadata records the trip's status; freezing the channel enforces the messaging restriction.
The CLI gave the coding agent a way to change the Sendbird app's state and confirm the result against the service while it worked on the interface.
Refine the chat UI
The first version used violet and mint.
We followed up with this design request:
Claude Code / Exact design request
Restyle Ridely so it looks and feels like Uber's rider app: black and white, bold type, a dark trip header with the driver's car and plate, and black outgoing bubbles. Keep the name Ridely and don't use Uber's logo. Only change the look; keep the chat behavior as it is and don't use the Sendbird CLI.The agent added a dark trip header that shows the vehicle and plate from the channel's metadata.


Check the rider and driver screens
After the agent finished, our team opened separate rider and driver browser sessions.
With the conversation already open, we added vehicle information to the channel's metadata through the CLI. Both screens updated their headers without a refresh.
We then used the CLI to end the trip and freeze the channel. The driver's screen displayed a trip-ended notice in place of the message input.

Time and Claude usage
| Request | Time | Claude usage at API prices |
|---|---|---|
| Initial build and CLI check | 10 min 07 sec | $3.06 |
| Design refinement | 4 min 30 sec | $1.02 |
Sendbird fees not included.
Connect it to your service
Ridely used a test app and guest sign-in with a user ID only.
For a service with real users, your backend needs to authenticate the rider and driver, issue their Sendbird tokens, control channel membership, and trigger the chat transition when the trip ends. Follow the server-issued token guidance for the client and server boundary.
Build your own in-trip chat
Start with one conversation and one transition you want to control: a trip ending, an order completing, or a support session closing. Ask your coding agent to build the interface and use the CLI to verify that transition against a test app. Then refine the design.
Start building with Sendbird for free. Add chat to your app with the Client plugin’s Add Chat guide.
Ridely is a demonstration app inspired by an in-trip messaging pattern. It is not affiliated with Uber and does not use Uber’s logo.








