bode proxy

The local half of bode.

bode proxy is one small program you run on your own machine. It lets the HTTP block reach APIs your browser isn’t allowed to, and lets the Builder use Claude Code - without an API key ever going into a web page.

Reach any API

/fetch

A browser may only call sites that invite it to - that’s CORS. The proxy has no such limit, so HTTP Request sends through it instead of failing on an API that never expected a browser.

Build with AI

/ai

The Builder’s chat is a claude session, started by the proxy with the Claude Code you’re already signed in to. That’s why bode never asks for a key.

Running in a minute.

  1. 01

    Download it and run it

    No installer and nothing else to install - it’s one file.

    terminal
    curl -fsSLo bode-proxy-darwin-arm64 https://usebode.com/download/bode-proxy-darwin-arm64
    chmod +x bode-proxy-darwin-arm64
    ./bode-proxy-darwin-arm64

    Downloaded in a browser instead? macOS quarantines it: run xattr -d com.apple.quarantine bode-proxy-darwin-arm64 first.

  2. 02

    It prints a token

    Every start makes a fresh one, unless you fix it with --token.

    ╭─ bode-proxy ────────────────────────────── 2026.10.14 ─╮
    │  address   http://127.0.0.1:8787                       │
    │  token     3f9c0b7e…a41d                               │
    │  origins   any localhost port  ·  https://usebode.com  │
    │  claude    2.1.311                                     │
    ╰────────────────────────────────────────────────────────╯
  3. 03

    Tell bode where it is

    Paste the address and token into bode’s proxy settings. That’s it.

Built to be a boundary.

A program that fetches URLs on your behalf is worth guarding twice. These are the rules it enforces.

Only this machine

It listens on 127.0.0.1, so nothing else on your network can reach it. Nobody hosts it but you; you start it, you stop it.

A token and an allowed site

Nothing works without the token it printed, and a call must come from bode itself, from localhost, or from a site you named with --origin.

Not your private network

It refuses to fetch private and local addresses - your router, your other machines, cloud metadata - from a list that’s tested against both of bode’s HTTP paths.

Logs the URL, nothing else

Every request and every refusal is logged by URL and reason. Never headers, never bodies - those are where your credentials are.

Nothing to audit but itself

Written in Go with only the standard library: no dependency tree, and one build per platform with no runtime to install.

Says what it is

Ask it and it reports its version and what it serves, and bode shows that beside the download - so an out-of-date proxy is something you can see, not something you have to guess.

Every platform

  • macOS · Apple Siliconbode-proxy-darwin-arm64 Download
  • macOS · Intelbode-proxy-darwin-amd64 Download
  • Linux · x86-64bode-proxy-linux-amd64 Download
  • Linux · ARMbode-proxy-linux-arm64 Download
  • Windows · x86-64bode-proxy-windows-amd64.exe Download

Options

--port 8787Which port to listen on.
--token secretA fixed token, instead of a fresh one each start.
--origin https://…Another site allowed to call it. Repeat it for more.
--versionPrint the version and exit.

Each has an environment variable too - BODE_PROXY_PORT, BODE_PROXY_TOKEN and BODE_PROXY_ORIGINS. A flag wins, except --origin, which adds to the list.