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

[Meta] Dogfood Ace end to end

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
developer-experience

Línea de trabajo

This is a tracking issue, not a task: read the linked scope-decision comment (issuecomment-5986572832) first, then pick one open sub-issue such as #50 or #55 rather than the meta issue itself. The stated convention is that every PR adds an external-tool escape to its "Built in Ace" section and links the gap issue; done means the sub-issue checkbox and its linked PR reflect that record. Nothing here is assigned or open for a single first-time edit.

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

Descripción

The team dogfoods Ace together this week, ahead of Universe. This issue is the dogfooding policy and the open backlog. It absorbed #218 on October 15. Closed items were removed; their history stays in the issues and PRs and in this issue's edit history.

Policy

  • All Ace development happens in Ace.
  • Record any external-tool escape in the PR's Built in Ace section and link the gap.
  • File bugs and missing capabilities as issues and link them here.

Items are ordered by importance within each list.

Blocking the team

  • #427: validate desktop tool use in Ace and track known gaps. The engine work is githubnext/desktop-tools#11.

Core and quality of life

  • #35: see who's in a chat and who's typing.
  • #24: edit and delete queued messages, and choose steer, follow-up, or interrupt now.
  • #28: start work from issues and PRs, and see who is already on them.
  • #19: show more than one chat in a channel (the app only shows chat 1).
  • #52: supervise subagents and send follow-up work.
  • #53: manage background and interactive jobs.
  • #22: browse files in Ace (read-only).
  • #16: open a lane's dev-server preview.
  • #105: attach every image from a multi-file Finder paste.
  • #502: walk a collaborator through cloning a project to their machine, without listing who else has it.
  • #503: keep channel names unique when an agent names or a person renames a channel.
  • #504: only offer Fork (and other owner-only actions) on channels this person can use them on.
  • #505: sidebar rows show faces right after the channel name, pin only in the context menu, so names truncate only when out of room.

Hosted and cloud channels

  • #177: create hosted channels from the new-channel picker. Until then, create locally and use Move to.
  • #430: show a cloud channel as stopped after the service's idle stop.
  • #413: keep cloud workspace files beyond the checkpoint limit and across the idle stop.
  • #500: when moving to a cloud workspace, have the agent push unready lanes instead of failing.
  • #499: move a hosted channel straight to a cloud workspace; Move to only offers this host.

The cloud compute pilot is done (#216 closed after scenarios 26 and 26b).

Development loop

  • #97: dev app reload, and reporting an open launch that exits early.
  • #55: verify the native development loop and recovery end to end.

Later

These aren't needed to dogfood this week:

  • #50: browser DOM tools.
  • #57: agents message channels on peer hosts.
  • #56: required skills and tool integrations.
  • #202: operate a teammate's desktop.

Other hosted and cross-host work is tracked in #58. The stable release is #217.

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.