Tor-compatible proxy sessions.
Default SOCKS route is socks5://127.0.0.1:9050, with profile support for other proxies.
local-first agent browser control
Agents should not browse naked.
agenTOR gives autonomous workers routed browser sessions, clean artifacts, and local receipts. Run the page. Capture what happened. Keep the trail.
why it exists
Route control for autonomous browsing.
Agent browsing is execution. agenTOR makes that execution explicit: proxy route, browser session, captured page state, screenshots, reports, and a receipt folder you can inspect after the run.
Every run leaves artifacts.
HTML, text, screenshots, compact reports, summaries, and structured receipt JSON.
No required backend.
Runs on the operator machine, uses local browser executables, and keeps outputs on disk.
cli surface
Simple commands. Real artifacts.
npm install -g @builtbyecho/agentor
agentor setup tor
agentor fetch <url>
agentor screenshot <url>
agentor run <url> --prompt "research this page"
agentor doctor
receipt folder
Proof, not vibes.
Each session writes a local folder that can be attached to a run log, reviewed by another agent, or kept as evidence for what the browser actually saw.
receipt.jsonrun metadata
page.htmlcaptured DOM
page.txtreadable text
screenshot.pngviewport capture
report.mdresearch summary
privacy framing
Operational discipline, not anonymity theater.
Tor routing improves path hygiene. It does not magically erase fingerprinting, account state, downloaded artifacts, or bad operational habits. agenTOR keeps the claims honest and the evidence local.