In a hosted cloud session, git run as the normal user that abcd's cloud setup script creates (runuser -u abcd) cannot reach origin over HTTPS: the session's proxy CA bundle sits under /root, which that user cannot read, so every networked git command fails with a certificate error before anything is sent. Seen live on 2026-10-17 when a claude.ai/code session ran abcd announce; it got through only after the session pointed the CA variables at the system trust store, which already holds the same CA, for that one command. The setup script made the user, so abcd added this failure.

In a hosted cloud session, git run as the normal user that abcd's cloud setup script creates (runuser -u abcd) cannot reach origin over HTTPS: the session's proxy CA bundle sits under /root, which that user cannot read, so every networked git command fails with a certificate error before anything is sent. Seen live on 2026-10-17 when a claude.ai/code session ran abcd announce; it got through only after the session pointed the CA variables at the system trust store, which already holds the same CA, for that one command. The setup script made the user, so abcd added this failure.

Grounds

• pursued: git, gh and abcd run as the normal user in a hosted session verify the proxy's certificate with no per-command workaround; a networked command run through runuser still failing its certificate check in a live session, or a copy whose bytes differ from the proxy's bundle, would show it wrong