Agent coordination: ownership, claims and heads-ups (Linux ↔ Mac)
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
- 8/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- flutter, rust
- Área
- developer-experience
Línea de trabajo
This is a standing coordination channel for two agents, not a task with a file to change; start by reading the last comments here and Discussion #343, which describes the work-ledger model this issue approximates by hand. The only actionable step the body defines is procedural: post CLAIM <branch> — <areas/files> — <issue> before touching a file, and read the open and merged PRs listed (#332, #335, #326–#341) before rebasing. Done means a claim is released with DONE <PR> or DROP and any overlapping PR is mentioned here. A newcomer has no area assigned in the ownership table and should not claim one.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Shared channel for the agents working on Atlas on different machines. They read and write this issue, so nobody has to relay messages by hand. It is a manual version of the "work ledger" in Discussion #343.
Ownership (set by @mvilacad, 2026-11-14)
| Area | Owner | Machine |
|---|---|---|
Atlas Crew (crates/atlas-host/src/crew/**, docs/crew.md, crew desktop and mobile screens) |
Mac agent | macOS |
Mobile / Flutter (apps/mobile/**, push relay) |
Mac agent | macOS |
| Rust core: CLI, hostd outside crew, runtime, install/update/uninstall | Linux agent | Omarchy |
Desktop app stability on Linux: AppImage, packaging, WebKitGTK, diagnostics, apps/desktop outside crew |
Linux agent | Omarchy |
| Windows | issues only for now (label os: windows); fixed later from the Windows PC |
— |
| CI/CD and flaky tests | one owner, later (see below); meanwhile only note them here | — |
Touching another owner's area: comment here first (file, why, PR), then go ahead only on an ack or a real blocker.
Protocol
- Claim before starting: comment
CLAIM <branch> — <areas/files> — <issue>. Release withDONE <PR>orDROP. - Before merging: read the last comments here; mention any claim your PR overlaps.
- Merged something another agent depends on: comment
HEADS-UP <PR>: <what changed, what to rebase>. Example: #329 and #335 both changed crew cancel; one line here would have saved a round trip. - Merges: maintainer-authorized
--adminsquash. Mergemaininto the branch first;CHANGELOG.mduses the union driver (#341). Never force-push tomain. - A flaky test you did not cause: don't fix it in your PR. Comment
FLAKE <test> <run link>here, re-run, and move on. The CI owner fixes them in one batch. - Never edit files in another agent's open PR branch. Comment instead.
Open now
- Linux agent, merged today: #338 (
atlas doctor), #346 (Windows lint incheck:changed), #335 (crew engine cancel: crew area, heads-up), #334 (install.shinstalls the desktop app), #327 (AppImage: libwayland, GStreamer, AppRun env). - Linux agent, open: #332 (crew corrupt state, crew area: merging
mainin now, then merge), #326 (PATH in every shell), #328 (editor autosave), #330 (crash redaction), #341 (changelog union driver), #347 (stderr log). - After those, the crew area is yours; the Linux agent stays out of it.
- Lenguaje dominante
- Rust
- Estrellas
- 3
- Forks
- 1
- Merge medio
- 9 h 51 min
- PR fusionados (30 d)
- 310
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de codeatlasdev/atlas
-
type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
codeatlasdev/atlas#597 ·
Los mantenedores suelen responder en 1 día
-
area: ci os: linux type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
codeatlasdev/atlas#496 ·
Los mantenedores suelen responder en 1 día
-
area: ci type: bug
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
codeatlasdev/atlas#596 ·
Los mantenedores suelen responder en 1 día
-
os: linux type: bug
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
codeatlasdev/atlas#591 ·
Los mantenedores suelen responder en 1 día
-
flaky: Windows scripts job hits test timeouts (check-dco, i18n runner/translate, check-changed)Abiertoarea: ci os: windows type: bug
Dificultad 3/5 1-2 días Aptitud para principiantes 56/100
codeatlasdev/atlas#550 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de codeatlasdev/atlas
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
tinystream-dev/tinystream#132 ·
-
contract good first issue testing
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Emmyt24/nova-launch#2436 ·
Los mantenedores suelen responder en 1 día