Files
PaperClipAI/ui/src/components/interrupt-handoff/InterruptHandoffViews.tsx
T
67b22d872f [codex] Clarify interrupt handoffs and scoped wake semantics (#7855)
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work.
> - The issue thread is the operator surface where comments, assignee
changes, pauses, resumes, and wakeups turn human intent into agent
execution.
> - Interrupting a live run and handing work to another assignee needs
clear semantics so the product does not accidentally keep work alive,
wake the wrong participant, or hide why an agent stopped.
> - Comment-driven wakes also need strict boundaries so closed, blocked,
and dependency-driven work only resumes when there is real actionable
input.
> - This pull request codifies the interrupt handoff contract,
implements backend scheduling behavior, and gives the UI clearer
handoff/pause language.
> - The benefit is a more inspectable and predictable task lifecycle for
both operators and agents.

## Linked Issues or Issue Description

Paperclip issue: `PAP-10664` / `PAP-10751`.

Problem: interrupting or reassigning live agent work could be ambiguous
in the UI and backend. Operators needed clearer feedback about whether a
handoff wakes an agent, what pause/cancel affects, and when comments
should revive execution. The backend also needed stronger tests around
comment wake boundaries, retry supersession, and structured agent
mention dispatch.

Related GitHub PR search found broad workflow-adjacent PRs #5082, #6359,
and #4083, but no exact duplicate for this head branch or
interrupt-handoff scope.

## What Changed

- Added an interrupt handoff semantics document covering destination
behavior, wake expectations, and live-run interruption states.
- Implemented backend interrupt handoff behavior and comment wake/reopen
handling in issue routes/services and heartbeat scheduling.
- Hardened structured agent mention dispatch so mentions resolve through
the intended dispatch path.
- Added UI helpers and components for handoff chips, wake rows,
interrupt banners, pause-affects summaries, and composer guidance.
- Updated the issue properties assignee picker and issue chat/composer
surfaces to make interrupt/reassign behavior clearer.
- Added backend, UI utility, component, and Storybook coverage for the
new behavior.
- Stabilized the new UI component tests with a local `flushSync`-backed
act helper matching existing repo practice in this dependency set.
- Addressed Greptile feedback by threading historical run `errorCode`
through issue-run data and operator-interrupted chat labels.
- Addressed Greptile's cancel ordering concern by terminating/deleting
in-memory heartbeat processes before cancellation status persistence,
with regression coverage for DB update failure.

## Verification

- `git diff --check $(git merge-base HEAD origin/master)..HEAD`
- `pnpm --filter @paperclipai/ui exec vitest run
src/lib/interrupt-handoff.test.ts src/lib/issue-chat-messages.test.ts
src/components/IssueProperties.test.tsx
src/components/interrupt-handoff/InterruptHandoffViews.test.tsx
--no-file-parallelism --maxWorkers=1` — 4 files / 91 tests passed before
the Greptile follow-ups.
- `pnpm run preflight:workspace-links && pnpm exec vitest run
server/src/__tests__/heartbeat-process-recovery.test.ts
server/src/__tests__/heartbeat-retry-scheduling.test.ts
server/src/__tests__/issue-comment-reopen-routes.test.ts
server/src/__tests__/issue-tree-control-service.test.ts
server/src/__tests__/issue-update-comment-wakeup-routes.test.ts
server/src/__tests__/issues-service.test.ts --no-file-parallelism
--maxWorkers=1` — 6 files / 191 tests passed before the Greptile
follow-ups.
- `pnpm --filter @paperclipai/ui exec vitest run
src/lib/issue-chat-messages.test.ts --no-file-parallelism
--maxWorkers=1` — 1 file / 24 tests passed after the historical
`errorCode` follow-up.
- `pnpm exec vitest run server/src/__tests__/activity-service.test.ts
server/src/__tests__/activity-routes.test.ts --no-file-parallelism
--maxWorkers=1` — 2 files / 11 tests passed after the historical
`errorCode` follow-up.
- `pnpm exec vitest run
server/src/__tests__/heartbeat-process-recovery.test.ts
--no-file-parallelism --maxWorkers=1` — 1 file / 52 tests passed after
the cancel ordering follow-up.
- Greptile is green for head `272647636287d034bab8d981eaf5305865aa0f96`;
the old inline P2 is resolved/outdated.
- GitHub Actions, Socket, security-review, and Greptile checks are green
for head `272647636287d034bab8d981eaf5305865aa0f96`. The external
`security/snyk (cryppadotta)` status was still pending at
`https://app.snyk.io/org/cryppadotta/pr-checks/85b3e8f4-04e1-4f8e-9362-899c8148c23c`
after a bounded wait.

## Risks

- Medium: changes touch issue comments, wake scheduling, and live-run
interruption semantics, so regressions could affect when agents resume
or stay stopped.
- Medium: UI copy and state grouping for assignee changes may need
reviewer tuning after product review.
- Low migration risk: no database schema migration is included.
- The branch was created before the latest `origin/master` commits;
reviewers should confirm CI merge-base behavior and resolve any merge
conflicts if GitHub reports them.

> For core feature work, check [`ROADMAP.md`](ROADMAP.md) first and
discuss it in `#dev` before opening the PR. Feature PRs that overlap
with planned core work may need to be redirected — check the roadmap
first. See `CONTRIBUTING.md`.

## Model Used

OpenAI Codex, GPT-5-based coding agent, tool use and local command
execution enabled. Exact hosted model build and context window were not
exposed by the runtime.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [ ] If this change affects the UI, I have included before/after
screenshots
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

Screenshot note: this PR includes Storybook coverage for the new
interrupt handoff UI states rather than captured before/after browser
screenshots in this PR-creation heartbeat.

---------

Co-authored-by: Paperclip <noreply@paperclip.ing>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-09 21:57:21 -05:00

350 lines
11 KiB
TypeScript

import { AlertTriangle, Info, PauseCircle, User, X } from "lucide-react";
import { cn } from "../../lib/utils";
import { AgentIcon } from "../AgentIconPicker";
import {
classifyAssigneeHandoff,
resolveRunStatusPresentation,
type ComposerHandoffPreview,
type PauseAffectsSummary,
type PlainAgentNameCandidate,
type ReassignInterruptCopy,
type TimelineAssigneeLike,
} from "../../lib/interrupt-handoff";
/**
* Presentational views for the interrupt-handoff UX clarity surfaces (PAP-10669).
* All logic lives in `lib/interrupt-handoff.ts`; these components only render it,
* so they can be exercised in isolation by component tests and Storybook.
*/
export interface HandoffAgentLike {
name: string;
icon?: string | null;
}
export interface HandoffChipResolvers {
agentMap?: ReadonlyMap<string, HandoffAgentLike> | null;
resolveUserLabel?: (userId: string) => string | null;
currentUserId?: string | null;
}
function agentName(agentId: string, resolvers: HandoffChipResolvers): string {
return resolvers.agentMap?.get(agentId)?.name ?? agentId.slice(0, 8);
}
function agentIcon(agentId: string, resolvers: HandoffChipResolvers): string | null {
return resolvers.agentMap?.get(agentId)?.icon ?? null;
}
function userLabel(userId: string, resolvers: HandoffChipResolvers): string {
const label = resolvers.resolveUserLabel?.(userId) ?? null;
const base = label ?? "Board";
return resolvers.currentUserId && resolvers.currentUserId === userId ? `${base} (you)` : base;
}
const CHIP_CLASS =
"inline-flex items-center gap-1 rounded-full border border-border bg-muted/40 px-2 py-0.5 text-xs";
/** A labelled assignee chip — agent, user, or unassigned — that never lets a
* user owner read like an agent. */
export function AssigneeChip({
assignee,
resolvers,
className,
}: {
assignee: TimelineAssigneeLike;
resolvers: HandoffChipResolvers;
className?: string;
}) {
if (assignee.agentId) {
return (
<span className={cn(CHIP_CLASS, className)} data-testid="handoff-assignee-chip" data-kind="agent">
<span className="sr-only">Agent </span>
<AgentIcon icon={agentIcon(assignee.agentId, resolvers)} className="h-3 w-3 shrink-0 text-muted-foreground" />
<span className="max-w-[12rem] truncate">{agentName(assignee.agentId, resolvers)}</span>
</span>
);
}
if (assignee.userId) {
return (
<span className={cn(CHIP_CLASS, className)} data-testid="handoff-assignee-chip" data-kind="user">
<span className="sr-only">User </span>
<User className="h-3 w-3 shrink-0 text-muted-foreground" />
<span className="max-w-[12rem] truncate">{userLabel(assignee.userId, resolvers)}</span>
</span>
);
}
return (
<span
className={cn("text-xs italic text-muted-foreground", className)}
data-testid="handoff-assignee-chip"
data-kind="unassigned"
>
<span className="sr-only">No assignee — </span>
Unassigned
</span>
);
}
/** The "Wake" sub-row that makes each handoff state self-describing: a queued
* agent wake, a board-user handoff with no wake, or no agent selected. */
export function HandoffWakeRow({
to,
resolvers,
interruptedRunAttached = false,
}: {
to: TimelineAssigneeLike;
resolvers: HandoffChipResolvers;
interruptedRunAttached?: boolean;
}) {
const info = classifyAssigneeHandoff(to, {
agentName: to.agentId ? agentName(to.agentId, resolvers) : null,
interruptedRunAttached,
});
return (
<div
className="flex flex-wrap items-center gap-1.5 text-xs"
data-testid="handoff-wake-row"
data-kind={info.kind}
>
<span className="text-xs font-medium uppercase tracking-wider text-muted-foreground">Wake</span>
<span className={cn(info.kind === "agent_wake" ? "text-foreground" : "text-muted-foreground")}>
{info.wakeText}
</span>
</div>
);
}
/** Run status text that distinguishes an intentional operator interrupt
* (amber "interrupted") from a generic muted "cancelled". */
export function RunStatusBadge({
status,
operatorInterrupted = false,
className,
}: {
status: string;
operatorInterrupted?: boolean;
className?: string;
}) {
const p = resolveRunStatusPresentation(status, { operatorInterrupted });
return (
<span
className={cn("font-medium", p.className, className)}
data-testid="run-status-badge"
data-interrupted={operatorInterrupted ? "true" : "false"}
>
{p.label}
{p.srHint ? <span className="sr-only"> — {p.srHint}</span> : null}
</span>
);
}
function PreviewChip({
chip,
resolvers,
}: {
chip: NonNullable<ComposerHandoffPreview["chip"]>;
resolvers: HandoffChipResolvers;
}) {
return (
<AssigneeChip
assignee={chip.kind === "agent" ? { agentId: chip.id, userId: null } : { agentId: null, userId: chip.id }}
resolvers={resolvers}
/>
);
}
/** One-line interpretation of what submitting the comment will durably do. */
export function ComposerHandoffPreviewRow({
preview,
resolvers,
}: {
preview: ComposerHandoffPreview;
resolvers: HandoffChipResolvers;
}) {
if (preview.kind === "none") return null;
return (
<div
className={cn(
"flex flex-wrap items-center justify-end gap-1.5 text-xs",
preview.tone === "warn" ? "text-amber-700 dark:text-amber-300" : "text-muted-foreground",
)}
data-testid="composer-handoff-preview"
data-kind={preview.kind}
role="status"
aria-live="polite"
>
<span>{preview.text}</span>
{preview.chip ? <PreviewChip chip={preview.chip} resolvers={resolvers} /> : null}
{preview.suffix ? <span>{preview.suffix}</span> : null}
</div>
);
}
/** Inline coach shown when the body contains a plain agent name without a chip,
* offering a one-click upgrade to a real mention. */
export function ComposerMentionCoach({
candidate,
agentDisplayName,
onInsert,
onDismiss,
}: {
candidate: PlainAgentNameCandidate;
agentDisplayName: string;
onInsert: () => void;
onDismiss: () => void;
}) {
return (
<div
className="flex items-center gap-2 rounded-md border border-amber-300/40 bg-amber-50/70 px-2 py-1.5 text-xs text-amber-700 dark:bg-amber-500/10 dark:text-amber-300"
data-testid="composer-mention-coach"
role="alert"
aria-live="polite"
>
<Info className="h-3.5 w-3.5 shrink-0" aria-hidden />
<span className="min-w-0 flex-1">
Did you mean <span className="font-medium">@{candidate.matchedText}</span>? Plain text won't
notify or assign an agent.
</span>
<button
type="button"
onClick={onInsert}
className="shrink-0 rounded border border-amber-400/50 px-1.5 py-0.5 font-medium hover:bg-amber-100/60 dark:hover:bg-amber-500/20"
aria-label={`Insert mention for ${agentDisplayName} into your comment`}
>
Insert mention
</button>
<button
type="button"
onClick={onDismiss}
className="shrink-0 rounded p-0.5 hover:bg-amber-100/60 dark:hover:bg-amber-500/20"
aria-label="Dismiss suggestion"
>
<X className="h-3.5 w-3.5" aria-hidden />
</button>
</div>
);
}
/** Live banner shown at the top of the assignee picker while a run is in flight,
* warning that reassigning will interrupt it. (design surface 2) */
export function AssigneeRunningBanner({
copy,
className,
}: {
copy: ReassignInterruptCopy;
className?: string;
}) {
return (
<div
role="status"
aria-live="polite"
data-testid="assignee-running-banner"
className={cn(
"flex items-start gap-1.5 rounded-md border border-amber-300/40 bg-amber-50/70 px-2 py-1.5 text-xs text-amber-700 dark:bg-amber-500/10 dark:text-amber-300",
className,
)}
>
<AlertTriangle className="mt-0.5 h-3.5 w-3.5 shrink-0" aria-hidden />
<span className="min-w-0 flex-1">{copy.banner}</span>
</div>
);
}
/** "Interrupt & assign" confirm step shown when an operator picks a different
* target while a run is live. (design surface 2) */
export function InterruptAssignConfirm({
copy,
to,
resolvers,
onConfirm,
onCancel,
}: {
copy: ReassignInterruptCopy;
/** The target the operator selected. */
to: TimelineAssigneeLike;
resolvers: HandoffChipResolvers;
onConfirm: () => void;
onCancel: () => void;
}) {
return (
<div
data-testid="interrupt-assign-confirm"
className="space-y-2 rounded-md border border-amber-300/40 bg-amber-50/70 p-2 text-xs text-amber-700 dark:bg-amber-500/10 dark:text-amber-300"
>
<div className="flex items-start gap-1.5">
<AlertTriangle className="mt-0.5 h-3.5 w-3.5 shrink-0" aria-hidden />
<div className="min-w-0 flex-1 space-y-1">
<p className="font-medium">{copy.confirmTitle}</p>
<p className="flex flex-wrap items-center gap-1 text-amber-700/90 dark:text-amber-300/90">
<span>Hand off to</span>
<AssigneeChip assignee={to} resolvers={resolvers} />
</p>
</div>
</div>
<div className="flex justify-end gap-2">
<button
type="button"
onClick={onCancel}
className="rounded border border-amber-400/50 px-2 py-0.5 font-medium hover:bg-amber-100/60 dark:hover:bg-amber-500/20"
>
{copy.cancelAction}
</button>
<button
type="button"
onClick={onConfirm}
data-testid="interrupt-assign-confirm-action"
className="rounded bg-amber-600 px-2 py-0.5 font-medium text-white hover:bg-amber-700 dark:bg-amber-500 dark:hover:bg-amber-400"
>
{copy.confirmAction}
</button>
</div>
</div>
);
}
/** "What this affects" bucket summary for the pause/hold dialog. (design surface 4) */
export function PauseAffectsSummaryView({
summary,
className,
}: {
summary: PauseAffectsSummary;
className?: string;
}) {
const visibleBuckets = summary.buckets.filter((bucket) => bucket.count > 0);
return (
<div
data-testid="pause-affects-summary"
className={cn("space-y-2 rounded-md border border-border bg-muted/30 p-3", className)}
>
<div className="flex items-center gap-1.5 text-xs font-medium uppercase tracking-wider text-muted-foreground">
<PauseCircle className="h-3.5 w-3.5" aria-hidden />
What this affects
</div>
{summary.nothingLive ? (
<p role="status" className="text-xs text-muted-foreground" data-testid="pause-nothing-live">
Nothing live to pause — no agent run is in flight or queued. This records a hold so new work
won't start until you resume.
</p>
) : null}
{visibleBuckets.length > 0 ? (
<ul className="space-y-1">
{visibleBuckets.map((bucket) => (
<li
key={bucket.key}
data-bucket={bucket.key}
className="flex flex-wrap items-baseline gap-x-1.5 gap-y-0.5 text-xs"
>
<span className="font-medium text-foreground">{bucket.label}:</span>
<span className="tabular-nums text-foreground">{bucket.count}</span>
<span className="text-muted-foreground">— {bucket.detail}</span>
</li>
))}
</ul>
) : (
<p className="text-xs text-muted-foreground">No tasks are affected.</p>
)}
</div>
);
}