[medium] muse-job: pristine-repo collision across orgs

Open Beginner friendly
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

Start at muse-job:121-125, especially repo_name_from_url, and inspect how pristine clone paths are derived from repository URLs. Reproduce the org1/foo and org2/foo collision, then verify that each repository gets a distinct pristine directory and that the existing fetch, worktree, and push flow remains correct.

Written by the indexing model from the issue text.

Description

area:muse-job bug severity:medium track:open-source

Summary

muse-job:121-125 (repo_name_from_url) keys ~/repos/ on the last URL segment only: org1/foo and org2/foo share one clone.

Scenario

The second spawn silently git fetches the wrong repo, cuts the worktree from the wrong base, and the agent pushes/PRs against the wrong upstream.

Proposed fix

Namespace the pristine dir by org or by URL hash.

Severity: medium. Filed from the 2026-09-18 adversarial review of the muse-job session architecture.

Dominant language
Python
Stars
1
Forks
0
Avg merge
4h 37m
Merged PRs (30d)
87

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ntindle/spark-vm

All issues in ntindle/spark-vm

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.