store: Gitea CLI: use tea not gh for API access

graph/configurations/gitea-cli-use-tea-not-gh-for-api-access-158f8e.md

@@ -0,0 +1,25 @@
+---
+id: 158f8e64-a935-4f0f-b7fd-d76657825c27
+type: configuration
+title: "Gitea CLI: use tea not gh for API access"
+tags: [gitea, tea, cli, configuration, api]
+importance: 0.7
+confidence: 0.8
+created: "2026-02-13T21:09:58.004523+00:00"
+updated: "2026-02-13T21:09:58.004523+00:00"
+---
+
+The gh CLI does not work with Gitea — it's hardcoded for GitHub API v3 at /api/v3/, but Gitea uses /api/v1/. Attempts to use 'gh api --hostname git.manticorum.com' fail with HTTP 404.
+
+Solution: Use tea (Gitea's official CLI) installed at ~/.local/bin/tea
+Authenticated as: cal@homelab (https://git.manticorum.com)
+Token source: ~/.claude/secrets/gitea_token
+
+Common commands:
+- tea repos list
+- tea pulls list
+- tea issues list
+
+Updated CLAUDE.md to always use tea for Gitea operations, never gh.
+
+This fixes the pattern where Claude would try gh first (fail), then retry with curl (succeed).