{"repo":"NousResearch/hermes-agent","public_id":"82484","display_label":"Docker credential volume mount conflict fixes","summary":"These items address a conflict where skill auto-mounting of credential volumes collides with or overrides explicit read-write mounts, particularly affecting OAuth token refresh in Docker sandboxes. The changes aim to prefer explicit volume mount configurations over automatic ones.","subsystem":"environments","counts":{"members":4,"open_issues":1,"open_issues_distinct":1,"open_prs":1,"closed_issues":0,"merged_prs":0,"attempt_prs":3},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.5},"fix_edges":[],"members":[{"kind":"issue","number":82484,"title":"Docker sandbox: Google OAuth refresh needs a writable token, but skill auto-mount duplicates explicit rw bind as ro","url":null,"state":"open"},{"kind":"pr","number":82498,"title":"Fix docker credential volume collision","url":null,"state":"closed","close_reason":{"category":"silent_close","implication":"active"},"merged":false},{"kind":"pr","number":82504,"title":"fix(docker): let OAuth refresh use explicit writable token mounts","url":null,"state":"open","close_reason":{"category":"silent_close","implication":"active"},"merged":false},{"kind":"pr","number":82511,"title":"fix(docker): prefer explicit credential volume mounts","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#82504","number":82504}],"category":"duplicate_of","implication":"duplicate"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}