fix(a2a): keep a failed agent's logged URLs only as their scheme and host

[earakely-scale]

Summary

When an agent's task fails on a sandbox with docker, fetch_container_logs tails the agent's container logs. Core logs that tail and keeps it with the failed step's error, which is persisted in the run context. An agent that logs the URLs it fetches therefore had its grant and signed URLs stored with the run, credentials and all. OpenCode does this through its HTTP client's request log.

• agentenv_protocol.transfers.redact_urls(text) cuts each HTTP(S) URL in text to its scheme and host. It is the rule the protocol's httpx log filter already applied to grant requests, now public, and the filter uses it too.
• fetch_container_logs passes stdout and stderr through it before cutting them to length. Otherwise the cut could leave part of a URL behind with no scheme for the pattern to match. This covers both the solver's and the rubrics judge's failure paths.

Testing

• Unit:
  • redact_urls on signed, staging and local URLs, leaving the rest of the text alone;
  • fetch_container_logs redacting a URL that the length cut runs through.
• Integration (fast tier, local agent): the echo agent now prints the text of a fail-with <text> line and fails the task. A local run tells it to log a signed URL and fail. The failed step's persisted error keeps the container-log tail, with the URL cut to its host and no part of its signature or credential left.
• Mutant checks:
  • main's fetch_container_logs fails the integration test: the full URL is kept;
  • redacting after the cut fails the unit test.
• Suite: tst/unit + protocol, 6341 passed.
• Plugin API: no break.
• On a dev deployment: reran the file-delivery suite from feat(prompt-agent): agents receive store-owned file parts as HTTPS URLs they can read #57 with OpenCode on a VM provider. That's where this was found: its deliberately failing "owned key that doesn't exist" case had one signature in the run context. Now the read cases still pass 9/9. Both failing steps keep their log tails with the URLs redacted, and the stored run holds 0 signatures.

🤖 Generated with Claude Code

Confidence Score: 5/5

The PR appears safe to merge; no finding remains outstanding.

What we checked:

• Later tests can use grants: The next grant starts the closed server again. It gets a certificate from the later test’s state directory.

Summary

Failed-agent container logs now keep URL origins while hiding URL paths and credentials, so signed or temporary links are not retained in failure details.

• Failed-agent logs keep URL hosts but hide paths and credentials.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    A[Agent container logs] --> B[Redact HTTP URLs]
    B --> C[Keep the log tail]
    C --> D[Save the failed step error]

Loading

_{Reviews (2) · Last reviewed commit: "test(a2a): the failure-logs test keeps i..." · Reviewed by Greptile}

[earakely-scale]

Closing for now: in the last 7 days, none of prod's failed-agent log tails carried a signed URL, so this isn't needed yet. The fix is on branch edgararakelyan/redact-agent-log-tail if it is.