paperclipai/paperclip · error · PaperclipRunnerProviderProfileError

paperclip_runner_aws_agentcore_recovery_identity_mismatch

paperclip_runner_aws_agentcore_recovery_identity_mismatch

Error message

The persisted AWS AgentCore identity no longer matches its qualified profile.

What it means

Guard assertAgentCoreProfileRecoveryBinding: a recovering AWS AgentCore run's snapshot (profileId plus harnessArn, endpointArn, agentRuntimeArn, memory ARNs, context bucket/KMS, qualificationRevision, etc.) must exactly match the profile's current configuration; any drift throws 'paperclip_runner_aws_agentcore_recovery_identity_mismatch' because the underlying AgentCore resources changed and resumption would be unbound.

Source

Thrown at server/src/services/native-runtime/provider-profile.ts:291

    "harnessArn",
    "harnessVersion",
    "endpointArn",
    "endpointQualifier",
    "agentRuntimeArn",
    "memoryArn",
    "memoryId",
    "invocationRoleArn",
    "contextBucket",
    "contextPrefix",
    "contextKmsKeyArn",
    "qualificationRevision",
    "eventExpiryDays",
  ] as const;
  if (
    snapshot.profileId !== stored.id
    || fields.some((field) => snapshot[field] !== configuration[field])
  ) {
    throw new PaperclipRunnerProviderProfileError(
      "paperclip_runner_aws_agentcore_recovery_identity_mismatch",
      "The persisted AWS AgentCore identity no longer matches its qualified profile.",
    );
  }
}

/**
 * Resolve the immutable provider identity used for a fresh Paperclip Runner
 * selection. The persisted adapterConfig is the authority; runtimeConfig is
 * deliberately not consulted so model-profile or migration metadata cannot
 * silently switch the harness selected for a run.
 */
export function resolvePaperclipRunnerProviderProfile(
  adapterConfig: unknown,
): PaperclipRunnerProviderProfile {
  const config = asRecord(adapterConfig);
  const candidate = config.provider ?? "codex";
  if (!isPaperclipRunnerProvider(candidate)) {

View on GitHub (pinned to 01ad858492)

Solutions

1. Re-qualify the AgentCore profile and start a fresh run instead of recovering the stale one.
2. Restore the changed infrastructure fields (harness/endpoint/memory/context) to their snapshot values if resumption is required.
3. Verify which field diverged by diffing the snapshot against the profile configuration.

When it happens

Trigger: Thrown at server/src/services/native-runtime/provider-profile.ts:285 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of paperclipai/paperclip@01ad858492 (2026-09-02). Data as JSON: /api/errors/32df9b492dd5a4d2. Report an issue: GitHub.