Repository navigation
fix(bundle): register writes a universe folder under its registry id - #762
Merged
earakely-scale merged 1 commit intoNov 19, 2026
Merged
Conversation
bundle register refused any bundle holding an environment universe folder: the folder's environments and their files are named from the universe's id, and every one was checked as a local id, which a registry id never is, so each name was first hashed and then refused as "must start with '@local/'", with advice to shorten the name that couldn't help. A local id is still checked as one; a registry id takes the folder's names as they are. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
earakely-scale
deleted the
edgararakelyan/register-universe-folder-registry-ids
branch
November 19, 2026 16:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
bundle registerrefused every bundle that holds an environment universe folder (artifacts/<name>/withtype = "environment_universe"and a folder per environment).read_foldernames each environment as<universe>__<name>and each environment's file as…__file. It checked every one of those ids withvalidate_local_id. Underregister, the universe's id is a registry id, which never starts with@local/, so:_child_idtreated every name as invalid and hashed it (<universe>__sha256__…);can't name the artifacts written from it (local id '…' must start with '@local/' or '@hf/'); give the universe a shorter name.No shorter name could help.
Now a local id is checked as one, and a registry id takes the folder's names as they are. This matches how the recording step treats ids (
if is_local_id(id): validate_local_id(id)).agent-env run, where ids are local, is unchanged.Why
I hit it while registering the laptop task's computer version into AgentEnvHub's dev stage (HB5.1.1, FD-6206). Its universe is the tools version's own
-ufolder.Proof
environment_universe_folder_test.py: a universe read under a registry id namesgmail<id>__gmailand its file<id>__gmail__file. A name holding__is still hashed.register_test.py: a bundle whose task loads a universe folder registers. Its environments aretriage-world-u__gmailandtriage-world-u__shelfway.tst/unit/artifact/environment_universe_folder_test.pyandtst/unit/bundle/register_test.py, 39 passed.ruff check: clean.agent-env --stage dev bundle registerwrote the laptop task's universe into the dev stores. Without it, the registration failed at the universe.🤖 Generated with Claude Code


Confidence Score: 5/5
The PR appears safe to merge.Summary
Fixes
bundle registerfor environment universe folders by applying local ID checks only to local IDs.No actionable issues found.
Reviews (1) · Last reviewed commit: "fix(bundle): register writes a universe ..." · Reviewed by Greptile