Add Shade Tree Grove to an agent.
Run one local Proxy, then give its route to one agent process.
1. Install
Requires Node.js 20 or newer, npm, and a local Tor SOCKS port.
npm install --global git+https://github.com/dmarzzz/shade-tree-node.git
This installs the current research preview from GitHub. It is not an npm registry release.
2. Get an access profile
A Grove operator supplies the current member secret or enrollment path, the Elder Tree onion, its raw 64-hex Canopy signer, your tier, and the member-set input for your admission path. There is no public v4 profile yet.
3. Start the local route
First load the bearer secret into this shell. Paste it after running the command, then press Enter:
read -s SHADE_TREE_SECRET && export SHADE_TREE_SECRET
The secret is not echoed or placed in the Proxy's process arguments. For invited access, save the operator's member list as members.json, then start the Proxy with system Tor on port 9050:
SHADE_TREE_MEMBERS_FILE=./members.json \
shade-tree proxy \
--bootnode <elder.onion> \
--dir-signer <64-hex-canopy-signer> \
--limit <operator-tier> \
--leaf-source invited \
--tor-port 9050
Tor Browser usually listens on 9150. Staked and paid profiles use the contract and RPC values supplied by the same operator.
4. Launch the agent
shade-tree run -- your-agent
The wrapper gives proxy variables only to its child. For Hermes, replace your-agent with hermes. Software that ignores proxy variables can use http://127.0.0.1:8888 directly.
Current boundary
The Proxy accepts HTTP CONNECT and the node permits target port 443. TLS stays between the agent and destination. The serving node still sees the target hostname, timing, lifetime, and traffic volume.