Files
PaperClipAI/ui/src/api/builtInAgents.ts
T
1f1f545238 feat: add built-in summarizer and summary slots (#9713)
## Thinking Path

> - Paperclip is the open source control plane people use to organize,
govern, and understand AI-agent work
> - Operators need concise, current status views across projects and
execution workspaces without manually reading every issue and run
> - Paperclip already has auditable issues, documents, built-in agents,
routines, and live run events, but no first-class summary-slot workflow
connecting those systems
> - A built-in Summarizer can generate status prose through ordinary
governed tasks while summary slots provide stable, revisioned
destinations for that output
> - The UI needs to show current summaries, generation progress,
failures, revisions, and streaming draft status in the places operators
already work
> - This pull request adds the end-to-end summary-slot data, API, agent,
orchestration, and UI surfaces behind an experimental setting
> - The benefit is decision-oriented status context that remains
company-scoped, auditable, retryable, and inexpensive by default

## Linked Issues or Issue Description

No public GitHub issue exists for this feature.

**Problem**

Operators currently have to reconstruct project and workspace status by
reading many issues, runs, and comments. This makes it hard to identify
decisions, review queues, recent work, and the next event worth
watching.

**Proposed capability**

Add an experimental summary system with revisioned summary slots for
projects and workspaces, a paused-by-default built-in Summarizer agent,
governed generation tasks, live draft status, and reusable UI cards.

**Expected behavior**

- Summary data remains company-scoped and revisions remain auditable.
- Generation runs through normal issue/agent orchestration and
deduplicates active requests.
- Only the linked built-in Summarizer generation task can author a slot
revision.
- Operators can generate, retry, inspect revisions, and follow draft
progress from project and workspace views.
- The feature remains opt-in and background generation remains paused by
default.

## What Changed

- Added summary-slot schema, idempotent migrations, shared contracts,
validators, API paths, and service tests.
- Added company-scoped summary-slot routes for reading revisions,
requesting generation, and guarded Summarizer writes with activity
logging.
- Added terminal generation finalization, failure reasons, assignment
wakeups, and orchestration integration.
- Added the paused-by-default built-in Summarizer bundle, low-cost
runtime defaults, status-summarization skill, and stale-summary routine.
- Added summary cards, revision selection, retry/configuration states,
live draft streaming, transcript chunk handling, and project/workspace
integrations.
- Updated Claude local parsing for streamed status output and expanded
server, adapter, shared, database, catalog, and UI coverage.

## Verification

- `pnpm -r typecheck`
- `pnpm exec vitest run packages/db/src/summary-slots-schema.test.ts
packages/shared/src/summary-slot.test.ts
server/src/__tests__/summary-slot-routes.test.ts
server/src/__tests__/summary-slots.test.ts
server/src/__tests__/built-in-agents.test.ts
ui/src/components/SummarySlotCard.test.tsx
ui/src/components/SummarySlotCard.status.test.tsx
ui/src/components/useSummaryDraftStream.test.tsx
ui/src/lib/summary-draft-stream.test.ts
ui/src/lib/run-log-chunks.test.ts
ui/src/context/LiveUpdatesProvider.hook.test.tsx` — 113 tests passed
- `pnpm test:run` — server and UI suites passed; one CLI AWS doctor test
was affected by inherited `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY`,
and passed when those host credentials were removed
- `pnpm exec vitest run cli/src/__tests__/secrets.test.ts` with
inherited AWS credential variables removed — 8 tests passed
- `pnpm build`
- `pnpm check:token-gates` currently reports nine `#9627` comment
references introduced by current `master`; none are in this PR diff

## Risks

- Database risk is limited by incrementally ordered, idempotent
migrations and migration safety checks.
- Summary generation creates normal issues/runs, so misconfiguration can
produce failed slots; the UI exposes retryable failure reasons and agent
configuration entry points.
- Streaming draft parsing depends on the documented `STATUS:` protocol;
final persisted revisions remain the source of truth.
- The feature is experimental, opt-in, and its built-in routine is
paused with no background token spend by default.

> 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 GPT-5.3 Codex with reasoning, repository tool use, code
execution, GitHub CLI, and Paperclip control-plane integration. Earlier
branch commits also record Claude model co-authorship where applicable.

## 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-17 11:03:07 -05:00

168 lines
6.6 KiB
TypeScript

import type { Agent, Approval } from "@paperclipai/shared";
import { api } from "./client";
/**
* Lifecycle of a built-in agent, derived server-side from row existence,
* adapter-config completeness, board-approval state, and `pausedAt`.
*
* `not_provisioned → pending_approval → needs_setup → ready ⇄ paused`
*
* `pending_approval` only occurs when the company requires board approval for
* new agents; otherwise provisioning goes straight to `needs_setup`/`ready`.
*/
export type BuiltInAgentStatus =
| "not_provisioned"
| "pending_approval"
| "needs_setup"
| "ready"
| "paused";
/**
* Redacted bundle metadata returned alongside a built-in agent that ships a
* managed resource bundle (instructions + skill + routine). The server strips
* file bodies to key lists; the UI only needs the identity/labels to render the
* bundle status panel. Present only on bundle-backed built-ins (Reflection
* Coach); flat built-ins (briefs/learning) omit it.
*/
export interface BuiltInAgentBundleMeta {
stockVersion: string;
instructions: { entryFile: string; files: string[] };
skill: {
skillKey: string;
displayName: string;
slug: string;
canonicalKey: string;
files: string[];
};
routine: {
routineKey: string;
title: string;
status: "active" | "paused";
triggerCount: number;
scheduleLabel?: string;
};
}
export interface BuiltInAgentDefinition {
key: string;
displayName: string;
featureKeys: string[];
shortPurpose: string;
defaultInstructions: string;
defaultRole: string;
allowedAdapterTypes?: string[];
defaultAdapterType?: string;
defaultAdapterConfig?: Record<string, unknown>;
defaultBudgetMonthlyCents?: number;
bundle?: BuiltInAgentBundleMeta;
}
/** Managed resources a bundle materializes; drift is tracked per kind. */
export type BuiltInManagedResourceKind = "instructions" | "skill" | "routine";
/**
* Drift status of one managed resource versus the shipped stock default:
* - `missing` — expected resource absent; a reconcile will recreate it.
* - `stock_current` — present and byte-identical to the shipped default.
* - `stock_update_available` — unedited, but Paperclip shipped a newer default.
* - `operator_modified` — operator-edited; reconcile preserves these edits.
*/
export type BuiltInManagedResourceStockStatus =
| "missing"
| "stock_current"
| "stock_update_available"
| "operator_modified";
export interface BuiltInManagedResourceState {
resourceKind: BuiltInManagedResourceKind;
resourceKey: string;
resourceId: string | null;
stockVersion: string;
stockHash: string;
currentHash: string | null;
stockStatus: BuiltInManagedResourceStockStatus;
/** True when an unedited resource has a newer shipped default to apply. */
updateAvailable: boolean;
/** True when the resource has drifted and can be reset to the default. */
resetAvailable: boolean;
changedFiles?: string[];
/** True when the managed weekly schedule is active and can create background work. */
scheduleEnabled?: boolean;
/** Pending request_confirmation for a Reflection Coach update proposal, when one exists. */
pendingUpdateInteractionId?: string | null;
/** Issue containing the pending proposal interaction. */
pendingUpdateIssueId?: string | null;
pendingUpdateIssueIdentifier?: string | null;
}
export interface BuiltInAgentState {
definition: BuiltInAgentDefinition;
status: BuiltInAgentStatus;
agentId: string | null;
agent: Agent | null;
pauseReason: string | null;
/** Per-resource drift/readiness for bundle-backed built-ins (may be empty). */
resources?: BuiltInManagedResourceState[];
/** Present when provisioning queued a board hire approval (HTTP 202). */
approval?: Approval | null;
}
export interface BuiltInAgentProvisionInput {
adapterType?: string;
adapterConfig?: Record<string, unknown>;
budgetMonthlyCents?: number;
}
/**
* Selectors accepted by the reset endpoint. `agent` resets the agent config
* (adapter/model/budget defaults) only; the resource kinds each reset a single
* managed resource back to its shipped default. Omitting the array resets
* everything (the agent-level "Reset to defaults" button).
*/
export type BuiltInResetResource = "agent" | BuiltInManagedResourceKind;
/**
* Error `code` thrown as HTTP 412 by `requireBuiltInAgent` on the server when a
* feature needs a built-in agent that is missing or not fully configured. The
* configure-on-first-use modal is triggered from this signal.
*/
export const BUILT_IN_AGENT_NOT_CONFIGURED_CODE = "built_in_agent_not_configured";
/**
* Warning `code` returned alongside a paused built-in agent so callers can
* surface the use-while-paused toast without treating the agent as ready.
*/
export const BUILT_IN_AGENT_PAUSED_CODE = "built_in_agent_paused";
export const builtInAgentsApi = {
list: (companyId: string) =>
api.get<BuiltInAgentState[]>(`/companies/${companyId}/built-in-agents`),
provision: (companyId: string, key: string, input: BuiltInAgentProvisionInput = {}) =>
api.post<BuiltInAgentState>(`/companies/${companyId}/built-in-agents/${key}/provision`, input),
/**
* Reset built-in defaults. Pass `resources` to scope the reset to specific
* managed resources (e.g. `["skill"]`); omit it to reset the whole agent +
* bundle. A single-resource reset re-applies that resource's newest shipped
* default — the same path used for both "reset drifted edits" and "apply an
* available stock update".
*/
reset: (companyId: string, key: string, resources?: BuiltInResetResource[]) =>
api.post<BuiltInAgentState>(
`/companies/${companyId}/built-in-agents/${key}/reset`,
resources ? { resources } : {},
),
/**
* Re-materialize the bundle. Applies the newest shipped defaults to unedited
* (`stock_update_available`) and `missing` resources while preserving
* `operator_modified` edits — it is the safe "apply available updates" path.
*/
reconcile: (companyId: string, key: string) =>
api.post<BuiltInAgentState>(`/companies/${companyId}/built-in-agents/${key}/reconcile`, {}),
runRoutine: (companyId: string, key: string, routineKey: string) =>
api.post<unknown>(`/companies/${companyId}/built-in-agents/${key}/routines/${routineKey}/run`, {}),
enableRoutineSchedule: (companyId: string, key: string, routineKey: string) =>
api.post<BuiltInAgentState>(`/companies/${companyId}/built-in-agents/${key}/routines/${routineKey}/enable`, {}),
disableRoutineSchedule: (companyId: string, key: string, routineKey: string) =>
api.post<BuiltInAgentState>(`/companies/${companyId}/built-in-agents/${key}/routines/${routineKey}/disable`, {}),
};