deepseek-ai/deepseek-harness · error · Error

invalid persisted inbox splice at session seq ${event.seq}

Error message

invalid persisted inbox splice at session seq ${event.seq}

What it means

Error "invalid persisted inbox splice at session seq ${event.seq}" thrown in deepseek-ai/deepseek-harness.

Source

Thrown at packages/core/agent/src/inbox.ts:37

  discarded(message: UserMessage): void
  /** Publish one claimed message inside its owning turn. */
  claimed(message: UserMessage, turn: number): void
}

/** A replay-once projection that incrementally consumes later inbox splices. */
export class Inbox {
  private readonly state: InboxState = { 'next-turn': [], 'next-step': [] }

  constructor(
    private readonly session: Session,
    private readonly notifications: InboxNotifications,
  ) {
    for (const event of session.events.slice(session.header.seedLength ?? 0)) {
      if (event.type !== 'agent/inbox/spliced') continue
      try {
        this.apply(event.data)
      } catch (error: unknown) {
        throw new Error(`invalid persisted inbox splice at session seq ${event.seq}`, { cause: error })
      }
    }
  }

  /** Prompts awaiting individual turns. */
  get nextTurn(): readonly UserMessage[] {
    return this.state['next-turn']
  }

  /** Input awaiting the next step boundary. */
  get nextStep(): readonly UserMessage[] {
    return this.state['next-step']
  }

  /** Whether either pending-message list contains work. */
  get hasPending(): boolean {
    return this.nextTurn.length > 0 || this.nextStep.length > 0
  }

View on GitHub (pinned to b150a551b8)

Solutions

1. Repair the persisted session log; the inbox splice at the reported seq is invalid.

When it happens

Trigger: Thrown at packages/core/agent/src/inbox.ts:37 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of deepseek-ai/deepseek-harness@b150a551b8 (2026-08-24). Data as JSON: /api/errors/234704b4e122dccc. Report an issue: GitHub.