0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-29 04:25:52 +01:00

Files

T

DottaandClaude Fable 5 8c46620678 Fall back to Codex CLI when ACP rejects session configuration

A codex_local agent configured with a manual model id (e.g. gpt-5.5-pro)
failed every ACP-lane run with acpx_session_config_failed: codex-acp
validates session/set_config_option values against its internal model
list and rejects ids it does not advertise (ACP -32602), even though the
Codex CLI lane accepts manual model ids via --model.

The existing ACP->CLI fallback only covered thrown startup errors, not
structured failed results from the configure_session phase. Auto-selected
ACP now falls back to the CLI lane when the ACP server rejects session
configuration, preserving the configured model/effort/fast-mode via
startup args. Explicit engine=acp remains strict and fails loudly.

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

2026-07-10 13:33:50 +00:00

src

Fall back to Codex CLI when ACP rejects session configuration

2026-07-10 13:33:50 +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.