BloumeChat RPC

Show your code editor activity on BloumeChat — in real time.

---

Let your friends and server members see what you're hacking on — without leaving your editor.

✨ Features

🚀 Getting Started

1 — Install the extension

From the VS Code Marketplace:

ext install BloumeSAS.bloumechat-rpc

Or search "BloumeChat RPC" in the Extensions panel (Ctrl+Shift+X).

From a .vsix file (latest release):

code --install-extension bloumechat-rpc-*.vsix

2 — Get your RPC token

1. Open BloumeChat and go to Settings → Desktop
2. Scroll to the Token RPC section
3. Click the copy icon to copy your token

Your token is unique to your account and never expires unless you rotate it manually.

3 — Configure the extension

Open VS Code settings (Ctrl+,) and search for BloumeChat RPC, or edit settings.json directly:

{
  // Required — your personal RPC token from BloumeChat Settings > Desktop
  "bloumechatRpc.token": "your_token_here",

  // Optional — enabled + the first three are true by default
  "bloumechatRpc.enabled": true,
  "bloumechatRpc.showFileName": true,
  "bloumechatRpc.showWorkspace": true,
  "bloumechatRpc.showFileType": true,
  "bloumechatRpc.showLineNumber": false,
  "bloumechatRpc.showProblems": false
}

The realtime endpoint is fixed to wss://api.bloumechat.com and is not configurable.

That's it. Your BloumeChat profile now shows your editor (VS Code, Cursor, Windsurf, Antigravity, VSCodium…) as your current activity, with its own name and logo. 🎉

⚙️ Configuration Reference

ℹ️ The WebSocket endpoint is hardcoded to wss://api.bloumechat.com and cannot be changed.

Status bar control

A BloumeChat RPC item lives in the status bar. Click it to Start, Reconnect, or Stop broadcasting at any time. The extension auto-starts on launch when enabled is true.

🔐 Privacy & Security

• Your token authenticates only RPC activity updates — it cannot read messages, servers, or any personal data.
• If you suspect your token was leaked, rotate it instantly in Settings → Desktop → Token RPC → Regenerate.
• The extension respects your Activity Privacy setting in BloumeChat: if set to Nobody, no activity is ever broadcast regardless of this extension.
• No file contents are ever transmitted — only the file name and workspace name.

📦 How it works

Your editor (extension)
      │
      │  Socket.IO (WebSocket)
      │  auth: { rpcToken: "..." }
      ▼
BloumeChat Server
      │
      │  activity:update event
      │  { type: "using", name: "Cursor", details: "file.ts — MyProject" }
      ▼
Your BloumeChat profile ✓

The name field is read from vscode.env.appName, so it automatically matches the editor you're actually running — "Visual Studio Code", "Cursor", "Windsurf", "Antigravity", "VSCodium", etc.

The extension opens a persistent Socket.IO connection to the BloumeChat server, authenticated via your RPC token. When you switch files or projects, it emits an activity:update event with a 5-second debounce to avoid flooding. When your editor loses focus or is closed, the activity is cleared automatically.

📄 License

© 2024–2026 Bloume.Fr — All rights reserved.

This extension is proprietary software distributed by Bloume.Fr as part of the BloumeChat platform. You may use it freely with your BloumeChat account, but you may not copy, modify, distribute, or reverse-engineer it without prior written permission from Bloume.Fr.