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

未关闭
#125 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust, vite

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Rust
星标
3
派生
1
平均合并
9 小时 51 分钟
30 天内合并 PR
310

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

codeatlasdev/atlas 的其他 Issue

查看 codeatlasdev/atlas 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。