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

Reach hosted channels from a browser without a host gateway

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
authentication, authorization, backend

Línea de trabajo

Start by reading #13 and the existing hosted lifecycle/discovery work it describes, then trace how current clients reach a cell and enforce owner operations, chat, and agent invocation. The issue does not name files or tests; first map those entry points and the tailnet identity flow. Done means the acceptance criteria are met, including revocation, reconnect, offline behavior, and deployment documentation.

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

Descripción

Allow a browser to reach a hosted channel without a reachable Ace host gateway. This is optional later work.

The original #13 requested browser reachability and per-person sign-in. Preserve that need while keeping the tailnet the sole authority for team membership and collaboration access. Ace must not introduce its own accounts, invitations, team membership or parallel authorization system, and a shared host/service secret must never become a browser participant credential.

Acceptance

  • Design a browser-to-cell route and a per-person identity/authorization proof tied to the existing tailnet authority. Document how team membership is checked, revoked and refreshed, and how browser origin/session handling works.
  • Keep server/workspace shared secrets out of browser clients and user-visible URLs. Enforce owner operations, ordinary chat and collaborator-agent invocation using the same policy as existing clients.
  • Open history, post attributed chat, watch live updates and invoke permitted agents directly against the cell, while displaying workspace availability honestly. Repository files and tools remain on the workspace.
  • Verify a real browser with no reachable host gateway, two people where available, membership removal/revocation, reconnect and an offline workspace. Refused/expired identity must not queue unauthorized work.
  • Document the team's deployment/configuration requirements and unsupported cases. Ace remains team-operated software rather than a hosting service.

Reuse hosted lifecycle/discovery work in #13. This issue does not require a new cloud execution environment or include real-phone UI qualification (#18), directory push (#14), cross-gateway terminals (#11), or execution-host handoff (#49).

Optional later milestone under #13, following the supported host route and its deployed qualification.

Lenguaje dominante
TypeScript
Estrellas
1
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 githubnext/ace2

Todos los issues de githubnext/ace2

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.