Skip to content

feat: make repo pulling by agents done in parallel#12272

Merged
dmichelin merged 2 commits into
masterfrom
make_repo_pulls_parallel
Jun 10, 2026
Merged

feat: make repo pulling by agents done in parallel#12272
dmichelin merged 2 commits into
masterfrom
make_repo_pulls_parallel

Conversation

@dmichelin

@dmichelin dmichelin commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

Description

This PR makes repo pulling in agent mode done in parallel rather than done sequentially. Oz environments with many repos can take a long time currently to start up, and much of that time is due to pulling in multiple large repos one after another.

Linked Issue

https://linear.app/warpdotdev/issue/REMOTE-1867/parallelize-environment-repo-cloning-to-speed-up-startup

Testing

  • I have manually tested my changes locally with ./script/run

Screenshots / Videos

Before:
image

After:
image

Agent Mode

  • Warp Agent Mode - This PR was created via Warp's AI Agent Mode

@cla-bot cla-bot Bot added the cla-signed label Jun 5, 2026
@oz-for-oss

oz-for-oss Bot commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

@dmichelin

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@oz-for-oss oz-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR parallelizes cloning of multiple agent environment and global-skill repositories by adding a batched clone path, then separates cloning from repo registration during environment preparation.

Concerns

  • No blocking correctness or security concerns found in the annotated diff.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@dmichelin dmichelin requested review from bnavetta and seemeroland June 5, 2026 20:32
failed=1
fi
done
exit "$failed"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If cloning any repo fails, do we get any output? Especially for failed clones I think we need to see the output, but ideally we can show the output of every clone that happened in a way that's not interleaved. I think we might need to write output to a log and print it when they're done?

@dmichelin dmichelin requested a review from seemeroland June 10, 2026 18:45
@seemeroland

Copy link
Copy Markdown
Contributor

Do you have a screenshot of what it looks like on success or when a repo clone fails?

@seemeroland seemeroland left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving to unblock assuming it's been tested. Also just making sure this script will work on any common shell and not using any zsh or bash specific syntax?

@dmichelin

Copy link
Copy Markdown
Contributor Author

Do you have a screenshot of what it looks like on success or when a repo clone fails?

image This is what it looks like on success. I'm having a hard time manually testing as warp local doesn't seem to let me create an environment with a repo I can't clone

@dmichelin

Copy link
Copy Markdown
Contributor Author

Approving to unblock assuming it's been tested. Also just making sure this script will work on any common shell and not using any zsh or bash specific syntax?

Yep, this is all POSIX

@dmichelin dmichelin merged commit 168f95e into master Jun 10, 2026
26 checks passed
@dmichelin dmichelin deleted the make_repo_pulls_parallel branch June 10, 2026 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants