cmd/cmd.go defaults GITEA_HOST to https://gitea.com and treats an empty GITEA_ACCESS_TOKEN as "use Authorization header per request". This is fine for HTTP mode, but in stdio mode a missing token surfaces as opaque 401 errors on every tool call — the user has no idea they forgot the env var.
Suggested direction
In Execute(), validate that, in stdio mode, a token is set via flag or env. If not, print a one-line setup hint and exit 1 before tool registration.
For HTTP mode, log a single Info line at startup describing the auth precedence (header > flag > env) so operators can confirm their setup.
## Problem
`cmd/cmd.go` defaults `GITEA_HOST` to `https://gitea.com` and treats an empty `GITEA_ACCESS_TOKEN` as "use Authorization header per request". This is fine for HTTP mode, but in stdio mode a missing token surfaces as opaque 401 errors on every tool call — the user has no idea they forgot the env var.
## Suggested direction
- In `Execute()`, validate that, in stdio mode, a token is set via flag or env. If not, print a one-line setup hint and exit 1 before tool registration.
- For HTTP mode, log a single `Info` line at startup describing the auth precedence (header > flag > env) so operators can confirm their setup.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
cmd/cmd.godefaultsGITEA_HOSTtohttps://gitea.comand treats an emptyGITEA_ACCESS_TOKENas "use Authorization header per request". This is fine for HTTP mode, but in stdio mode a missing token surfaces as opaque 401 errors on every tool call — the user has no idea they forgot the env var.Suggested direction
Execute(), validate that, in stdio mode, a token is set via flag or env. If not, print a one-line setup hint and exit 1 before tool registration.Infoline at startup describing the auth precedence (header > flag > env) so operators can confirm their setup.