Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

hey auth login fails: "install_id doesn't identify this install. Upgrade your client."

Abierto
  • ¿Algo no está bien?
#578 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
authentication, cli

Línea de trabajo

Start with the browser OAuth path behind hey auth login, where the authorization URL is built with install_id=hey-cli and a loopback redirect to 127.0.0.1. Check where the install id is set and whether it is a shared constant rather than a per-install value. The issue mentions an existing run titled "Identify each CLI install to HEY with its own install_id", so confirm whether that work is already underway before starting. Done means the authorization request carries an install id the server accepts and the login completes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What happened

Running hey auth login (or any command that triggers browser OAuth) opens the browser to app.hey.com/oauth/authorizations/new, but the HEY server rejects the request and sign-in never completes.

What I expected

The browser flow completes and the CLI becomes authenticated.

What actually happened

The browser shows a JSON error:
{"error_description":"install_id doesn't identify this install. Upgrade your client.","error":"invalid_request"}

The CLI is stuck at "Waiting for authentication..."

Environment
  • hey-cli version: 1.3.0
  • OS: omarchy 4.0.4-1
  • Install method: Install -> Packages -> hey-cli
  • hey doctor output:

~ ❯ hey doctor
[!!] CLI Version: 1.3.0 (c0f19cf3c22a8cd51e4c73f4fedbc47bcf2ec47e, 2026-08-29T03:30:57Z) (update available: 1.9.0)
hint: hey upgrade
[ok] Go Version: go1.26.6
[ok] Config File: Not found (using defaults)
[ok] Credentials: Stored in system keyring
[!!] Authentication: Not authenticated
hint: hey auth login
[ok] Shell: /usr/bin/bash
[ok] Shell Completion: Installed by your package manager (/usr/share/bash-completion/completions/hey)
[!!] Agent Skill: Not installed
hint: hey skill install
[!!] Claude Code Plugin: Plugin not installed
hint: Run: hey setup claude
[!!] Claude Code Skill: Skill not linked
hint: Run: hey setup claude
[ok] Claude Code Plugin Version: Version not tracked
[!!] Codex Skill: Skill not installed
hint: Run: hey setup codex
[!!] Omarchy Bar Plugin: Not installed
hint: hey setup omarchy
[ok] Git: Available

Notes

The authorization URL includes install_id=hey-cli and a loopback redirect to 127.0.0.1, suggesting the CLI uses a shared/generic install id that the server no longer accepts. There's an existing GitHub Actions run titled "Identify each CLI install to HEY with its own install_id" that may be related.

Lenguaje dominante
Go
Estrellas
412
Forks
52
Merge medio
1 d 7 h
PR fusionados (30 d)
77

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de basecamp/hey-cli

Todos los issues de basecamp/hey-cli

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.