0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-14 08:26:46 +02:00

Files

T

Priya RamanandPaperclip 223068e2ff fix(sandbox): keep bridge queue-directory setup on the startup step

The paperclip callback bridge reset the active startup-step store for the
whole worker start. That also unparented the awaited queue-directory setup
execs, which are startup work and must keep the `bridge.paperclip` step.

Move the store reset to the long-lived poll loop inside the worker. The
`makeDir` setup now keeps the active step, so its `sandbox.exec` spans stay
parented with the correct `criticalPath` flag. The loop still runs with an
empty store, so each run-time exec span opens unparented.

Add a regression test that reads the active step during setup and during the
first poll, and proves the boundary sits at the loop, not the whole worker.

Co-authored-by: Paperclip <noreply@paperclip.ing>

2026-08-04 06:40:12 +00:00

src

fix(sandbox): keep bridge queue-directory setup on the startup step

2026-08-04 06:40:12 +00:00

CHANGELOG.md

…

package.json

build(deps-dev): bump @types/node from 22.19.21 to 22.20.1 (#10304 )

2026-07-28 10:48:45 -07:00

README.md

PAPA-430: workspace finalize gates + no-remote-git enforcement (#6969 )

2026-05-29 08:25:29 -07:00

tsconfig.json

…

README.md

@paperclipai/adapter-utils

Shared utilities for Paperclip adapters: process spawning, environment injection, sandbox/SSH transport, workspace sync, and the round-trip helpers that move code between the local execution-workspace cwd and wherever the agent actually runs.

For the adapter-author guide see docs/adapters/creating-an-adapter.md and the in-repo notes at packages/adapters/AUTHORING.md.

No-remote-git contract

The local execution-workspace cwd is the only persistence boundary across runs. No adapter may depend on a git remote for cross-run state.

Adapters that run the agent on a different host should use the SSH round-trip helpers in src/ssh.ts:

prepareWorkspaceForSshExecution({ spec, localDir, remoteDir }) — bundles the local cwd (tracked files, dirty edits, untracked additions, and the git history needed to reconstruct it) to remoteDir before the run starts. Runs with no git remote configured.
restoreWorkspaceFromSshExecution({ spec, localDir, remoteDir, ... }) — syncs the remote cwd back into localDir after the run, including any new commits the agent created. Also runs with no git remote configured.

prepareRemoteManagedRuntime in src/remote-managed-runtime.ts wraps both calls for adapters that want a per-run remote workspace and an automatic restoreWorkspace() finally hook.

The invariant is pinned by the no-remote-git contract case in src/ssh-fixture.test.ts, which asserts that a remote-only commit propagates to the local worktree through the prepare → restore round-trip with no git remote configured at any point. Do not regress that test.