Skip to content
ProxAI

Capture Phases

Capture Phases

Section titled “Capture Phases”

Capture phases name where data sits in the proxy pipeline. Use phase names for capture artifacts, config fields, flow locals, and logs that describe the proxy pipeline.

  1. 1
    inbound_request
    Modules
    ingress/pipeline/inbound_request
    Responsibility

    The original local client request after HTTP admission and protocol detection.

  2. 2
    provider_request
    Modules
    routingtranslation/provider/*/request
    Responsibility

    The selected provider request after routing, protocol conversion, model rewrite, projection, and serialization.

  3. 3
    upstream_response
    Modules
    provider/*/transportpipeline/upstream_response
    Responsibility

    The upstream status, headers, and body bytes before outbound response reconstruction.

  4. 4
    outbound_response
    Modules
    translation/http_support
    Responsibility

    The final response reconstructed for the client-facing inbound protocol.

Config switches

Section titled “Config switches”
Config fieldPhase
inbound_request_enabledinbound_request
provider_request_enabledprovider_request
upstream_response_enabledupstream_response
outbound_response_enabledoutbound_response

CLI phase names

Section titled “CLI phase names”

The capture CLI accepts hyphenated phase names:

Terminal window
proxai capture enable inbound-request
proxai capture enable provider-request
proxai capture enable upstream-response
proxai capture enable outbound-response

Privacy risk

Section titled “Privacy risk”
PhaseLikely sensitive content
inbound_requestClient prompts, input files, tool outputs, client-provided headers
provider_requestTranslated prompts, provider payloads, tool arguments, provider auth decisions
upstream_responseModel output, tool-call arguments, provider headers, raw SSE bytes
outbound_responseFinal model output and protocol-specific response payload
Section titled “Related docs”