feat(traffic): pace Bash requests at the capture proxy

With traffic capture on, the Bash proxy URL carries a marker userinfo. The recording proxy drops Proxy-Authorization from every request before it is forwarded or recorded; when the value is the marker it marks the client connection, and every later request on it, including those inside its CONNECT tunnel, waits for the per-host token and jitter of the current noise profile (egress.Wait) and is counted, with a bounded wait. WebFetch, the http custom tools and enrich keep the unmarked URL, which egress already paces, so nothing is paced twice. Off paces nothing. Best effort: only clients that honour the proxy are covered, with capture on.
This commit is contained in:
BaaRai
2026-11-15 00:57:13 +01:00
parent 251ab680cc
commit 2e55615713
10 changed files with 527 additions and 6 deletions
@@ -78,8 +78,11 @@ export function NoiseProfileCard() {
</CardTitle>
<CardDescription>
Paces the requests ARTEX itself sends to targets (WebFetch, http custom tools, the enrich probe) and sets the
low-and-slow guidance in agent prompts. Commands run through Bash are not paced. This setting takes
precedence over ARTEX_NOISE_PROFILE and applies to the next request.
low-and-slow guidance in agent prompts. With traffic capture on, Bash commands that use the proxy (curl,
wget, python-requests…) are paced too, by rate and jitter only: the in-flight, cache and retry limits apply
to ARTEX's own requests. Raw scanners such as nmap, and commands that bypass the proxy, are not paced; this
is best effort, not a security boundary. This setting takes precedence over ARTEX_NOISE_PROFILE and applies
to the next request.
</CardDescription>
</CardHeader>
<CardContent className="flex flex-col gap-4">