Forgejo `tea` CLI is unavailable and unauthenticated in the runtime container (not in image/Home Manager, no token bootstrap) #76

New issue

Closed

opened 2026-09-04 15:37:56 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-04 15:37:56 +00:00

Owner

Summary

The runtime container cannot use the Forgejo tea CLI end-to-end: it is not installed, cannot be installed through the available nix tooling, and has no working login/token bootstrap. Filing an issue on git.starintel.actor took the agent a dozen failed attempts before stumbling through with ad-hoc workarounds.

Evidence (chat `xPXTvnZd`, "Git and issue", 2026-09-04)

Entry 10: tea: command not found — not in the image PATH nor in the Home Manager profile (/a0/usr/home-manager/home.nix installs openssh but no tea).
Entry 15: nix-env -iA nixpkgs.tea fails with error: attribute 'nixpkgs' in selection path 'nixpkgs.tea' not found — the image ships nix-bin (apt) with no nixpkgs channel in NIX_PATH, and home-manager runs use pinned flakes instead.
Entry 32: tea issues list → Error: no available login (empty logins table).
Entry 40: tea logins add --token-stdin ... → flag provided but not defined: -token-stdin (not supported by the tea version available via nix shell nixpkgs#tea).
Entries 45/49: env-based auth attempts fail — Error: user does not exist [uid: 0, name: ] and Error: access token does not exist for the STAR_AUTH secret; password auth also rejected.
Entry 85: tea issues create ... --body → flag provided but not defined: -body (tea uses --description); the model only discovered this from raw --help output.

Related but distinct from #71-class /root state loss: even with credentials restored, there is no tea binary, no nixpkgs channel to fetch it ad hoc, and no documented bootstrap from a stored project secret to a configured tea login.

Suggested fix

Add tea to docker/symbolics/home-manager/home.nix home.packages so it is present in the persistent profile on every boot.
Document (and preferably script in docker/symbolics/initialize.sh or a usr-scoped restore script) an exact, version-pinned tea login bootstrap that consumes a Forgejo token from project variables/secrets — including the correct GITEA_SERVER_URL/GITEA_TOKEN env usage for the bundled tea version.
Update the git/Forgejo skill guidance with the correct tea issues create --description (not --body) syntax so the model does not rediscover CLI flags by trial and error.

Cross-ref: lost-rob0t/a0-symbolics#75

## Summary The runtime container cannot use the Forgejo `tea` CLI end-to-end: it is not installed, cannot be installed through the available nix tooling, and has no working login/token bootstrap. Filing an issue on `git.starintel.actor` took the agent a dozen failed attempts before stumbling through with ad-hoc workarounds. ## Evidence (chat `xPXTvnZd`, "Git and issue", 2026-09-04) - Entry 10: `tea: command not found` — not in the image PATH nor in the Home Manager profile (`/a0/usr/home-manager/home.nix` installs `openssh` but no `tea`). - Entry 15: `nix-env -iA nixpkgs.tea` fails with `error: attribute 'nixpkgs' in selection path 'nixpkgs.tea' not found` — the image ships `nix-bin` (apt) with no nixpkgs channel in `NIX_PATH`, and `home-manager` runs use pinned flakes instead. - Entry 32: `tea issues list` → `Error: no available login` (empty logins table). - Entry 40: `tea logins add --token-stdin ...` → `flag provided but not defined: -token-stdin` (not supported by the tea version available via `nix shell nixpkgs#tea`). - Entries 45/49: env-based auth attempts fail — `Error: user does not exist [uid: 0, name: ]` and `Error: access token does not exist` for the `STAR_AUTH` secret; password auth also rejected. - Entry 85: `tea issues create ... --body` → `flag provided but not defined: -body` (tea uses `--description`); the model only discovered this from raw `--help` output. Related but distinct from #71-class /root state loss: even with credentials restored, there is no `tea` binary, no nixpkgs channel to fetch it ad hoc, and no documented bootstrap from a stored project secret to a configured tea login. ## Suggested fix 1. Add `tea` to `docker/symbolics/home-manager/home.nix` `home.packages` so it is present in the persistent profile on every boot. 2. Document (and preferably script in `docker/symbolics/initialize.sh` or a usr-scoped restore script) an exact, version-pinned `tea login` bootstrap that consumes a Forgejo token from project variables/secrets — including the correct `GITEA_SERVER_URL`/`GITEA_TOKEN` env usage for the bundled tea version. 3. Update the git/Forgejo skill guidance with the correct `tea issues create --description` (not `--body`) syntax so the model does not rediscover CLI flags by trial and error. Cross-ref: lost-rob0t/a0-symbolics#75

nsaspy closed this issue

2026-09-04 19:11:28 +00:00

nsaspy referenced this issue

2026-09-09 15:04:58 +00:00

Forgejo tea CLI is unavailable and unauthenticated in the runtime container (not in image/Home Manager, no token bootstrap) #78