Agent coordination: ownership, claims and heads-ups (Linux ↔ Mac)

Aberta
#348 20 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
8/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
flutter, rust

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

type: chore

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

  1. Claim before starting: comment CLAIM <branch> — <areas/files> — <issue>. Release with DONE <PR> or DROP.
  2. Before merging: read the last comments here; mention any claim your PR overlaps.
  3. 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.
  4. Merges: maintainer-authorized --admin squash. Merge main into the branch first; CHANGELOG.md uses the union driver (#341). Never force-push to main.
  5. 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.
  6. Never edit files in another agent's open PR branch. Comment instead.

Open now

  • Linux agent, merged today: #338 (atlas doctor), #346 (Windows lint in check:changed), #335 (crew engine cancel: crew area, heads-up), #334 (install.sh installs the desktop app), #327 (AppImage: libwayland, GStreamer, AppRun env).
  • Linux agent, open: #332 (crew corrupt state, crew area: merging main in 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.
Linguagem predominante
Rust
Estrelas
3
Forks
1
Merge médio
9h 51min
PRs com merge (30d)
310

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de codeatlasdev/atlas

Todas as issues de codeatlasdev/atlas

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.