Deleting the old UI took its connection panel with it, so the plugin installed, opened, and had nowhere to type a URL. The frame would have loaded and answered 503 on every request inside it — which reads as Gitea being down rather than as nobody having said where Gitea is. The panel now asks for the connection FIRST and shows the form when there is none. Two halves, and which one you get depends on who you are: the URL is the owner's, one instance per server, and everyone else supplies only a token and inherits it. Not a UI choice — service_connections stores a member's row with a null URL for exactly this reason, so "members never see the instance URL" is a property of the schema rather than a filter somebody has to remember. Defaults to http://localhost:3000 and says why in the field: the sidecar fetches SERVER-side, so localhost means the machine Officer runs on. It needs no TLS and never leaves the box, where the public URL takes the same traffic out and back.
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.