proxy

Documentation

Overview

Package proxy routes Factor's own HTTP through a proxy, so a debugging or auditing session can watch every provider call go past — prompts, tool definitions, replies and token counts, as they cross the wire.

Any proxy will do: an intercepting one (mitmproxy, Burp, ZAP, Charles), a corporate egress proxy, a SOCKS5 listener. It works through the standard proxy environment variables rather than by pinning a transport, for two reasons: Go's own ProxyFromEnvironment already leaves loopback alone, so the memory sidecar and the speech server keep talking directly, and every child process Factor spawns — smrti, the voice shell — inherits the setting and shows up in the same capture.

Index

• func Use(raw, caPath string) (string, error)

Functions

func Use

func Use(raw, caPath string) (string, error)

Use routes this process (and its children) through the proxy at raw. The returned line says what it did, for the caller to print.

caPath names a certificate authority to trust on top of the system roots, which any TLS-intercepting proxy needs; empty means "look in the usual places". Trusting an extra CA is exactly as broad as it sounds, which is why it happens only when a proxy was explicitly asked for, and why the caller is told which certificate was trusted.