Keep the local CLI path simple
For a local OpenCode-style CLI, start with agentsight record around the command you already run. This preserves the terminal workflow and bounds the process family to one task. Do not add container-specific options or runtime assumptions unless the actual deployment requires them.
A container name resolves to an init process before it resolves to TLS
AgentSight's OpenClaw experiment documents a real Docker topology in which docker inspect returns tini as the container init while the Node descendant owns the TLS stack. Attaching to tini would capture no model plaintext. The docker:// resolver walks descendants and chooses the SSL-embedding executable for the supported case.
Node-based services can embed OpenSSL in the executable
The same OpenClaw walkthrough explains why a system libssl path is not enough: the Node executable contains the relevant OpenSSL code in the tested deployment. AgentSight therefore attaches its SSL uprobe to /proc/<pid>/exe for the resolved Node process. This is the same binary-identity problem described in the TLS deep dive, now combined with container process discovery.
Kubernetes adds control-plane resolution before host PID resolution
For supported k8s:// references, AgentSight first resolves the pod/container to a container ID, then uses Docker or CRI tooling to find the host PID before walking the process tree. That means cluster permissions, kubeconfig, CRI availability, and node placement are part of the attachment contract. Run AgentSight on the node that actually hosts the pod and verify the resolved executable.
Do not equate successful model capture with full container coverage
Capturing the LLM request proves that one plaintext path was observed. The container can still contain other processes, local IPC, plain HTTP, or runtime paths outside the selected probe. Use process/file/network views and the workload's own logs when the audit question extends beyond the model client.
Pin the deployment shape when publishing a result
Container images, Node versions, init processes, and agent versions change. Record the image or source version, container runtime, resolved PID/executable, and AgentSight version with any published investigation. This turns an automatic resolver from a black box into a reproducible compatibility claim.
$ sudo agentsight record -- opencode
$ sudo agentsight record -c node --binary-path docker://openclaw
$ sudo agentsight debug trace --binary-path k8s://namespace/pod/container --server