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

Ouverte
#348 20 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
8/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
flutter, rust

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
Rust
Étoiles
3
Forks
1
Merge moyen
9 h 51 min
PR mergées (30 j)
310

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de codeatlasdev/atlas

Toutes les issues de codeatlasdev/atlas

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.