Gitea CLI for issues, pull requests, releases, actions, webhooks, and API calls.
$brew install tea
Agent Compatibility
JSON Output
Agent Skill
MCP Support
AI Analysis
tea is Gitea's official CLI for working with one or more Gitea instances from the shell. It covers day-to-day collaboration and service operations around repositories, issues, pull requests, releases, actions, webhooks, notifications, and raw API access.
What It Enables
- List, create, edit, close, and comment on issues or pull requests, then check out, review, approve, reject, or merge PRs from a local clone.
- Inspect and update repository state such as releases, labels, milestones, branches, tracked time, action secrets or variables, notifications, and webhooks.
- Call arbitrary Gitea REST endpoints with
tea apiwhen a built-in subcommand does not cover the workflow you need.
Agent Fit
- Real machine-readable output is available through
--output jsonand related formats across many list commands, and issue or pull detail views can also emit JSON. - Login profiles, repo-aware defaults, and a raw
apiescape hatch make it practical for inspect/change/verify loops across one or many Gitea instances. - Some paths still prompt interactively for auth, comments, editors, or confirmations, so unattended runs should pass flags explicitly and avoid prompt-driven flows.
Caveats
- Best results assume a local git checkout with correctly configured remotes; commands like PR checkout and repo inference depend on local git context.
- Authentication options vary by deployment. Token login is the safest baseline, while OAuth or SSH-based flows depend on instance configuration.