0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-28 04:02:18 +01:00

Files

T

nickyleachandPaperclip 57fd03312f fix(adapter-utils): prune a Gemini managed skill only when its shape on disk is still lane-owned

The prune step removed any entry the managed-skills manifest named, with
no check of what the entry currently is. The manifest records what the
lane owned at the end of the last run, not what the entry is now. A user
could remove a managed symbolic link and write their own directory at
the same name between runs; the next prune then deleted that directory.

Add a shape check at the point of removal. A manifest-named entry is
still lane-owned only when it is a symbolic link, or a directory that
carries a valid materialized-skill sentinel. Every other shape survives
the prune, and Paperclip logs one line to record why.

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

2026-09-11 15:17:40 +00:00

src

fix(adapter-utils): prune a Gemini managed skill only when its shape on disk is still lane-owned

2026-09-11 15:17:40 +00:00

CHANGELOG.md

fix: bound workspace Git scans (#11572 )

2026-08-17 22:11:30 -05:00

package.json

feat(connections): add self-serve intent runtime (#12345 )

2026-08-29 12:08:34 -05:00

README.md

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

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

tsconfig.json

Fix root TypeScript solution config

2026-03-09 14:09:30 -05:00

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.