Files
kandev/docs/plans/attach-workspace-sources/task-05-remote-materialization.md
T
Carlos Florêncio bc218dfbbe feat: add workspace sources from files panel (#1900)
* feat: add workspace sources from files panel

* fix: preserve worktree identity during recovery

* feat: unify workspace source actions

* fix: validate recovered workspace repositories

* fix: harden workspace source filesystem boundaries

* test: split workspace repository chip coverage

* fix: restrict repository rescan recovery paths

* fix: stabilize workspace source CI checks

* test: canonicalize workspace source paths

* test: align workspace source container paths

* fix: populate direct workspace repository names

* test: preserve git fixture rewrites across restarts

* test: isolate backend git fixture config

* fix: resume remote workspace executions before creation

* fix: preserve ssh agent identity during resume

* fix: preserve SSH workspace across backend restart

* fix: simplify workspace actions trigger

* fix: refine add workspace repositories UX

* docs: narrow workspace source UX updates

* fix: avoid phantom turn on session resume

* test(web): normalize workspace source request headers

* feat(web): streamline workspace source picker

* docs: remove trailing spaces from workspace source plan

* fix: prevent resume status from creating phantom turns

* fix(web): stabilize workspace source attachment

* refactor(web): extract workspace source store contract

* fix: avoid phantom turns on idle agent resume

* fix: address backend static analysis findings

* fix: preserve agentctl readiness status value

* fix: preserve resume messages without active turns

* fix: resume agents from promoted workspace root

* chore: merge origin/main into feature/add-new-repo-folder-d97

* feat(web): explain workspace source consequences

* test(websocket): count session activity subscription
2026-07-25 21:29:53 +01:00

2.2 KiB

id, title, status, wave, depends_on, plan, spec
id title status wave depends_on plan spec
05-remote-materialization Remote materialization done 4
03-protocol-surfaces
04-host-materialization
plan.md ../../specs/tasks/attach-workspace-sources.md

Task 05: Remote Materialization

Acceptance

  • Agentctl can atomically clone/checkout a validated repository into a collision-checked workspace subdirectory with cancellation and cleanup defenses.
  • Docker, SSH, and Sprites use their live agentctl clients and existing credential resolution to materialize and rescan repository sources; secrets are absent from logs and metadata.
  • Container and remote folder requests are rejected before persistence or filesystem access, and the same executor capability is available to the frontend picker.
  • New/reset environments rebuild all durable sources, and adapter tests cover failure rollback plus the future remote-Docker capability boundary.

Verification

cd apps/backend
rtk go test ./internal/agentctl/... ./internal/agent/runtime/lifecycle/... ./internal/backendapp/...

Files likely touched

  • apps/backend/internal/agentctl/client_workspace_sources.go (new)
  • apps/backend/internal/agentctl/server/api/workspace_sources.go (new)
  • apps/backend/internal/agentctl/server/api/workspace_sources_test.go (new)
  • apps/backend/internal/agentctl/server/api/server.go
  • apps/backend/internal/agentctl/server/process/manager.go
  • apps/backend/internal/agent/runtime/lifecycle/executor_docker.go
  • apps/backend/internal/agent/runtime/lifecycle/executor_ssh.go
  • apps/backend/internal/agent/runtime/lifecycle/executor_sprites.go
  • apps/backend/internal/agent/runtime/lifecycle/executor_remote_docker.go
  • apps/backend/internal/agent/runtime/lifecycle/manager_launch.go
  • executor/materialization tests beside those files

Dependencies

Tasks 03 and 04.

Inputs

  • Spec: executor source capabilities, credential boundary, persistence, failure modes.
  • Existing workspace/copy-files, remote copy-files, Docker prepare, SSH upload, and Sprites file uploader patterns.

Output contract

Summary, files changed, tests run, blockers, risks, divergence, and task/plan status updates.