Files
PaperClipAI/ui/src/components/PropertiesPanel.tsx
T
scotttongandClaude Fable 5 c185e64b77 feat(ui): chat-style task view behind an experimental flag (#10606)
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work.
> - Operators spend most of their time on the issue detail page. They
talk to the assigned agent there through comments.
> - The current page reads as a ticket form. The thread sits below
properties, the composer sits mid-page, and live agent activity renders
as dense transcript logs.
> - Talking to an agent is a conversation. A chat-first layout matches
that mental model better than a ticket form.
> - A layout change this large must not disrupt current users. It needs
a safe opt-in path and full parity with the existing thread features.
> - This pull request adds a chat-style task view behind a new
"Chat-Style Tasks" experiment toggle. The flag is off by default and the
existing page is unchanged when it is off.
> - The benefit is a focused, readable conversation with the agent: live
tool activity folds into compact summaries, the composer stays at the
bottom, and properties, plan, and artifacts move into header tabs.

## Linked Issues or Issue Description

Refs #49 (chat with agents is a much-wanted feature).

Related PRs found in the dedup search:
- #4489 — an earlier, closed attempt to promote the conversation to the
primary surface on issue detail. This PR is a fresh, flag-gated take on
the same goal.
- #8837 — an open PR that proposes a two-column task layout. It
restructures the same page but keeps the ticket paradigm; this PR is
orthogonal because it is opt-in and chat-first.

**Subsystem affected**

UI (issue detail page).

**Problem or motivation**

The issue detail page presents agent conversations as a ticket:
properties first, thread below, composer in the middle of the page, and
raw transcript noise during live runs. Users who mainly converse with
their agents must scroll past chrome to follow the conversation, and
live activity is hard to read.

**Proposed solution**

An opt-in chat-style view of the issue detail page, gated by a new
"Chat-Style Tasks" experiment toggle in Settings → Experimental. With
the flag on, the thread fills the center pane, the composer docks to the
bottom of the viewport, Properties / Plan / Artifacts become header
tabs, live turns show a status pill with the current tool action and
elapsed time, and settled turns collapse to a "Worked · N tools" summary
that expands into per-tool rows. With the flag off, nothing changes.

**Alternatives considered**

Restyling the existing layout in place (rejected: too disruptive without
an opt-out), and a separate chat page beside the issue page (rejected:
splits the task's single source of truth). A per-request lab page
(`/task-chat-lab`, dev-only) was kept for design iteration instead.

**Roadmap alignment**

ROADMAP.md "CEO Chat" wants lighter conversations that still resolve to
real work objects. This PR keeps the core task-and-comments model — it
only changes presentation, opt-in — so it does not duplicate that
planned work.

## What Changed

- New `enableTaskChatRedesign` instance setting, exposed as a
"Chat-Style Tasks" experiment card in Settings → Experimental (shared
feature catalog, validators, server instance-settings service, and UI
settings page).
- New `ui/src/components/task-chat/` component family: chat thread with
turn grouping, agent reply bubbles, live status pill, collapsible turn
summaries with per-tool rows, plan tab with a sticky CTA action bar,
inline interaction cards, per-request mode chips, and a bottom-docked
composer.
- A shared tool taxonomy (`tool-taxonomy.ts`) maps tool names to verbs
and icons; the status pill, tool rows, and the classic transcript view
all use it.
- A transcript adapter converts stored run logs into chat turns; it
dedupes tool-call updates by `toolUseId` so tool counts match the
expanded rows, and it keeps a tool row's first real name when later
generic updates arrive.
- Composer: posts on Cmd/Ctrl+Enter, supports image paste with
object-URL thumbnail previews (revoked on clear/unmount), and uploads
through the issue attachments route.
- `IssueDetail.tsx`: with the flag on, pane tabs move to the header bar,
the header is not sticky, and the chat fills the center; with the flag
off, the previous layout renders unchanged.
- Motion tokens for the new animations live in `ui/src/index.css` with a
`motion-tokens.ts` catalog and a test that keeps the two in sync (the
catalog now also covers the shared enter/exit/swap tokens that the
decision/quicklook block declares).
- A dev-only `/task-chat-lab` page with fixtures and a tweak panel for
motion tuning.

## Verification

- `pnpm typecheck` — clean across the workspace.
- `pnpm check:token-gates` — 3/3 CLEAN.
- `cd ui && pnpm vitest run` — 3,344 of 3,345 tests pass locally. The
one failure is `IssueProperties.test.tsx` monitor-row time formatting,
which is timezone-sensitive: it also fails on unmodified `origin/master`
in a non-UTC timezone and passes with `TZ=UTC`. It is not related to
this change.
- `cd server && pnpm vitest run
src/__tests__/instance-settings-service.test.ts` — 21/21 pass (covers
the new setting).
- Manual: start the dev server, open Settings → Experimental, enable
"Chat-Style Tasks", and open any issue. The thread fills the page, the
composer docks to the bottom, and Properties / Plan / Artifacts appear
as header tabs. Assign an agent and comment to watch a live run: the
status pill shows the current tool action with elapsed time, and the
finished turn folds into a "Worked · N tools" summary. Disable the
toggle and confirm the classic page is unchanged.
- Visual snapshot baselines are intentionally not updated: per
`doc/design/DECISION-SHEET.md`, "Per-change snapshot verification
demoted to dormant (Jul 13 2026)".

## Risks

- The flag-off path goes through the same `IssueDetail.tsx` file, so a
regression there would affect current users. Mitigation: the classic
markup renders through the same components as before behind explicit
flag conditionals, and the full UI suite passes.
- The transcript adapter interprets stored run-log formats, including
legacy entries without `toolUseId`. Malformed logs degrade to generic
tool rows rather than crashing.
- The new view changes no server behavior other than one additive
instance setting; it is additive and default-off. Overall risk with the
flag off is low.

## Model Used

- Claude (Anthropic), model id `claude-fable-5` (Claude Fable 5),
extended thinking enabled, agentic tool use (file editing, shell, test
execution) via Claude Code / Claude Agent SDK.

## 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 not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [ ] All Paperclip CI gates are green
- [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-08-01 02:26:47 -07:00

400 lines
14 KiB
TypeScript

import { useCallback, useEffect, useRef, useState, type ReactNode } from "react";
import { Maximize2, Minimize2, X } from "lucide-react";
import { usePanel } from "../context/PanelContext";
import { useTaskChatRedesignEnabled } from "../hooks/useTaskChatRedesignEnabled";
import { cn } from "../lib/utils";
import { Button } from "@/components/ui/button";
import { ScrollArea } from "@/components/ui/scroll-area";
export function PropertiesPanel() {
const { panelContent, panelVisible, setPanelVisible } = usePanel();
const { enabled: redesignEnabled } = useTaskChatRedesignEnabled();
if (!panelContent) return null;
if (!redesignEnabled) {
return (
<aside
className="hidden md:flex border-l border-border bg-card flex-col shrink-0 overflow-hidden transition-(--tp-width-opacity) duration-200 ease-in-out h-full"
style={{ width: panelVisible ? 320 : 0, opacity: panelVisible ? 1 : 0 }}
>
<div className="w-80 flex-1 flex flex-col min-w-(--sz-320px) min-h-0">
<div className="flex items-center justify-between px-4 py-2 border-b border-border">
<span className="text-sm font-medium">Properties</span>
<Button variant="ghost" size="icon-xs" onClick={() => setPanelVisible(false)}>
<X className="h-4 w-4" />
</Button>
</div>
<ScrollArea className="flex-1">
<div className="p-4">{panelContent}</div>
</ScrollArea>
</div>
</aside>
);
}
return (
<ResizablePropertiesPanel
panelContent={panelContent}
panelVisible={panelVisible}
setPanelVisible={setPanelVisible}
/>
);
}
/* ------------------------------------------------------------------------- *
* Task Chat Redesign (flag: enableTaskChatRedesign) — resizable/maximizable
* variant. Everything below renders only when the flag is ON.
* ------------------------------------------------------------------------- */
/**
* Portal target in the redesigned pane's header bar: hosted content (the
* Properties | Plan | Artifacts tab strip) renders here, left of the window
* controls. See IssueProperties' flag-ON shell.
*/
export const PROPERTIES_PANE_HEADER_SLOT_ID = "properties-pane-header-slot";
/**
* Portal target pinned below the pane's scroll area: hosted content (the plan
* confirmation action bar) renders here so it stays visible while the pane
* body scrolls.
*/
export const PROPERTIES_PANE_FOOTER_SLOT_ID = "properties-pane-footer-slot";
const WIDTH_STORAGE_KEY = "taskChatRedesign.propertiesPaneWidth";
const DEFAULT_PANE_WIDTH = 322;
const MIN_PANE_WIDTH = 260;
/** ~236px sidebar + ~420px minimum center column stay usable while resizing. */
const RESERVED_LAYOUT_WIDTH = 656;
/** Content cap while maximized so text doesn't span the full viewport. */
const MAXIMIZED_CONTENT_MAX_WIDTH = 840;
/**
* Defensive fallback (in milliseconds) for the restore glide in case
* `transitionend` never fires; slightly longer than the --motion-pane-glide
* token in index.css.
*/
const RESTORE_FALLBACK_DELAY = 400;
function clampPaneWidth(width: number): number {
const max =
typeof window === "undefined"
? Number.POSITIVE_INFINITY
: Math.max(MIN_PANE_WIDTH, window.innerWidth - RESERVED_LAYOUT_WIDTH);
return Math.min(Math.max(Math.round(width), MIN_PANE_WIDTH), max);
}
function readStoredPaneWidth(): number {
if (typeof window === "undefined") return DEFAULT_PANE_WIDTH;
try {
const raw = window.localStorage.getItem(WIDTH_STORAGE_KEY);
const parsed = raw === null ? Number.NaN : Number(raw);
return Number.isFinite(parsed) ? parsed : DEFAULT_PANE_WIDTH;
} catch {
return DEFAULT_PANE_WIDTH;
}
}
function persistPaneWidth(width: number) {
if (typeof window === "undefined") return;
try {
window.localStorage.setItem(WIDTH_STORAGE_KEY, String(width));
} catch {
// Ignore storage failures.
}
}
function clearStoredPaneWidth() {
if (typeof window === "undefined") return;
try {
window.localStorage.removeItem(WIDTH_STORAGE_KEY);
} catch {
// Ignore storage failures.
}
}
function prefersReducedMotion(): boolean {
if (typeof window === "undefined" || typeof window.matchMedia !== "function") return false;
return window.matchMedia("(prefers-reduced-motion: reduce)").matches;
}
/** Fixed-position geometry while the panel is maximized (or gliding). */
interface FixedPane {
top: number;
/** Animated by the .tc-pane-glide transition. */
left: number;
/** Distance from the viewport's right edge to the panel's right edge. */
rightInset: number;
/** Glide target: the layout row's left edge (flush with the sidebar). */
parentLeft: number;
}
interface ResizablePropertiesPanelProps {
panelContent: ReactNode;
panelVisible: boolean;
setPanelVisible: (visible: boolean) => void;
}
function ResizablePropertiesPanel({
panelContent,
panelVisible,
setPanelVisible,
}: ResizablePropertiesPanelProps) {
const [width, setWidth] = useState(() => clampPaneWidth(readStoredPaneWidth()));
const [dragging, setDragging] = useState(false);
const [maximized, setMaximized] = useState(false);
const [fixedPane, setFixedPane] = useState<FixedPane | null>(null);
const asideRef = useRef<HTMLElement | null>(null);
const widthRef = useRef(width);
widthRef.current = width;
const dragStateRef = useRef<{ pointerId: number; startX: number; startWidth: number } | null>(
null,
);
const previousBodyUserSelectRef = useRef("");
const restoreTimerRef = useRef<number | null>(null);
const clearRestoreTimer = useCallback(() => {
if (restoreTimerRef.current !== null) {
window.clearTimeout(restoreTimerRef.current);
restoreTimerRef.current = null;
}
}, []);
const finishRestore = useCallback(() => {
clearRestoreTimer();
setFixedPane(null);
}, [clearRestoreTimer]);
// Hiding the panel keeps today's collapse-to-0 behavior; if it was
// maximized (or mid-glide), just unmaximize instantly first.
useEffect(() => {
if (!panelVisible) {
setMaximized(false);
finishRestore();
}
}, [panelVisible, finishRestore]);
useEffect(
() => () => {
if (restoreTimerRef.current !== null) window.clearTimeout(restoreTimerRef.current);
if (dragStateRef.current !== null) {
document.body.style.userSelect = previousBodyUserSelectRef.current;
}
},
[],
);
const endDrag = useCallback((persist: boolean) => {
if (dragStateRef.current === null) return;
dragStateRef.current = null;
setDragging(false);
document.body.style.userSelect = previousBodyUserSelectRef.current;
if (persist) persistPaneWidth(widthRef.current);
}, []);
const handleGripPointerDown = useCallback((event: React.PointerEvent<HTMLDivElement>) => {
// Primary button only (touch/pen report button 0 or -1 for down events).
if (event.pointerType === "mouse" && event.button !== 0) return;
event.preventDefault();
event.currentTarget.setPointerCapture(event.pointerId);
dragStateRef.current = {
pointerId: event.pointerId,
startX: event.clientX,
startWidth: widthRef.current,
};
previousBodyUserSelectRef.current = document.body.style.userSelect;
document.body.style.userSelect = "none";
setDragging(true);
}, []);
const handleGripPointerMove = useCallback((event: React.PointerEvent<HTMLDivElement>) => {
const drag = dragStateRef.current;
if (drag === null || drag.pointerId !== event.pointerId) return;
// The grip sits on the panel's LEFT border: moving left widens the panel.
setWidth(clampPaneWidth(drag.startWidth + (drag.startX - event.clientX)));
}, []);
const handleGripPointerUp = useCallback(
(event: React.PointerEvent<HTMLDivElement>) => {
const drag = dragStateRef.current;
if (drag === null || drag.pointerId !== event.pointerId) return;
endDrag(true);
},
[endDrag],
);
const handleGripLostPointerCapture = useCallback(() => {
endDrag(true);
}, [endDrag]);
const handleGripDoubleClick = useCallback(() => {
setWidth(DEFAULT_PANE_WIDTH);
clearStoredPaneWidth();
}, []);
const handleMaximize = useCallback(() => {
const aside = asideRef.current;
const row = aside?.parentElement;
if (!aside || !row) return;
clearRestoreTimer();
setMaximized(true);
const rowRect = row.getBoundingClientRect();
setFixedPane((pane) => {
// Re-maximizing mid-restore: keep the current geometry, glide back left.
if (pane) return { ...pane, left: pane.parentLeft };
const rect = aside.getBoundingClientRect();
const seeded: FixedPane = {
top: rect.top,
left: rect.left,
rightInset: Math.max(0, window.innerWidth - rect.right),
parentLeft: rowRect.left,
};
if (prefersReducedMotion()) return { ...seeded, left: seeded.parentLeft };
// Seed at the current left, then glide to the row's left edge once the
// fixed position has been committed (double rAF).
window.requestAnimationFrame(() => {
window.requestAnimationFrame(() => {
setFixedPane((current) => (current ? { ...current, left: current.parentLeft } : current));
});
});
return seeded;
});
}, [clearRestoreTimer]);
const handleRestore = useCallback(() => {
const row = asideRef.current?.parentElement;
setMaximized(false);
if (prefersReducedMotion()) {
finishRestore();
return;
}
setFixedPane((pane) => {
if (!pane) return pane;
const rowRight = row
? row.getBoundingClientRect().right
: window.innerWidth - pane.rightInset;
return { ...pane, left: rowRight - widthRef.current };
});
clearRestoreTimer();
restoreTimerRef.current = window.setTimeout(finishRestore, RESTORE_FALLBACK_DELAY);
}, [clearRestoreTimer, finishRestore]);
const handleTransitionEnd = useCallback(
(event: React.TransitionEvent<HTMLElement>) => {
if (event.target !== asideRef.current || event.propertyName !== "left") return;
// Only the restore glide needs to unfix on arrival.
if (!maximized) finishRestore();
},
[maximized, finishRestore],
);
const isFixed = fixedPane !== null;
return (
<>
{isFixed ? (
// Holds the panel's slot in the layout flex row while the panel is
// position:fixed, so the main column never reflows.
<div
aria-hidden
className="hidden md:block shrink-0"
style={{ width: panelVisible ? width : 0 }}
/>
) : null}
<aside
ref={asideRef}
className={cn(
"hidden md:flex border-l border-border bg-card flex-col",
isFixed
? "tc-pane-glide fixed z-40 overflow-hidden"
: cn(
"relative h-full shrink-0",
panelVisible ? "overflow-visible" : "overflow-hidden",
// The width/opacity transition would fight pointer-driven
// resizing, so it is suspended while dragging.
!dragging && "transition-(--tp-width-opacity) duration-200 ease-in-out",
),
)}
style={
isFixed
? {
top: fixedPane.top,
bottom: 0,
left: fixedPane.left,
right: fixedPane.rightInset,
}
: { width: panelVisible ? width : 0, opacity: panelVisible ? 1 : 0 }
}
onTransitionEnd={handleTransitionEnd}
>
{!isFixed && panelVisible ? (
<div
role="separator"
aria-orientation="vertical"
aria-label="Resize panel"
data-dragging={dragging ? "" : undefined}
className="group absolute inset-y-0 z-10 cursor-col-resize touch-none"
style={{ left: -4, width: 8 }}
onPointerDown={handleGripPointerDown}
onPointerMove={handleGripPointerMove}
onPointerUp={handleGripPointerUp}
onPointerCancel={handleGripPointerUp}
onLostPointerCapture={handleGripLostPointerCapture}
onDoubleClick={handleGripDoubleClick}
>
<div
className={cn(
"mx-auto h-full w-0.5 transition-colors",
dragging ? "bg-ring" : "bg-transparent group-hover:bg-ring",
)}
/>
</div>
) : null}
<div
className={cn("flex-1 flex flex-col min-h-0", isFixed && "w-full")}
style={isFixed ? undefined : { width, minWidth: width }}
>
{/* The slot hosts whatever IssueProperties portals in — the tab strip
when Plan/Artifacts have content, else a plain "Properties" title;
window controls sit right. Vertical padding lives on the controls
cluster, not the bar, so the tab strip can stretch to the border
and its active underline hugs the header's bottom line. */}
<div className="flex items-center justify-between gap-2 px-4 border-b border-border">
<div
id={PROPERTIES_PANE_HEADER_SLOT_ID}
className="flex min-w-0 flex-1 items-center self-stretch"
/>
<div className="flex items-center gap-1 py-2">
<Button
variant="ghost"
size="icon-xs"
className="size-7"
title={maximized ? "Restore panel" : "Maximize panel"}
aria-label={maximized ? "Restore panel" : "Maximize panel"}
onClick={maximized ? handleRestore : handleMaximize}
>
{maximized ? (
<Minimize2 className="h-3.5 w-3.5" />
) : (
<Maximize2 className="h-3.5 w-3.5" />
)}
</Button>
<Button variant="ghost" size="icon-xs" onClick={() => setPanelVisible(false)}>
<X className="h-4 w-4" />
</Button>
</div>
</div>
<ScrollArea className="flex-1">
<div
className={cn("p-4", maximized && "mx-auto w-full px-9")}
style={maximized ? { maxWidth: MAXIMIZED_CONTENT_MAX_WIDTH } : undefined}
>
{panelContent}
</div>
</ScrollArea>
<div id={PROPERTIES_PANE_FOOTER_SLOT_ID} className="shrink-0" />
</div>
</aside>
</>
);
}