Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Reach hosted channels from a browser without a host gateway

Ouverte
  • Quelque chose ne va pas ?
#182 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript
Domaine
authentication, authorization, backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
1
Forks
0
Aucune PR mergée en 30 j

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de githubnext/ace2

Toutes les issues de githubnext/ace2

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.