Repository navigation
rax-task-runner: keep the first-run marker on the workspace volume, as AX now does - #15
Merged
Merged
Conversation
…s AX now does The marker lived under /ax, which a volumes-only resume does not restore, so setup ran again and could overwrite the agent's edits. Write it under the workspace instead: .git/.ax/initialized when the workspace root is a git repository, otherwise .ax/initialized. - Migrate a marker left under /ax only when it names this workspace, since two mount paths can share a legacy marker name (/a/b and /a-b). - Refuse a marker, or a marker directory, that is a symbolic link: the agent can create one, and following it would leave the workspace. - Create the marker's directory before writing it. - Normalize path separators in marker_name. Ports AX's new setup tests (root clone, own and foreign legacy markers, a linked marker directory) and moves the runner and local E2E checks to the new path. README: parity as of AX 241bc4d. AX's other change since the last parity point only touches its README quick start, demo.sh and a WorkerPool example; RAX's local setup already creates a WorkerPool. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0193yhp4LhPwgHBK6JdpZQb5
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.
Requested by Hoffmann · project thread
Brings RAX to parity with AX's
mainat241bc4d(from6e970c5). AX has two commits since the last parity point; one changes behavior, and this PR ports it.What changed
The workspace's first-run marker lived under
/ax, which a volumes-only resume does not restore, so setup ran again and could overwrite the agent's edits. Like AX, RAX now writes it on the workspace volume:.git/.ax/initializedwhen the workspace root is a git repository (the git directory is untouched bygit add -Aandgit clean -fdx), otherwise.ax/initialized./axby an older runner is migrated, but only when it names this workspace, since two mount paths can share a legacy name (/a/band/a-b).marker_namenormalizes path separators.Tests
.git, own legacy marker migrated, another workspace's legacy marker ignored, linked.axdirectory refused. Added one for a linked marker file.workspace_setup_files_and_git) now check the new path, as AX's runner and E2E tests do. Dropped the E2E harness's now-unused per-actor/axmap.cargo fmt,cargo clippy --workspace --all-targets(clean) andcargo test --workspaceall pass, including the 7 local E2E tests.Not ported
AX's other change only touches its README quick start,
demo.shand a WorkerPool example manifest. RAX's local cluster setup (hack/local) already creates theax-workersWorkerPool, so nothing applies here.README: parity point moved to
241bc4d, line counts updated (7,640 of 8,262).Generated by Claude Code