feat(runtime): warm per-project dev sessions shared across worktrees (Vite, test runner, browser)

Abierto
#125 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust, vite

Línea de trabajo

The payload names no files, so start from the atlas.yaml parsing and the process-supervision code in codeatlasdev/atlas and find where per-worktree commands are currently launched cold. Then read how the pilot project codeatlasdev/ui declares Vite, Vitest browser and Chromium runs. Done means the second run of a one-file test is at least 5x faster than the cold run and no processes survive an agent being killed. This is design work spanning daemon lifecycle, health checks, port and browser-profile multiplexing.

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

Descripción

area: desktop area: runtime priority: 2 normal type: feature

Each worktree cold-starts Vite, a Vitest browser session and Chromium for every run.

Proposal: Atlas keeps warm, project-scoped sessions declared in atlas.yaml (a daemon command plus a health check) and multiplexes per-worktree requests onto them, each with its own port and browser profile. It idles them out after N minutes and kills them when their owner dies.

Acceptance: the second run of a one-file test is at least 5× faster than the cold run, and there are no orphan processes after an agent is killed.


Found while working on codeatlasdev/ui with parallel agents: a single machine (M4 Pro) saturated by several worktrees each running their own Vite, Chromium and Astro builds, plus orphaned browsers and caches. ui is the pilot project for this. Design target: works on a 4-core laptop.

Lenguaje dominante
Rust
Estrellas
3
Forks
1
Merge medio
9 h 51 min
PR fusionados (30 d)
310

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 codeatlasdev/atlas

Todos los issues de codeatlasdev/atlas

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.