pastilhasandClaude Opus 5
6d5b75f4f2
teaBinary hardcoded ~/.local/bin:$PATH. Right for tea, wrong as a habit: iris wrote the same function with ~/.cargo/bin added, the two disagreed, and a rustup-only machine was refused a plugin its own sidecar could build. locateBinary asks the owner's login shell, so it knows about every directory a per-user installer added without anyone listing them. Verified it still resolves tea from ~/.local/bin, which is the case the comment above it was written for. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.