opentrench
Getting started
1 · Install 2 · Discord 3 · Telegram 4 · Channels 5 · J7 feed 6 · Using it 7 · Share with friends
Help
Set up with Claude Host a relay Troubleshooting Ask on Discord

Getting started

About ten minutes end to end. Install the app, connect the accounts you already have, pick the channels you care about.

01Install

The app is self-contained: you do not need Node, npm, git or anything else. Those only come up if you build from source, or set up the Discord plugin by hand (there is a one-click way now, see step 2).

  1. Download from GitHub releases. The page lists several files; you want exactly one:
    Your machineFile
    Mac with Apple Silicon (M1, M2, M3, M4 · any Mac from 2020 on)opentrench-x.y.z-arm64.dmg
    Mac with an Intel chip (2019 or older)opentrench-x.y.z.dmg (no arm64 in the name)
    Windowsopentrench-Setup-x.y.z.exe
    Not sure which Mac? Apple menu → About This Mac: "Chip: Apple M…" is Apple Silicon, "Processor: Intel…" is Intel. Ignore the .zip, .blockmap and .yml files: the app uses those to update itself.
  2. Mac: open the dmg and drag opentrench to Applications. The build is signed and notarized, so it opens like any app.
    Windows: run the installer. It isn't code-signed yet, so SmartScreen warns once: click More info → Run anyway.
  3. Open opentrench. A three-step checklist greets a fresh install (Discord, Telegram, channels); it is the same as the next three sections here. Updates are checked on start and installed from inside the app.
Rather have someone walk you through it? Set up with Claude below.

02Connect Discord

opentrench talks to Discord through a small plugin inside your own Discord app, loaded by Vencord or BetterDiscord. It reads the channels you watch and sends for you using Discord's own functions, so to Discord it is simply you using Discord. No token is pasted or stored anywhere. Discord has to be open for the Discord side of the feed to work.

One click (opentrench 0.8.8 and later)

  1. In opentrench, ⚙ → Accounts → Discord → Set up Discord. The same button sits in the first-run checklist and in the app menu (Set up Discord Plugin…).
  2. Pick Vencord or BetterDiscord in the dialog (whichever you already use; Vencord if neither). opentrench quits Discord, installs it with the opentrench plugin already switched on, and reopens Discord. Nothing else to install.
    Mac, first time: macOS asks before one app may change another. If opentrench reports that macOS blocked it, open System Settings → Privacy & Security → App Management, switch on opentrench, and press the button again. The dialog offers to open that pane for you.
  3. The discord pill in the top bar turns green within a few seconds and ⚙ → Accounts shows your name.
Already running Vencord? It is replaced by opentrench's copy: the same Vencord plus this one plugin, with your settings and plugins kept. Already running BetterDiscord? It stays as it is, with this plugin added. Picking one removes the other from Discord, and once you are connected, switch to BetterDiscord (or switch to Vencord) in ⚙ → Accounts → Discord swaps them in one click. remove the plugin in ⚙ → Accounts → Discord puts Discord's original files back. Discord occasionally replaces its own files in an update; if the pill goes red afterwards, press the button again.

By hand, with BetterDiscord

BetterDiscord loads plugins as single files, so this is quick. With BetterDiscord installed, download OpentrenchBridge.plugin.js, open User Settings → BetterDiscord → Plugins → Open Plugins Folder, drop the file in, and switch OpentrenchBridge on. If opentrench isn't on port 3210, set the port in the plugin's settings (the gear next to it).

By hand, with Vencord

For an older opentrench, a Discord installed somewhere unusual, or if you prefer to build the plugin yourself. Vencord loads third-party plugins only from a source build, so these steps install a few developer tools first. Once.

  1. Install the tools. Open Terminal (⌘-Space, type Terminal) and paste each line, pressing Return after each. The first one shows a dialog: click Install. 
    xcode-select --install
curl -fsSL https://fnm.vercel.app/install | bash
source ~/.zshrc
fnm install 22 && fnm use 22
npm install -g pnpm
  2. Get Vencord and add the plugin. 
    cd ~/Documents
git clone https://github.com/Vendicated/Vencord
cd Vencord
pnpm install --frozen-lockfile
mkdir -p src/userplugins
git clone --depth 1 https://github.com/frogeth/opentrench /tmp/opentrench
cp -r /tmp/opentrench/vencord/opentrench-bridge src/userplugins/
  3. Build and inject. When asked which Discord to patch, pick the one you use and confirm. 
    pnpm build
pnpm inject
  4. Turn it on. Quit Discord fully (⌘Q) and reopen it. User Settings → Vencord → Plugins → find OpentrenchBridge and switch it on.
  5. Done. Open opentrench: the discord pill in the top bar turns green within a few seconds and ⚙ → Accounts shows your name.
  1. Install the tools. Open PowerShell (Start, type PowerShell) and paste each line, pressing Enter after each. Close and reopen PowerShell after the second line. 
    winget install --id Git.Git -e
winget install --id OpenJS.NodeJS.LTS -e
npm install -g pnpm
  2. Get Vencord and add the plugin. 
    cd $HOME\Documents
git clone https://github.com/Vendicated/Vencord
cd Vencord
pnpm install --frozen-lockfile
mkdir src\userplugins -Force
git clone --depth 1 https://github.com/frogeth/opentrench $env:TEMP\opentrench
Copy-Item -Recurse $env:TEMP\opentrench\vencord\opentrench-bridge src\userplugins\
  3. Build and inject. When asked which Discord to patch, pick the one you use and confirm. Allow it if Windows asks. 
    pnpm build
pnpm inject
  4. Turn it on. Quit Discord fully (tray icon → Quit Discord) and reopen it. User Settings → Vencord → Plugins → find OpentrenchBridge and switch it on.
  5. Done. Open opentrench: the discord pill in the top bar turns green within a few seconds and ⚙ → Accounts shows your name.
Built before copying the plugin? Run pnpm build again in the Vencord folder and restart Discord. The plugin folder must sit at Vencord/src/userplugins/opentrench-bridge.

Already using a token?

Nothing breaks. Your feed keeps reading through the token; sending on that path is off. Once the plugin connects, opentrench switches to it and closes the token session. Then remove the token in ⚙ → Accounts → Discord.

03Connect Telegram

Telegram uses your own account through Telegram's official API, which Telegram allows. It needs an API id and hash, which takes a minute.

  1. Go to my.telegram.org and log in with your phone number and the code Telegram sends.
  2. Open API development tools. Any app title and short name (say opentrench), leave the rest, Create application. Copy the api_id and api_hash.
  3. In opentrench, ⚙ → Accounts → Telegram: paste both, Save credentials.
  4. Enter your number in international format (+15551234567) → Send code. The code arrives in your Telegram app, not by SMS. Enter it, and your two-step password if you have one.

The telegram pill turns green and stays logged in across restarts.

04Add channels

  1. Click the round + at the bottom of the left rail.
  2. Pick Discord or Telegram, browse your servers and chats, tick the ones to watch. Click a name first to preview its recent history.
  3. Each server and chat becomes an icon in the rail. Drag to reorder. Click one to focus on it, click ★ to get back to everything.

05J7 feed (optional)

Add J7Tracker's live tweet feed as a column, right next to your calls. Tweets that mention a token you're already tracking get a highlighted strip, and tokens launched off a tweet on pump.fun or Pons show up under it within seconds.

This reads J7 with your own J7 session, so you need a J7Tracker account you're logged into. It's read-only and unofficial: if J7 changes their site it can stop working, and you'd just paste a fresh session id.
  1. Open j7tracker.io in a browser and make sure you're logged in.
  2. Open DevTools. F12, or Cmd+Option+I on a Mac, then go to the Application tab (it may be hidden under the » menu).
  3. Find the session id. In the left sidebar under Storage → Local Storage, click https://j7tracker.io. Find the row named sessionId and copy its value.
  4. Paste it into opentrench. ⚙ → Accounts → J7Tracker → paste the session id → Save & connect. The status turns to connected.
  5. Add the column. The + at the right end of the terminal → pick J7. Tweets stream newest first.

In the column: ★ on any account to get a sound and a notification whenever it tweets. Right-click a contract in a tweet for the usual Buy / Research / Open token menu. The launches line under a tweet is filled in automatically for tokens deployed off it.

06Using it

The terminal
  • All Calls: one card per token, newest call first. Gold 1st for a first call, a 🔥 count when several chats called it, market cap at the call and the multiple since. Click the address to copy it.
  • All Chats: the raw messages, read bottom-up. Every contract becomes a token strip with a live chart. Click a message's chat chip to open that channel.
  • Pings: the @ button in the top bar. Everyone who mentioned you, with the messages before and after, jump-to-chat and reply.
  • Drill-down: click a token's picture, or right-click any contract → Open token. Candles on a market-cap axis with every caller pinned.
  • Columns: the + at the right end adds one: calls, chat, Top Callers, Cove, Salpha or J7, scoped to any channels, with filters and its own alert sound. Drag the grip to reorder, the edge to resize.
  • Favorites: ⋯ next to a name → Favorite caller. They get a crown and their first calls ping you.
  • Bots: ⚙ → Feed → Bots decides which bots show, which count as calls, and which may ping you.

07Share calls with friends

⚙ → Together → Create a room: give it a name, paste a relay address (there is no official relay: host your own, see Host a relay, or use a friend's; the field remembers the last relay you used), press Copy invite and send the link. Your friends click it, or paste it under Join a room, and from then on each other's calls show in the feed marked via <name>. Only calls travel, never chat messages or market numbers, and every one is encrypted on your machine with a key that lives in the invite, so the relay cannot read it.

The full story, rotating an invite, hosting your own relay and what the status words mean: Share calls with friends. Sharing on the same Wi-Fi with no relay at all is still there, under Same Wi-Fi instead on the same page.

Set up with Claude

If you use Claude Code or the Claude desktop app, opentrench ships a skill: a page of instructions Claude follows to walk you through installing, connecting Discord and Telegram, adding channels, and the usual things that go wrong. Claude does the explaining; you do the clicking.

  1. Add the skill. In a terminal (Mac: ⌘-Space, Terminal; Windows: PowerShell), paste: 
    git clone --depth 1 https://github.com/frogeth/opentrench /tmp/opentrench
mkdir -p ~/.claude/skills
cp -r /tmp/opentrench/skills/opentrench-setup ~/.claude/skills/
    No git? Open the skill on GitHub and paste its text into any Claude chat instead.
  2. Ask. Open Claude Code and say "set up opentrench", or "my discord pill is red", or whatever you are stuck on. The skill knows which installer file you need, the one-click and by-hand Discord paths, the Telegram API steps, and where the app keeps its files and logs.
The skill is a plain text file you can read: skills/opentrench-setup/SKILL.md in the repository. It never touches your accounts; it only tells Claude how opentrench works.

Troubleshooting

  • The discord pill stays red. Is Discord open, and is OpentrenchBridge switched on in the plugin list (User Settings → Vencord → Plugins, or BetterDiscord → Plugins)? One-click install: press Set up Discord again. By hand: if the plugin isn't in the list, the build didn't include it: check the folder path, run pnpm build again, restart Discord.
  • "macOS blocked the change (App Management)". System Settings → Privacy & Security → App Management → switch on opentrench, then Set up Discord again. Vencord's own installer needs the same permission.
  • "Discord is not installed". The one-click setup looks in /Applications (Mac) and the per-user install under %LOCALAPPDATA% (Windows), for Discord, PTB and Canary. A Discord living elsewhere needs the by-hand steps.
  • Vencord isn't in Discord's settings. One click: press Set up Discord again. By hand: pnpm inject didn't patch the Discord you run; run it again and pick the right one.
  • Discord updated and Vencord stopped loading. One click: press Set up Discord again. By hand: run pnpm inject again in the Vencord folder.
  • Different port. If opentrench's web page isn't on 3210, set the port in the plugin's settings (Vencord → Plugins → OpentrenchBridge → gear). The one-click install sets it for you.
  • "npm: command not found", "make", missing dependencies. You are following the from-source instructions. Unless you are changing the code, don't: download the app instead (step 1). The app needs nothing installed.
  • Updating the plugin. When release notes mention it: in the Vencord folder, copy the plugin again, pnpm build, restart Discord.
  • Is this allowed? Client mods sit outside Discord's terms. Vencord has a very large user base and Discord hasn't banned for it. A self-bot, a separate program with your token, is what Discord's detection targets, which is why opentrench moved away from it.