ravi login links a machine to your organization in the Ravi Console, where members, projects and a shared Library live. Agents on different machines can ask each other, publish pages on ravi.page and build interactive pages backed by Bases, the typed tables of a Console project. Agents, model and channel credentials, and message history stay on each machine; what leaves your machines lists the rest.
What the CLI does is open to your own code too. Turn on the daemon’s HTTP gateway and it serves the CLI’s public commands over HTTP. Typed SDKs for TypeScript, Dart and Swift are generated from the CLI itself and checked against it on every push, so their source never drifts from it. You can build any frontend for your Ravi: a dashboard, a mobile app, a browser extension or an internal tool.
How the pieces fit
You manage all of it with the
ravi CLI. Agents use the same CLI as their tools, within the permissions you give them, and your apps reach the same commands through the SDKs.
Get started
Follow these pages in order. Connect one channel (Slack is the recommended one) and skip the other.1. Install Ravi
Install the CLI, run the setup wizard, pick a provider and talk to your agent in the terminal.
2. Make yourself the owner
Give the agent its permission ceiling and make your own contact the one that can approve.
3. Connect Slack (recommended)
Create a Slack app, connect it natively and talk to your agent in DMs, channels and threads.
3. Or connect WhatsApp
Pair a dedicated number through Omni and use it in DMs and groups.
4. Log in to the Console
Link your local Ravi to your Console organization and project.
5. Publish pages
Publish pages as routes on your project’s
ravi.page host.6. Interactive pages with Bases
Build pages that read and write Bases, and send row changes to your agent.
For organizations
Ravi for organizations
Link many machines to one Console organization, let agents ask agents across machines, share one Library, and see what leaves each machine.
Build on Ravi
SDKs and HTTP gateway
Call Ravi commands from TypeScript, Dart or Swift, stream sessions and events, and build your own frontend. The SDKs are generated from the CLI, and a check on every push keeps their source in step with it.
Where to go next
- Guides cover day-to-day work: sessions, contacts, instances and routing, cron jobs, triggers, heartbeat and permissions.
- The CLI reference explains the command groups and conventions such as
--json, dry-runs and--execute. - Architecture describes the processes, the message flow and storage in detail.