zib/Veskslop-t
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Seed client auth from token file and pin the data dir

Browse Source
This commit is contained in:
agent
2026-09-11 13:09:35 +02:00
parent 7fdc71562a
commit 2830bd1ade
6 changed files with 53 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
poc/README.md
+5 -1
View File
@@ -27,10 +27,14 @@ TOKEN_FILE=/path/to/token DEBUG=1 pnpm poc:qr
Connects to `wss://remote-auth-gateway.discord.gg/?v=2`, renders the approval QR directly in the
terminal, waits for a phone scan, exchanges the login ticket and writes the token to
`poc/.token` (mode 600, gitignored; override with `TOKEN_FILE`). No existing token required.
`poc/.token` (mode 600, gitignored; override with `TOKEN_FILE`). This is the **puppet account's**
token. No existing token required.
If Discord responds with an hCaptcha challenge, the script prints the challenge and prompts for a
`HCAPTCHA_KEY` (or takes it from the environment).
The headless client consumes this file on startup via `VESKSLOP_TOKEN_FILE` (default
`<DATA_DIR>/token`, see [../AGENTS.md](../AGENTS.md) → Auth persistence).
### 1. Vesktop control bridge — `src/control-bridge.ts`
The MCP daemon. Exposes Streamable HTTP and forwards tool calls over the JSON-lines protocol on