REZO — Team Messaging That Lives on Your Code

Drop a comment on any line. Your teammates see it as a native review thread, exactly where the code is. No sidebar. No tab switching. No comments in git.

What's new in 2.0

• Native comment threads, not source-file edits. v1 inserted a // ===== REZO HISTORY ===== block into your file. v2 renders every message as a real VS Code comment thread on the line it was sent against — the same UI Pull Request review uses. Your source files never change.
• Persistent rooms. Default room lifetime is 24 hours (was 35 minutes). Configurable from 5m to never.
• Presence. Status bar shows how many teammates are in the room and who they are.
• Git context. Every message records the commit SHA + branch it was sent from. You can tell at a glance "Alice flagged this on feat/login @ abc1234".
• Replies in-thread. Hit the native "Reply" button on a comment thread — the reply lands on the same line, chained to the parent.

Zero setup. Just install and go.

1. Install the extension
2. Ctrl+Shift+P → REZO: Create New Room
3. Share the code (e.g. REZO-7K9P) with your team
4. They run REZO: Join Room by Code
5. Done

No account. No Firebase setup. No API keys (AI ships with a built-in free Groq key).

How a message flows

You select code on line 42 of utils.ts → Ctrl+Shift+S
   ↓
Message saved to the room with file=utils.ts line=42 + git commit
   ↓
Teammate sees a comment thread appear at utils.ts:42 inside their editor
   ↓
They click "Reply" → conversation continues, all on the same line

No comment block is ever inserted into the file. If a teammate doesn't open utils.ts, the thread is just waiting in the room — they'll see it the moment they open the file.

Keyboard Shortcuts

Status Bar

• 💬 REZO: REZO-7K9P · 3 online — connected, three teammates present
• 💬 REZO: REZO-7K9P (2) · 3 online — two unread, three online
• 💬 REZO: No Room — click to create

Hover the status bar to see who is online.

Rooms

• Format: REZO-XXXX (4 uppercase alphanumeric chars)
• Default expiry: 24 hours of inactivity — configurable via rezo.roomExpiry
  • 5m 35m 1h 4h 24h 7d never
• Anyone with the room code can join — choose code distribution accordingly

AI Assistant

Built-in. Works out of the box (no key needed) via a shared Groq free tier. Add your own keys for higher limits.

Slash commands:

• /explain <code> — plain English explanation
• /test <code> — generate unit tests
• /refactor <code> — cleaner, idiomatic version
• /fix <code> — find and fix bugs

Fallback chain: Groq (built-in) → Gemini → DeepSeek → Groq (user key).

Vault — Personal Cloud Storage

Save important snippets to your private vault. Persists forever (unlike rooms). Access from any machine signed in with the same display name.

• Ctrl+Alt+B save selection
• Ctrl+Shift+B browse / insert / delete

Privacy & Security

• All messages flow through a shared Firebase Realtime Database
• No accounts; identity is just a display name
• Rooms auto-delete after their configured expiry
• Do not share sensitive credentials in REZO rooms — the backend is shared infrastructure

Roadmap note: the Firebase + Groq keys currently ship inside the extension. A proxy server (Phase 1.1) will move these behind per-room rate limits and enable real auth. Until then, treat REZO as suitable for teams who already trust each other on shared dev tooling.

Migration from v1.x

• Old // ===== REZO HISTORY ===== blocks still in your files? Hit Ctrl+Shift+D to remove all of them at once.
• The legacy "dump room into a comment block at cursor" behavior is still available as REZO: Dump History as Comments (legacy) from the command palette.

Built By

License

MIT.

Contributing

Issues and PRs welcome. Keep patches small and focused.