Define workspace, state, and credential boundaries #9

Closed
opened 2026-08-22 22:21:19 -04:00 by jb · 0 comments
Owner

Part of #1

Blocked by: #2, #4, #8

Question

What host-to-sandbox path mappings and ownership rules apply to an existing workspace versus a Paseo-owned worktree, dedicated Pi session storage, minimal agent state, generated launch files, and narrowly scoped credentials? Settle exact-path preservation, linked-worktree Git metadata, validation, read/write modes, Docker mount provenance, OAuth refresh coordination, partial-create rollback, archive/delete behavior, and protection from another agent session, daemon state, ambient home files, or host devices.

Part of #1 Blocked by: #2, #4, #8 ## Question What host-to-sandbox path mappings and ownership rules apply to an existing workspace versus a Paseo-owned worktree, dedicated Pi session storage, minimal agent state, generated launch files, and narrowly scoped credentials? Settle exact-path preservation, linked-worktree Git metadata, validation, read/write modes, Docker mount provenance, OAuth refresh coordination, partial-create rollback, archive/delete behavior, and protection from another agent session, daemon state, ambient home files, or host devices.
jb added the wayfinder:grilling label 2026-08-22 22:21:19 -04:00
jb changed title from Define workspace, image, state, and credential boundaries to Define workspace, state, and credential boundaries 2026-08-22 22:38:10 -04:00
jb closed this issue 2026-08-23 01:22:11 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jb/paseo#9