Ricochet
Bring Ricochet agents to the interfaces teams already use.
Work from VS Code,Terminal,Telegram,Swarm,Ether,MCP,BYOK with one local-first agent: reviewable edits, orchestration, remote control, and model routing stay under your control.
Installs the Ricochet extension into VS Code, Cursor, and Windsurf from the latest GitHub Release.
curl -fsSL https://grik.io/ricochet/install | shCross Channel
const session = ricochet.session(repo)
await session.start({ interface: "vscode" })
// Hand off without losing context
session.on("telegram.voice", async (note) => {
const task = await ether.transcribe(note)
await swarm.delegate(task, { workers: 4 })
})
// Tools and models stay user-owned
await mcp.use(["github", "postgres", "browser"])
await models.route({ byok: true, tier: "free" })
One session across every developer interface
Repo context, approvals, tools, and model routing move together.
Start anywhere
Open Ricochet from VS Code, terminal, or Telegram.
Hand off without losing context
Ether keeps voice, progress, and approvals attached.
Coordinate Swarm workers
Split bounded work and merge through one coordinator.
Use MCP tools
Reach GitHub, databases, browser, APIs, and local tools.
Bring your own model
Use BYOK, compatible endpoints, or Grik-hosted credits.
Try Cloud Free
Get free credits, device linking, and remote sessions.
One agent layer across editor, terminal, and phone.
Ricochet is not a hosted IDE. The core stays local, while Grik Cloud adds identity, credits, and remote control when the workflow needs them.
Local agent core
A Go sidecar reads the workspace, plans changes, applies scoped patches, runs commands, and keeps the review loop inside your repo.
Swarm workers
Independent work can be split into bounded workers, then merged back through the coordinator with a clear handoff.
Ether remote control
Telegram, Discord, voice messages, progress updates, and remote approvals let the same session continue when you leave the IDE.
MCP hub and skills
Connect GitHub, databases, browser automation, local skills, project rules, and other Model Context Protocol tools.
BYOK plus Grik Cloud
Use your own provider keys for open-source local work, or connect Grik Cloud for account billing, credits, and hosted provider access.
See Ricochet at work.
One agent across your IDE, terminal, and phone. Pick a task and keep it moving through the same session.
Understand
Understand your codebase
Ask how files, dependencies, services, and behavior fit together before changing anything.
Refactor
Refactor large codebases
Make coordinated multi-file changes while Ricochet keeps patches reviewable and checks close to the repo.
Automate
Automate recurring work
Use CLI, Swarm, MCP, and Cloud sessions for recurring checks, scheduled tasks, and remote follow-up.
Questions before installing.
The short version: Ricochet is local-first, open-source, and Cloud is optional.
What is Ricochet?+
Ricochet is an AI coding agent for VS Code with a local Go core, a React webview, and optional Grik Cloud control for remote sessions.
How is it different from Cursor, Copilot, Cline, or Claude Code?+
Those products focus on editor chat, IDE forks, or single-session agents. Ricochet is built around local autonomy plus remote control, so the same session can continue from VS Code, Telegram, or voice.
Do I need Ricochet Cloud?+
No. BYOK local development should work without Cloud. Cloud is for Grik account login, credits, Telegram linking, voice, and shared control-plane features.
Can I bring my own API keys?+
Yes. BYOK remains the open-source path. Grik credits are for teams or users who want hosted providers and shared billing.
What keeps it from breaking the repo?+
Ricochet uses scoped patches, checkpoints, project checks, and explicit handoff summaries. The goal is to reduce interrupt work without bypassing developer review.
Start in VS Code. Continue from terminal or phone.
Install Ricochet, keep the repo local, use BYOK models, and connect Grik Cloud when you want Ether, Telegram, voice, or shared credits.