0 Fork 0

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

Files

T

DottaandClaude Fable 5 6b2d2ef1e8 Handle ACP session-config rejections inside the ACP lane instead of falling back to CLI

Review feedback on the previous fix: the point of ACPX is to stop
maintaining the CLI adapter, so recovering from a codex-acp
set_config_option rejection by switching lanes was the wrong shape.

ACP-native handling instead:
- The codex model is now applied via a `-c model=...` startup config
  override on the codex-acp command (mirroring ANTHROPIC_MODEL for
  claude). The override feeds the same config surface as
  ~/.codex/config.toml, which accepts manual model ids; verified against
  codex-acp 0.12.0 that session/new then reports the manual id as
  currentModelId while set_config_option validation rejects unlisted ids
  on older versions.
- session/set_config_option application is now best-effort: a rejected
  option (e.g. ACP -32602) logs loudly, surfaces in the run's command
  notes, and the run continues on the agent default instead of dying
  with acpx_session_config_failed.
- The ACP->CLI session-config fallback and its error-code constant are
  reverted; auto lane falls back to CLI only for startup failures, as
  before.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-10 14:37:48 +00:00

src

Handle ACP session-config rejections inside the ACP lane instead of falling back to CLI

2026-07-10 14:37:48 +00:00

CHANGELOG.md

chore: release v0.3.1

2026-03-12 13:09:22 -05:00

package.json

Make ACP the default engine for local adapters (#9238 )

2026-07-08 19:05:03 -07: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.