0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-27 19:35:13 +01:00

Files

T

nickyleachandPaperclip 53bf0667b8 fix(server): bound origin messages by the item cap, and disclose truncation on every capped list

Origin messages could bypass the item cap: when more than 30 wake
comments were origin messages, the cap kept all of them and let
messages and resumeDelta.messages grow without limit. The cap now
keeps only the newest 30 origin messages when there are more origins
than the cap allows.

completedActions, interactionOutcomes, unresolvedInteractionIds, and
recoveryOutcomes could drop items with no signal to the agent. Each
list now reports its own omitted count, and the wake prompt states the
count so the agent does not treat a capped durable-action list as
complete.

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

2026-09-10 19:47:41 -07:00

src

fix(server): bound origin messages by the item cap, and disclose truncation on every capped list

2026-09-10 19:47:41 -07: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.