CLI
What this solves
You operate or use a Gitea-compatible forge and want a practical command line client.
CLI for Gitea and Forgejo-compatible hosts
fj targets Forgejo and Gitea-compatible APIs, so terminal workflows can follow you across self-hosted forges.
Best fit
- Self-hosted teams
- Forgejo migrations from Gitea
- Scripted repository administration
How to think about it
Forgejo and Gitea share enough API history that many repository, issue, pull request, and release workflows can be handled with the same terminal habits. The right test is not the product name; it is whether your host exposes the endpoints and permissions your workflow needs.
Host compatibility check
fj auth login --host git.example.net
fj repo view org/project
fj issue list --repo org/project
fj api versionPractical path
- 01 Confirm your host exposes the compatible API surface.
- 02 Authenticate with a token scoped to your workflow.
- 03 Use raw API access for host-specific gaps.
When to choose another path
Older hosts may not expose every endpoint used by newer workflows.
Token scopes and organization permissions vary across installations.
Self-hosted network policy can affect mobile, CLI, and runner access differently.
Next resources
Related reading
Forgejo CLI for issues, pull requests, and releases
Use fj as a Forgejo CLI for issues, pull requests, releases, and Actions logs, and script the parts of your day that never needed a browser.
Terminal workflow for Forgejo
Build a terminal-first Forgejo workflow that carries a change from branch to review to release without leaving the shell, using fj and Forgejo Actions.
Automating Forgejo with fj, Actions, and the API
Automate Forgejo with fj, Actions, and API calls: schedule routine jobs, wire repository hooks, handle secrets, and cut releases without touching the UI.