[giordano-lucas]

Automated regeneration of the generated API client (internal/api, internal/cmd/*_flags.gen.go) from the latest OpenAPI spec.

Last regenerated: 2026-11-04 01:27 UTC

[andreakiro]

Auto-approved: scheduled API client regeneration.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The changes affect callers of the generated session API client.

The PR appears safe to merge, with a non-blocking text-output issue.

Findings

1.  Certificate fingerprints become unreadable ▶

Fix with agent prompt

### Issue 1
internal/api/client.gen.go:4929
For sessions with `ca_sha256` set, the new `SecretProxy` field makes text-mode `sessions status` print a pointer address instead of the certificate fingerprints. `printSessionStatus` dereferences the outer pointer, then prints the whole struct with `%v`, leaving the nested `CaSha256` pointer unreadable. Format the summary’s fields separately so users can read the fingerprints. JSON output is unaffected.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Updates the generated API client for secret proxies.

• Session requests can route chosen hosts through a secret proxy.
• Session responses include a summary of the secret proxy.

_{Reviews (1) · Last reviewed commit: "chore: regenerate API client from latest..." · Reviewed by Greptile}

[greptile-apps]

Certificate fingerprints become unreadable

For sessions with ca_sha256 set, the new SecretProxy field makes text-mode sessions status print a pointer address instead of the certificate fingerprints. printSessionStatus dereferences the outer pointer, then prints the whole struct with %v, leaving the nested CaSha256 pointer unreadable. Format the summary’s fields separately so users can read the fingerprints. JSON output is unaffected.

Prompt To Fix With AI

This is a comment left during a code review.
Path: internal/api/client.gen.go
Line: 4929

Comment:
**Certificate fingerprints become unreadable**

For sessions with `ca_sha256` set, the new `SecretProxy` field makes text-mode `sessions status` print a pointer address instead of the certificate fingerprints. `printSessionStatus` dereferences the outer pointer, then prints the whole struct with `%v`, leaving the nested `CaSha256` pointer unreadable. Format the summary’s fields separately so users can read the fingerprints. JSON output is unaffected.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.