Files
PaperClipAI/ui/src/lib/pipeline-liveness.ts
T
ad961227f5 feat(secrets): add user-specific runtime secrets (#8825)
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work.
> - Agent runs often need provider credentials, API tokens, and other
environment-bound secrets.
> - Company-level secrets work for shared credentials, but they do not
model values that should differ by human operator.
> - Without a user-scoped model, a run can dispatch without knowing
whether the responsible human has supplied the needed value.
> - Paperclip also needs run attribution to make those user-scoped
runtime checks deterministic and auditable.
> - This pull request adds user-specific secret definitions, per-user
values, environment bindings, responsible-user attribution, and runtime
resolution gates.
> - The benefit is that teams can define the secret once, let each user
provide their own value, and block runs before dispatch when required
user secrets or active definitions are unavailable.

## Linked Issues or Issue Description

Refs #224
Refs #6057

This PR implements user-specific secret support as a core
secret-management capability rather than a one-off adapter setting. It
is related to existing public work on company secrets UI and runtime
secret refs, but is distinct because the value is owned by the
responsible user and resolved at run dispatch time.

Related PR search before opening found existing secrets work such as
#1550, #8256, #8614, #8634, and #8647; none of those add the full
user-secret definition/value/runtime gate covered here.

## What Changed

- Added user-secret definitions and per-user "My secrets" values,
keeping stored values out of access metadata.
- Added `user_secret_ref` environment bindings and UI affordances to
pick them alongside existing secret refs.
- Added responsible-user runtime resolution so user-secret refs resolve
against the human responsible for the run.
- Added pre-dispatch missing-secret gates so runs fail before adapter
dispatch when required user values are absent or definitions are
inactive.
- Added low-trust allowlist hardening for user-secret runtime access.
- Added issue, routine, run, and agent API key responsible-user
attribution and fail-closed dispatch behavior when attribution cannot be
resolved.
- Added denial-copy mapping so responsible-user authorization failures
surface as actionable run outcomes instead of opaque setup failures.
- Added OpenAPI documentation for the user-secret routes.
- Rebases cleanly on current `master`; migrations were renumbered
incrementally as `0128_user_specific_secrets`,
`0129_agent_api_key_responsible_user`, and
`0130_run_responsible_user_invariant` after upstream `0126`/`0127`
migrations.
- Removed previously committed local design screenshots so the PR
contains code/docs/tests only.

## Verification

- PASS: PR head `2527febd106bcf3ca264ca0da7fca491084192d6` is based on
`paperclipai/paperclip:master`.
- PASS: `git diff --check`
- PASS: `git diff --name-only public/master...HEAD | rg
'^(pnpm-lock\\.yaml|\\.github/workflows/|screenshots/)' || true`
produced no files.
- PASS: migration journal audit confirmed unique indexes through `130`
with tail entries `0126_issue_comment_derived_attribution`,
`0127_environment_custom_images_instance_scoped`,
`0128_user_specific_secrets`, `0129_agent_api_key_responsible_user`, and
`0130_run_responsible_user_invariant`.
- PASS: `pnpm --filter @paperclipai/ui typecheck`
- PASS: `pnpm --filter @paperclipai/server typecheck`
- PASS: `pnpm --filter @paperclipai/server exec vitest run
src/__tests__/heartbeat-responsible-user-invariant.test.ts`
- PASS: `pnpm --filter @paperclipai/server exec vitest run
src/__tests__/heartbeat-active-run-output-watchdog.test.ts
src/__tests__/heartbeat-stale-queue-invalidation.test.ts
src/__tests__/heartbeat-workspace-finalize-branch.test.ts
src/__tests__/issue-monitor-scheduler.test.ts`
- PASS: `pnpm --filter @paperclipai/server exec vitest run
src/__tests__/heartbeat-comment-wake-batching.test.ts
src/__tests__/heartbeat-retry-scheduling.test.ts
src/__tests__/heartbeat-accepted-plan-workspace-refresh.test.ts
src/__tests__/heartbeat-plugin-environment.test.ts`
- PASS: `pnpm --filter @paperclipai/server exec vitest run
src/__tests__/low-trust-red-team-routes.test.ts`
- PASS: `pnpm --filter @paperclipai/server exec vitest run
src/__tests__/secrets-service.test.ts` (55 tests)
- PASS: `pnpm vitest run server/src/__tests__/secrets-routes.test.ts
server/src/__tests__/secrets-service.test.ts` (89 tests after final
Greptile cleanup fixes)
- PASS: `pnpm --filter @paperclipai/server exec vitest run
src/__tests__/heartbeat-issue-liveness-escalation.test.ts` (17 tests
after the final rebase CI fix)
- PASS: focused server Vitest batches covering heartbeat recovery,
project env, plugin env, routines, low-trust, pipelines, monitors,
watchdog, and stale queue paths.
- PASS: GitHub checks are green on
`2527febd106bcf3ca264ca0da7fca491084192d6`, including Typecheck +
Release Registry, Build, General tests, serialized server suites, e2e,
Canary Dry Run, verify, security checks, and Greptile Review.
- PASS: Greptile Review completed successfully on
`2527febd106bcf3ca264ca0da7fca491084192d6` with Confidence Score 5/5,
and GraphQL review-thread audit returned zero unresolved non-outdated
threads.

## Risks

- Runtime behavior now depends on a run having a correct responsible
user; missing or incorrect responsibility assignment can block runs
before adapter dispatch.
- `user_secret_ref` bindings intentionally expose metadata without
values, but UI/API callers may need to handle the new binding kind
explicitly.
- External secret providers and IAM policies are not automatically
provisioned by this PR; operators still need to configure provider-side
access for non-local vaults.
- The PR is broad across db/shared/server/UI/runtime paths, so release
validation should include both API and UI secret workflows before merge.
- The migration renumbering is intentionally incremental after upstream
migrations; the branch migrations use guarded
column/table/index/constraint creation so users who tested the older
draft numbering should not hit duplicate DDL for the existing objects.

> 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 (`gpt-5`), Codex local adapter
with shell/tool use and code execution. Context window and internal
reasoning mode are 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 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
- [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

---------

Co-authored-by: Paperclip <noreply@paperclip.ing>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-05 05:58:20 -05:00

236 lines
8.2 KiB
TypeScript

import type { PipelineCaseLiveness } from "@paperclipai/shared";
/**
* Visual tone for a pipeline item liveness banner. Each tone maps to a palette
* in {@link ../components/PipelineLivenessBanner}:
* - `blocked` → amber, "automation paused, waiting on a named blocker"
* - `permission` → purple, "a permission grant is missing before this can run"
* - `retry` → indigo, "blocker resolved, ready to retry"
* - `attention` → orange, "automation failed / no action path, needs a nudge"
*/
export type LivenessBannerTone = "blocked" | "permission" | "retry" | "attention";
export type LivenessRetryKind = "automation" | "stage" | null;
export interface LivenessBannerLink {
/** Task link target. We only link tasks; cases lack a routable id here. */
issueId: string;
identifier?: string | null;
title?: string | null;
}
export interface LivenessBannerView {
reason: PipelineCaseLiveness["reason"];
tone: LivenessBannerTone;
title: string;
body: string;
/** Primary link to the underlying blocker task, when one is known. */
blockerLink: LivenessBannerLink | null;
/** Secondary link to the linked automation/work task, when one is known. */
automationLink: LivenessBannerLink | null;
/** Permission key the configured responsible is missing (e.g. `pipelines:write`). */
permissionKey: string | null;
/** Whether a retry call-to-action should render. */
showRetry: boolean;
/** Which mutation the retry CTA should invoke. */
retryKind: LivenessRetryKind;
retryLabel: string;
/** Reassurance line that steers operators away from forcing a manual move. */
helperNote: string | null;
}
const AUTO_RETRY_NOTE =
"Paperclip retries automatically once the blocker clears — you don't need to move the item by hand.";
/**
* Prosumer-voice body for the `no_action_path` "stuck" banner. The server's
* raw `liveness.message` ("No lease, linked work, blocker, automation retry,
* review, or breakdown action path is visible.") leaks implementation vocabulary
* the PAP-11245 voice rule forbids, so we translate it here. See PAP-11259.
*/
const NO_ACTION_PATH_BODY =
"Paperclip can't see anything to work on next here — no automation, retry, blocker, or review. " +
"Re-run the stage to nudge it, or use the ⋯ menu to move it by hand.";
/**
* The `pipelines:write` permission key is the only permission the Phase 2
* preflight blocks on today. The fingerprint encodes it as the final two
* colon-separated segments (`...:pipelines:write`).
*/
function permissionKeyFromFingerprint(fingerprint: string | null | undefined): string | null {
if (!fingerprint) return null;
const parts = fingerprint.split(":");
if (parts.length < 2) return null;
const key = parts.slice(parts.length - 2).join(":");
return key.includes(":") ? key : null;
}
function blockerLinkFromLiveness(liveness: PipelineCaseLiveness): LivenessBannerLink | null {
const blocker = liveness.blocker;
if (blocker?.issueId) {
return { issueId: blocker.issueId, title: blocker.title ?? null };
}
return null;
}
function automationLinkFromLiveness(liveness: PipelineCaseLiveness): LivenessBannerLink | null {
const issue = liveness.issue;
if (issue?.id) {
return { issueId: issue.id, identifier: issue.identifier, title: issue.title };
}
return null;
}
/**
* Derive the banner view-model from the server's liveness payload. Returns
* `null` for states that should not raise a banner (terminal, actively running,
* or states already represented by another section such as review/children
* waiting). This keeps the item detail header from over-crowding.
*/
export function derivePipelineLivenessBanner(
liveness: PipelineCaseLiveness | null | undefined,
): LivenessBannerView | null {
if (!liveness) return null;
switch (liveness.reason) {
// Handled elsewhere or not "stuck" — no banner.
case "terminal":
case "lease_active":
case "linked_issue_active":
case "linked_issue_waiting":
case "children_waiting":
case "review_waiting":
return null;
case "case_blocked":
return {
reason: liveness.reason,
tone: "blocked",
title: "Automation paused — waiting on a blocker",
body: liveness.message,
blockerLink: blockerLinkFromLiveness(liveness),
automationLink: automationLinkFromLiveness(liveness),
permissionKey: null,
showRetry: false,
retryKind: null,
retryLabel: "",
helperNote: AUTO_RETRY_NOTE,
};
case "linked_issue_blocked":
return {
reason: liveness.reason,
tone: "blocked",
title: "Automation paused — waiting on a blocker",
body: liveness.message,
blockerLink: blockerLinkFromLiveness(liveness),
automationLink: automationLinkFromLiveness(liveness),
permissionKey: null,
showRetry: false,
retryKind: null,
retryLabel: "",
helperNote: AUTO_RETRY_NOTE,
};
case "permission_preflight_failed":
return {
reason: liveness.reason,
tone: "permission",
title: "Permission needed before this can run",
body: liveness.message,
blockerLink: null,
automationLink: automationLinkFromLiveness(liveness),
permissionKey: permissionKeyFromFingerprint(liveness.automation?.fingerprint) ?? "pipelines:write",
showRetry: false,
retryKind: null,
retryLabel: "",
helperNote:
"Grant the access above to the configured responsible, then Paperclip retries automatically.",
};
case "automation_failed": {
// Phase 2 reuses `automation_failed` both for a generic failure and for
// the recovered "permission restored" case. The recovery path is the only
// one whose message announces the restore, so key off that.
const recovered = /permission has been restored/i.test(liveness.message);
const automationId = liveness.automation?.automationId ?? null;
return {
reason: liveness.reason,
tone: recovered ? "retry" : "attention",
title: recovered ? "Blocker resolved — ready to retry" : "Automation failed",
body: liveness.message,
blockerLink: null,
automationLink: automationLinkFromLiveness(liveness),
permissionKey: null,
showRetry: true,
retryKind: automationId ? "automation" : "stage",
retryLabel: "Retry now",
helperNote: recovered ? AUTO_RETRY_NOTE : null,
};
}
case "breakdown_pending":
return {
reason: liveness.reason,
tone: "attention",
title: "Waiting on breakdown evidence",
body: liveness.message,
blockerLink: null,
automationLink: null,
permissionKey: null,
showRetry: true,
retryKind: "stage",
retryLabel: "Re-run stage automation",
helperNote: null,
};
case "breakdown_incomplete":
return {
reason: liveness.reason,
tone: "blocked",
title: "Breakdown is incomplete",
body: missingPiecesBody(liveness),
blockerLink: null,
automationLink: null,
permissionKey: null,
showRetry: true,
retryKind: "stage",
retryLabel: "Re-run stage automation",
helperNote: null,
};
case "no_action_path":
return {
reason: liveness.reason,
tone: "attention",
title: "This item is stuck",
body: NO_ACTION_PATH_BODY,
blockerLink: null,
automationLink: null,
permissionKey: null,
showRetry: true,
retryKind: "stage",
retryLabel: "Re-run stage automation",
helperNote: null,
};
default:
return null;
}
}
function missingPiecesBody(liveness: PipelineCaseLiveness): string {
const missing = liveness.breakdown?.missingRequestKeys?.length ?? 0;
if (missing > 0) {
return `${liveness.message} ${missing} expected ${missing === 1 ? "piece is" : "pieces are"} still missing.`;
}
return liveness.message;
}
/** True when the PAP-11238 "Re-run stage automation" menu item must be disabled. */
export function shouldDisableRerunForPermission(
liveness: PipelineCaseLiveness | null | undefined,
): boolean {
return liveness?.reason === "permission_preflight_failed";
}