Files
PaperClipAI/ui
Jannes StubbemannandClaude Fable 5 cdacb6b5bd feat(ui): render OpenCode process-adapter runs with the rich transcript
Runs executed through the generic process adapter (adapterType "process")
whose command ultimately execs an OpenCode harness emit OpenCode JSONL on
stdout. The process transcript parser was a pass-through that wrapped every
line as raw stdout, so the Run page nice view rendered identically to the raw
view: both dumped raw JSONL.

The process parser now content-detects OpenCode-shaped JSONL (a JSON object
whose type is one of text|reasoning|tool_use|step_start|step_finish|error,
carrying a sessionID string or a part payload) and, once detected, locks on
and delegates every subsequent line to the existing OpenCode parser. This
gives such runs the rich transcript (messages, tool cards, thinking lane)
that already exists, while leading plain wrapper lines and genuinely
non-JSONL process output stay raw stdout.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-04 17:57:02 +02:00
..

@paperclipai/ui

Published static assets for the Paperclip board UI.

What gets published

The npm package contains the production build under dist/. It does not ship the UI source tree or workspace-only dependencies.

Storybook

Storybook config, stories, and fixtures live under ui/storybook/.

pnpm --filter @paperclipai/ui storybook
pnpm --filter @paperclipai/ui build-storybook

Typical use

Install the package, then serve or copy the built files from node_modules/@paperclipai/ui/dist.