officer
4a7aa40a28
PM2 hands the sidecar a login-less PATH that excludes ~/.local/bin, which is exactly where the platform installs a release binary. So `tea whoami` failed with "the token may be wrong, or tea is not installed" on a machine where tea was sitting in the owner's home and working perfectly from a shell. Third time today the same trap: the probe in os-deps, then the agent's env, now this. Anything the platform installs to ~/.local/bin has to be found deliberately, because nothing the platform spawns inherits a PATH that includes it. Resolved per call rather than cached, so an install that adds it mid-run is picked up instead of a cached "missing" outliving the thing that fixed it.
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.