Repository navigation
Open
Labels
loom:blockedWaiting on something named (another change, a capability); released once it resolvesWaiting on something named (another change, a capability); released once it resolves
Description
Live run this issue tracks
The fix in #14744 (daemon-owned App gh-config dir no longer refused nor mounted for a NEW private seat) is verified offline by unit tests in loom-daemon/src/tokens_pool/private_workspace/tests.rs. What those tests cannot establish is the live, unattended reconciler pass on a real App-only host.
Someone with access to an App-only crew host (loom-crew-7 / loom-crew-8 class, 2AMLogic/2am#7871, daemon with the #14744 fix deployed) must:
- Declare a private-clone seat binding for a repository not yet registered (
autonomous.sessionReconcile.privateClones). - Let ONE reconcile pass run (no hand
accounts session start). - Confirm:
loom-daemon accounts listshows the seat in session mode (notsession=host);- the
loom-codex-session-*container exists; - the seat's
workspace.jsonrecords"gh_config": nullanddocker inspectshows NO/run/loom-ghbind mount; - the seat can clone/fetch its private repository (token arrives per exec via the
forge_authpath, Codex private-clone sessions have no forge credential on App-only workers (gh_config: None) → every contained dispatch refused #13916); - a non-daemon
GH_CONFIG_DIRunder a checkout is still refused with "forge credentials must be outside every repository/worktree" (e.g. via a handsession startin a shell with such a dir exported).
- Close this issue with the observed output.
Dependencies
- PR fix: skip the gh-config bind for daemon-owned App credentials in new private seats #14766 delivers the fix for session_reconcile cannot create a private-clone seat on an App-only host: the daemon's own GH_CONFIG_DIR is inside its checkout #14744. As of 2026-11-20 its head was
eaf51fc73and the PR was open. Before collecting evidence, identify the running daemon build on the App-only host and confirm it contains the fix.
Test Plan
- Record the host, running daemon revision, seat identifier, and UTC time. Choose a logged-in seat with no existing private workspace record or session container. Adding a repository to an existing seat exercises registration and cannot establish fresh seat creation.
- Declare the binding and capture one unattended reconcile pass. Match its timestamp and seat to the new running container and the session mode shown by
loom-daemon accounts list. Run the refusal check below only after collecting this evidence. - Confirm the new seat record explicitly contains a null
gh_configfield (jq -e 'has("gh_config") and .gh_config == null'). Inspect the container’s mount destinations for absence of/run/loom-gh. Use the normal Loom seat execution path to fetch from the declared private repository and record the exit status. - For the refusal check, use a separate fresh seat and an existing, empty non-daemon config directory under a disposable checkout. Record the expected refusal text from step 3. Keep credentials outside the checkout.
- Close with the observed results from the live run. Report only the relevant fields and exit statuses. If a check fails, leave the issue open and identify the failed step.
Affected Files
PR #14766 contains the implementation and offline tests. This issue's deliverable is the evidence comment.
loom-daemon/src/tokens_pool/private_workspace/lifecycle.rsresolves the forge configuration directory for a new private seat.loom-daemon/src/tokens_pool/private_workspace/tests.rscontains the corresponding resolution and refusal cases at the PR head above.
Out of Scope
- Source changes, credential rotation, and migration or removal of existing seats.
Metadata
Metadata
Assignees
Labels
loom:blockedWaiting on something named (another change, a capability); released once it resolvesWaiting on something named (another change, a capability); released once it resolves
Activity
loom-fleet-dispatch commentedon Nov 20, 2026
PR #14765's
loom:curatingclaim is held by the curator of sweepstep-curator-14765-1795160843on hosthost-a6032f0c. This comment is a PR lease record (#9401): its liveness signal is its own forge-assignedupdated_at, renewed while the curator works and released when it is done. Another curator that finds this lease live stands down before touching a worktree. Seedefaults/docs/lease-record.md§ "PR-phase leases".loom-fleet-dispatch commentedon Nov 20, 2026
Curating this issue per user request.
loom dashboard
loom-fleet-dispatch commentedon Nov 20, 2026
PR #14766 implements the fix for #14744 and explicitly leaves the crew-host run to this issue. The updated test plan records how to distinguish a new seat from an existing one and what evidence to collect. The PR is still open. Verification can proceed once an App-only host is running the fix.
loom dashboard