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

Feature proposal/discussion: enable end-to-end Agent Access through PATs, answer-cli, and an Answer Skill

Abierto
#1,614 2 comentarios 0 reacciones 1 asignado Ver en GitHub

@hgaol ya está trabajando en esto.

Desde el 14/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Is your feature request related to a problem? Please describe

There is no consistent, least-privilege way for CLI tools and coding agents to operate as an existing Answer user while preserving the user account permissions, moderation rules, CAPTCHA behavior, and the ability to revoke access.

Describe the solution you would like

Discuss an Agent Access design based on Personal Access Tokens, answer-cli, and an Answer Agent Skill.

The initial PAT scopes are:

  • question.read
  • question.create
  • answer.read
  • answer.create
  • vote.write

This is an initial scope set and may be extended in future releases as additional workflows are defined.

The complete design, including authentication, authorization, token lifecycle, CLI behavior, Skill behavior, security considerations, and delivery phases, is documented in Agent Access Design.

This issue is intended for design review and discussion before implementation is expanded.

Related issue: #1555

Describe alternatives you have considered

  • Continue using administrator-managed API keys, which do not represent an individual Answer user and are not suitable for least-privilege user delegation.
  • Add agent-specific identities or a separate agent API, which would introduce new identity, attribution, and authorization models.
  • Use unrestricted browser automation or ad hoc HTTP scripts, which would not provide a stable CLI contract or explicit revocation and scope controls.
Lenguaje dominante
Go
Estrellas
15.7k
Forks
1.4k
Merge medio
1 d 20 h
PR fusionados (30 d)
6

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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 apache/answer

Todos los issues de apache/answer

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.