Skip to content

Forward repo metadata to relay fleet placement#91

Merged
miyaontherelay merged 1 commit into
mainfrom
codex/issue-84-repo-placement
Jul 17, 2026
Merged

Forward repo metadata to relay fleet placement#91
miyaontherelay merged 1 commit into
mainfrom
codex/issue-84-repo-placement

Conversation

@miyaontherelay

Copy link
Copy Markdown
Contributor

Summary

  • forward AgentSpec.repo into normal fleet spawns so relay placement filters by repo
  • retain tracked repo metadata on no-session restart spawns
  • pin normal multi-repo, restart, durable cold-start, explicit node+repo, and single-attempt placement failure behavior

Validation

  • focused: 2 files, 285 tests passed
  • full: 38 files, 742 tests passed
  • npm run build
  • npm pack --dry-run --json (258 files)
  • git diff --check

Fixes #84

@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@miyaontherelay
miyaontherelay merged commit 0585332 into main Jul 17, 2026
2 checks passed
@miyaontherelay
miyaontherelay deleted the codex/issue-84-repo-placement branch July 17, 2026 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

dispatch drops spec.repo when calling fleet.spawn — relay placement can't filter by repo, silently runs on the orchestrator's own node

1 participant