Every asset in the frame answered 502. `fetch()` decompresses transparently while `upstream.headers` still claims content-encoding: gzip, so re-emitting those headers with the decompressed body hands the next hop a lie and it dies with ZlibError. The HTML escaped it only because the sidecar deletes that header when it rewrites — which is why the page rendered and every stylesheet, script and image beside it failed. Not asking for compression removes the mismatch rather than chasing it through two hops. The cost is nil: this hop is loopback, and the browser's own connection is compressed by whatever terminates TLS.
Gitea
Your own Gitea inside Officer — repositories, issues and pull requests, rendered as the real thing rather than a copy of it.
What you get
Gitea's own web interface, in an Officer panel. Not a reimplementation: the actual application, proxied through Officer so it stays signed in, with an open in a new tab button for anything the frame handles badly.
Requirements
A Gitea instance Officer can reach.
Setup
Install the plugin, open /gitea, and set the instance URL and an API token in the connection panel. Then sign in to Gitea inside the frame, once — the frame shows your Gitea account, not the owner's.
The stored token is used only for the small things around the frame. Everything you see in it is your own session.
For agents
This plugin ships an affordance: use plain git for clone, fetch, pull and push; use tea for pull
requests, issues, comments and releases. tea is logged in as you, with your permissions.
Permissions
One permission, gitea, grantable per role like any other app permission. Each account reaches its own
Gitea identity.