0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-30 13:20:54 +01:00

Files

T

Priya RamanandPaperclip 81951535e9 feat(server): reopen an archived isolated execution workspace in place

Make an archived isolated execution workspace usable again, so a terminal
issue can resume without a dead end. Reopen the same workspace row: flip it
back to active and rebuild the worktree. Do not create a new row and do not
change any issue-to-workspace link, so every issue that shares the row keeps
access.

Add reopenClosedIsolatedExecutionWorkspaceForIssue in the execution workspace
service. It binds the workspace to the issue company and project, accepts only
an isolated workspace in a closed state, and fails closed with no workspace
detail on a mismatch. It rebuilds the worktree first and publishes active only
on success. A rebuild failure keeps the row closed and returns an error, so the
caller never dispatches a run against a broken workspace.

Fence a cleanup against a concurrent reopen. Every archive and every reopen
raises a lifecycle generation stored in the workspace metadata. Reopen and the
destructive cleanup paths take the same transaction-scoped Postgres advisory
lock. A cleanup captures the generation it archived at and re-checks it under
the lock before it deletes the worktree. A reopen that ran in between raises the
generation, so the stale cleanup does nothing. The terminal-workspace reaper and
the archive route both use this fence.

Wire the reopen at the resume, checkout, and comment guards. Each guard runs
after the route authorizes the request on the issue. A closed isolated workspace
now reopens and the request continues, instead of a 409 dead end. A
non-reopenable workspace returns 409 and a rebuild failure returns 503.

Enable the comment composer for a reopened issue and show a hint that the next
comment or resume rebuilds the worktree.

Co-authored-by: Paperclip <noreply@paperclip.ing>

2026-08-13 01:18:02 +00:00

public

fix(ui): always give respondWith a real Response in the sw fetch fallback (#11292 )

2026-08-12 11:23:18 -07:00

src

feat(server): reopen an archived isolated execution workspace in place

2026-08-13 01:18:02 +00:00

storybook

fix(ui): add mobile blocker actions (#11282 )

2026-08-12 12:12:55 -04:00

components.json

Overhaul UI with shadcn components and new pages

2026-02-17 09:07:32 -06:00

index.html

fix(ui): fetch the web app manifest with credentials (#11245 )

2026-08-11 19:11:56 -07:00

package.json

revert(ui): back out onboarding port (#10786 ) (#11067 )

2026-08-07 14:55:34 -07:00

README.md

[codex] add comprehensive UI Storybook coverage (#4132 )

2026-04-20 12:13:23 -05:00

tsconfig.json

chore(ui): remove deprecated baseUrl from ui/tsconfig.json (#4067 )

2026-08-04 18:39:13 -05:00

vite.config.ts

revert(ui): back out onboarding port (#10786 ) (#11067 )

2026-08-07 14:55:34 -07:00

vite.qa.config.mjs

feat(mcp) [split 7/8]: activate Apps and gateway UI (#9562 )

2026-07-14 15:40:08 -05:00

vitest.config.ts

build(deps): upgrade lexical family to 0.46.0 and pin via overrides (fixes dual-version getType crash) (#9180 )

2026-07-07 13:00:26 -07:00

vitest.setup.ts

feat(ui): NUX rework behind enableConferenceRoomChat experimental flag — capsule onboarding, conference-room chat, unified composer (#8000 )

2026-06-11 16:32:55 -05:00

README.md

@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.