[FEATURE] Discord Rich Presence — let everyone see how long we've been vibe coding

Open 💬 1 comment Opened Jun 8, 2026 by JordanRO2

The pitch

I want my Discord status to publicly announce that I've been "vibe coding" with Claude Code for 4 hours straight, no breaks, probably should eat something. You know, accountability. Or shame. Same thing.

Right now my friends just see me as "Online" and have no idea I've been locked in a death match with a TypeScript error since noon. Let's fix that.

What I'm actually asking for

Optional Discord Rich Presence integration so a running Claude Code session shows up on your Discord profile — project name, model, and that glorious elapsed timer ticking up while your sanity ticks down.

Discord folded the old Rich Presence into the Discord Social SDK (overview), but honestly you don't even need the whole SDK — the classic local IPC pipe (discord-rpc) is enough to do this. Lightweight, no bot, no gateway.

What it'd look like

Claude Code
   Vibe coding in my-startup-that-will-totally-ship
   Opus 4.8 · 04:17:32 elapsed

Suggested fields:

  • Details: project / working dir name
  • State: model in use
  • Timestamp: session start (the elapsed timer is the whole point, don't take it from me)
  • Assets: Claude Code logo

The boring-but-important part

  • Off by default, opt-in via settings.json (discordRichPresence: true) or CLAUDE_CODE_DISCORD_RPC=1.
  • Talks to the local Discord client over IPC only — no bot token, no network calls to Anthropic, completely separate from the existing Discord channel plugin.
  • Privacy switches: hide the project name (show just "Coding") for when you're working on something you'd rather not flex, and a global kill-switch.

Prior art (everyone else already does this)

  • VS Code — Discord Presence extensions
  • Neovim — presence.nvim
  • JetBrains — Discord Integration

The IDEs all let people flex their coding sessions. Terminal gang deserves to flex too. :pensive:

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗