mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-29 21:07:40 +01:00
## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work. > - Tasks can use isolated repository workspaces. > - Core currently prepares those repositories on its own filesystem. > - A storage provider may only expose repositories inside remote agent computers. > - Project storage and task workspace preparation must have one provider owner. > - This pull request adds that contract and keeps execution as a separate plugin interface. > - Core keeps authorization, durable task bindings, and lifecycle fences. ## Linked Issues or Issue Description **Subsystem affected** Plugin SDK, project workspace policy, heartbeat preparation, execution leases, and workspace lifecycle. **Problem or motivation** Core cannot prepare a task workspace when its repository storage is unavailable on the Core host. An execution lease must not be required just to prepare persistent storage. **Proposed solution** Let one plugin provide project resource lifecycle and workspace prepare, inspect, restore, and remove behavior. Core reserves a task workspace before it calls the plugin. The plugin returns an opaque durable reference. The matching execution plugin receives that reference on its task RPC. **Alternatives considered** Preparing repositories on Core would require a provider mount on Core. Preparing them only during task launch would tie persistent workspace lifecycle to execution leases and agent availability. **Roadmap alignment** This extends the remote provider model in ROADMAP.md. Related execution work is in #16978. This PR does not replace that task bridge. Native execution of managed storage requires the bridge; this change fails closed when it is absent. ## What Changed - Add one storage provider declaration with supported modes/strategies, a capability, a validated RPC contract, and a test harness. - Persist provider ownership, repository revision, and execution-workspace identity before external effects. Reconcile retries with a stable operation ID. - Prepare provider storage before environment acquisition. Keep Core filesystem preparation out of this path. - Pin the durable reference to the matching execution plugin and validate the lease binding before task dispatch. - Route inspection, reopen, and removal through the existing lifecycle process. Keep local data when remote recovery is uncertain. - Keep the application database pool free during lifecycle locks. Preserve pending workspace selections, validate source edits before retirement, and retry unfinished closed storage cleanup. - Protect provider metadata and live repository sources from caller edits. Storage edits retire only closed records with confirmed removal; retired records cannot reopen. ## Verification - Current head `8214b3ca5`: all 25 provider lifecycle tests pass with `maxConnections=1`. They cover preparation, inspection, reopening, removal, a paused provider with responsive ordinary SQL and a competing source edit, pending selection preservation, rejected source edits, cleanup retry scheduling, and providers that cache operation results, and committed cleanup notifications for storage intent and recovered state. - Final frozen-tree lifecycle run on `8214b3ca5`: all 318 tests passed in 10 files, covering workspace services, reopen, compaction, task binding, project sources, heartbeat preparation, display caching, and source locks. - Direct server `tsc --noEmit` passes. The SDK build and all 128 SDK tests passed during initial verification; later SDK changes are documentation only. - Full CI on the previous head `ec5c7209a` passed all 55 applicable checks; 2 conditional checks skipped. Standard Greptile reviewed current head `342e6d9c3` at 5/5 with no unresolved threads. All 55 applicable CI checks passed on `342e6d9c3`; 2 conditional checks skipped. The Slack browser and CLI startup jobs passed on their single unchanged-head rerun. Its Apex review returned 4/5 with one pending-restoration issue. Commit `1b58943b1` reconciles that durable intent before cleanup, advances the generation without reopening the Core row, and blocks direct removal or retirement while intent remains unresolved. Standard Greptile reviewed `1b58943b1` at 5/5 with no new findings. All 54 applicable CI checks passed on `1b58943b1`; 3 conditional checks skipped. The chat job passed on its single unchanged-head rerun. Apex then returned 4/5 for a missing cleanup wake after recovery. Commit `8214b3ca5` atomically registers cleanup intent before storage intent and recovery-result writes. Its provider test observes real committed notification hints and the visible advanced generation. Standard Greptile reviewed `8214b3ca5` at 5/5 with no new findings. All 55 applicable current-head CI checks passed on the first run; 2 conditional checks skipped. Final Apex verification completed at 5/5 on this exact head: 38 files reviewed, no new comments, and no unresolved threads. The PR is ready for review and mergeable. - The first Apex review found five issues after a standard 5/5: application-pool starvation, stale pending selections, retirement during rejected source edits, lost cleanup retries, and reused inspection identities. Commits `6d72e7fd4` and `342e6d9c3` fix each with regression coverage. Archive lock waits use dedicated connections, and source edits fail promptly if the lifecycle is busy. Retirement compares normalized values. The normalized-source regression initially failed with the raw-value comparison; after moving the check after normalization, a clean provider-suite rerun passed all 24 tests at that stage. Those threads are resolved; the earlier Apex 0/5 is not a passing acceptance result. - Earlier local integration attempts could not bind localhost inside the sandbox. The same suites passed with permission to start local PostgreSQL. - The earlier broad local `pnpm test:run` overlapped edits and reported stale-revision and checkout-path/Git-fixture failures. It was not a final-tree result. Full CI subsequently passed; the original local failure remains part of verification history. - Local repository-wide typecheck/build cannot complete because `cargo` is unavailable. Direct server TypeScript checks and affected tests pass; full Rust and build validation comes from CI. - An earlier browser run on `ff918c5a8` failed in the unchanged case-filter journey: expected “Done,” received “All statuses,” with an announcement handler recorded during the assertion. The cause is not confirmed. [The failed job](https://github.com/paperclipai/paperclip/actions/runs/39500611857/job/118896954508) remains verification history. The unchanged shard passed in the next full CI run on `ec5c7209a`; no UI or fixture change was made. - Current-head browser shard 2 failed waiting five seconds for the mocked Slack setup Success heading. This PR changes neither that UI nor its fixture. [The failed job](https://github.com/paperclipai/paperclip/actions/runs/39506070513/job/118916021232) remains verification evidence. The cause is not confirmed; the single unchanged-shard rerun passed; no UI or fixture change was made, and the original cause remains unconfirmed. - The workspace test shard passed its 3,978 general tests, then its CLI company-import/export fixture timed out after 30 seconds waiting for startup health before creating any company or workspace. [The failed job](https://github.com/paperclipai/paperclip/actions/runs/39506070513/job/118916021855) remains verification history. The child reached external-PostgreSQL startup without exiting or reporting an exception. Its cause is not confirmed; the single unchanged-job rerun passed, including the CLI fixture. No startup or fixture change was made, and the original cause remains unconfirmed. - The new cached-removal regression initially failed because its fake worker advertised availability for unrelated fixture plugins, so another workspace changed its fake checkout state. Worker availability now matches the fixture plugin; the complete 25-test provider suite passes. - On `1b58943b1`, the chat shard timed out polling for one conversation after an authorized GitHub description edit. [The failed job](https://github.com/paperclipai/paperclip/actions/runs/39510521657/job/118930193418) remains evidence. The exact case passes locally against PostgreSQL (1 passed, 1,380 unrelated cases skipped), and this PR changes neither that test nor its handler. The original cause is unconfirmed; the single unchanged-job CI rerun passed without a code or fixture change. The original cause remains unconfirmed. - The diff was checked for credentials, private references, and generated artifacts. ## Risks This is an additive provider contract with no database migration. Existing projects keep their local behavior unless their policy selects a storage plugin. A selected provider must be ready and enabled. Unknown or unsafe cleanup fails closed. Managed native execution depends on #16978. Core refuses a host Runner fallback. Providers must fence lifecycle generations, preserve ambiguous retries, and report remote recovery honestly. Provider-specific live storage and guest mount qualification remain separate from these Core contract tests. ## Model Used OpenAI Codex (GPT-6), with repository inspection, code execution, and tests. The exact model variant was not exposed. ## 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 linked existing issues or described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links - [x] My branch name describes the change and contains no internal ticket id - [x] I have run tests locally and they pass (affected suites; broad-run limits are documented above) - [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>
620 lines
24 KiB
TypeScript
620 lines
24 KiB
TypeScript
import type { PluginWorkspaceParams, PluginWorkspaceResult } from "./workspace-provider.js";
|
|
import type { PluginEnvironmentTaskParams, PluginEnvironmentTaskResult } from "./environment-tasks.js";
|
|
import type { AgentLifecycleRequest, AgentLifecycleResult } from "@paperclipai/shared";
|
|
import type { AiConnectionRouterRequest, AiConnectionRouterResult } from "@paperclipai/shared";
|
|
/**
|
|
* `definePlugin` — the top-level helper for authoring a Paperclip plugin.
|
|
*
|
|
* Plugin authors call `definePlugin()` and export the result as the default
|
|
* export from their worker entrypoint. The host imports the worker module,
|
|
* calls `setup()` with a `PluginContext`, and from that point the plugin
|
|
* responds to events, jobs, webhooks, and UI requests through the context.
|
|
*
|
|
* @see PLUGIN_SPEC.md §14.1 — Example SDK Shape
|
|
*
|
|
* @example
|
|
* ```ts
|
|
* // dist/worker.ts
|
|
* import { definePlugin } from "@paperclipai/plugin-sdk";
|
|
*
|
|
* export default definePlugin({
|
|
* async setup(ctx) {
|
|
* ctx.logger.info("Linear sync plugin starting");
|
|
*
|
|
* // Subscribe to events
|
|
* ctx.events.on("issue.created", async (event) => {
|
|
* const companyId = event.companyId;
|
|
* const config = await ctx.config.get(companyId);
|
|
* const apiKey = await ctx.secrets.resolve(config.apiKeyRef, { companyId, configPath: "apiKeyRef" });
|
|
* await ctx.http.fetch(`https://api.linear.app/...`, {
|
|
* method: "POST",
|
|
* headers: { Authorization: `Bearer ${apiKey}` },
|
|
* body: JSON.stringify({ title: event.payload.title }),
|
|
* });
|
|
* });
|
|
*
|
|
* // Register a job handler
|
|
* ctx.jobs.register("full-sync", async (job) => {
|
|
* ctx.logger.info("Running full-sync job", { runId: job.runId });
|
|
* // ... sync logic
|
|
* });
|
|
*
|
|
* // Register data for the UI
|
|
* ctx.data.register("sync-health", async ({ companyId }) => {
|
|
* const state = await ctx.state.get({
|
|
* scopeKind: "company",
|
|
* scopeId: String(companyId),
|
|
* stateKey: "last-sync",
|
|
* });
|
|
* return { lastSync: state };
|
|
* });
|
|
* },
|
|
* });
|
|
* ```
|
|
*/
|
|
|
|
import type { PluginContext, ResourceLifecycleEvent, ResourceLifecycleResult } from "./types.js";
|
|
import type {
|
|
PluginEnvironmentAcquireLeaseParams,
|
|
PluginEnvironmentDestroyLeaseParams,
|
|
PluginEnvironmentInspectLeaseParams,
|
|
PluginEnvironmentLeaseObservation,
|
|
PluginEnvironmentExecuteParams,
|
|
PluginEnvironmentExecuteResult,
|
|
PluginEnvironmentRunnerIngressEndpointParams,
|
|
PluginEnvironmentRunnerIngressEndpoint,
|
|
PluginEnvironmentSyncInParams,
|
|
PluginEnvironmentSyncOutParams,
|
|
PluginEnvironmentSyncResult,
|
|
PluginEnvironmentStartInteractiveSetupParams,
|
|
PluginEnvironmentInteractiveSetupSession,
|
|
PluginEnvironmentGetInteractiveSetupParams,
|
|
PluginEnvironmentCaptureTemplateParams,
|
|
PluginEnvironmentCaptureTemplateResult,
|
|
PluginEnvironmentCancelInteractiveSetupParams,
|
|
PluginEnvironmentCancelInteractiveSetupResult,
|
|
PluginEnvironmentDeleteTemplateParams,
|
|
PluginEnvironmentDeleteTemplateResult,
|
|
PluginEnvironmentLease,
|
|
PluginEnvironmentProbeParams,
|
|
PluginEnvironmentProbeResult,
|
|
PluginEnvironmentRealizeWorkspaceParams,
|
|
PluginEnvironmentRealizeWorkspaceResult,
|
|
PluginEnvironmentReleaseLeaseParams,
|
|
PluginEnvironmentTerminationReceipt,
|
|
PluginEnvironmentResumeLeaseParams,
|
|
PluginEnvironmentValidateConfigParams,
|
|
PluginEnvironmentValidationResult,
|
|
DetectExternalObjectsParams,
|
|
DetectExternalObjectsResult,
|
|
ResolveExternalObjectParams,
|
|
PluginExternalObjectResolveResult,
|
|
RefreshExternalObjectsParams,
|
|
RefreshExternalObjectsResult,
|
|
PluginLoginPtyOpenParams,
|
|
PluginLoginPtyOpenResult,
|
|
PluginLoginPtyInputParams,
|
|
PluginLoginPtyStopParams,
|
|
PluginLoginPtyCloseParams,
|
|
PluginLoginPtyCloseResult,
|
|
PluginDuplexChannelOpenParams,
|
|
PluginDuplexChannelOpenResult,
|
|
PluginDuplexChannelWriteParams,
|
|
PluginDuplexChannelStopParams,
|
|
PluginDuplexChannelCloseParams,
|
|
PluginDuplexChannelCloseResult,
|
|
} from "./protocol.js";
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// Health check result
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Optional plugin-reported diagnostics returned from the `health()` RPC method.
|
|
*
|
|
* @see PLUGIN_SPEC.md §13.2 — `health`
|
|
*/
|
|
export interface PluginHealthDiagnostics {
|
|
/** Machine-readable status: `"ok"` | `"degraded"` | `"error"`. */
|
|
status: "ok" | "degraded" | "error";
|
|
/** Human-readable description of the current health state. */
|
|
message?: string;
|
|
/** Plugin-reported key-value diagnostics (e.g. connection status, queue depth). */
|
|
details?: Record<string, unknown>;
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// Config validation result
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Result returned from the `validateConfig()` RPC method.
|
|
*
|
|
* @see PLUGIN_SPEC.md §13.3 — `validateConfig`
|
|
*/
|
|
export interface PluginConfigValidationResult {
|
|
/** Whether the config is valid. */
|
|
ok: boolean;
|
|
/** Non-fatal warnings about the config. */
|
|
warnings?: string[];
|
|
/** Validation errors (populated when `ok` is `false`). */
|
|
errors?: string[];
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// Webhook handler input
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Input received by the plugin worker's `handleWebhook` handler.
|
|
*
|
|
* @see PLUGIN_SPEC.md §13.7 — `handleWebhook`
|
|
*/
|
|
export interface PluginWebhookInput {
|
|
/** Endpoint key matching the manifest declaration. */
|
|
endpointKey: string;
|
|
/** Inbound request headers. */
|
|
headers: Record<string, string | string[]>;
|
|
/** Raw request body as a UTF-8 string. */
|
|
rawBody: string;
|
|
/** Parsed JSON body (if applicable and parseable). */
|
|
parsedBody?: unknown;
|
|
/** Unique request identifier for idempotency checks. */
|
|
requestId: string;
|
|
}
|
|
|
|
export interface PluginApiRequestInput {
|
|
routeKey: string;
|
|
method: string;
|
|
path: string;
|
|
params: Record<string, string>;
|
|
query: Record<string, string | string[]>;
|
|
body: unknown;
|
|
actor: {
|
|
actorType: "user" | "agent";
|
|
actorId: string;
|
|
agentId?: string | null;
|
|
userId?: string | null;
|
|
runId?: string | null;
|
|
};
|
|
companyId: string;
|
|
headers: Record<string, string>;
|
|
}
|
|
|
|
export interface PluginApiResponse {
|
|
status?: number;
|
|
headers?: Record<string, string>;
|
|
body?: unknown;
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// Config change context
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Scope metadata delivered alongside a `configChanged` RPC so the worker knows
|
|
* *which company's* configuration changed.
|
|
*
|
|
* The host→worker `configChanged` message has always carried the company scope,
|
|
* but the SDK historically dropped it before invoking `onConfigChanged`, leaving
|
|
* proactive plugins to keep a single worker-global config. That is safe for a
|
|
* single-tenant plugin but silently collapses a multi-company plugin onto
|
|
* whichever company's config was delivered last. Threading the scope through
|
|
* lets a `multiCompanyConfig` plugin maintain per-company state.
|
|
*
|
|
* @see PLUGIN_SPEC.md §13.4 — `configChanged`
|
|
*/
|
|
export interface PluginConfigChangeContext {
|
|
/**
|
|
* The company whose configuration changed, or `null` for an instance/global
|
|
* save that is not bound to a specific company.
|
|
*/
|
|
companyId: string | null;
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// Plugin definition
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* The plugin definition shape passed to `definePlugin()`.
|
|
*
|
|
* The only required field is `setup`, which receives the `PluginContext` and
|
|
* is where the plugin registers its handlers (events, jobs, data, actions,
|
|
* tools, etc.).
|
|
*
|
|
* All other lifecycle hooks are optional. If a hook is not implemented the
|
|
* host applies default behaviour (e.g. restarting the worker on config change
|
|
* instead of calling `onConfigChanged`).
|
|
*
|
|
* @see PLUGIN_SPEC.md §13 — Host-Worker Protocol
|
|
*/
|
|
export interface PluginDefinition {
|
|
/**
|
|
* Called once when the plugin worker starts up, after `initialize` completes.
|
|
*
|
|
* This is where the plugin registers all its handlers: event subscriptions,
|
|
* job handlers, data/action handlers, and tool registrations. Registration
|
|
* must be synchronous after `setup` resolves — do not register handlers
|
|
* inside async callbacks that may resolve after `setup` returns.
|
|
*
|
|
* @param ctx - The full plugin context provided by the host
|
|
*/
|
|
setup(ctx: PluginContext): Promise<void>;
|
|
|
|
/**
|
|
* Called when the host wants to know if the plugin is healthy.
|
|
*
|
|
* The host polls this on a regular interval and surfaces the result in the
|
|
* plugin health dashboard. If not implemented, the host infers health from
|
|
* worker process liveness.
|
|
*
|
|
* @see PLUGIN_SPEC.md §13.2 — `health`
|
|
*/
|
|
onHealth?(): Promise<PluginHealthDiagnostics>;
|
|
|
|
/**
|
|
* When true, this plugin's worker correctly serves configuration from more
|
|
* than one company inside a single worker process — for example by keying its
|
|
* state on `context.companyId` in `onConfigChanged` and running one connection
|
|
* / subscription set per company.
|
|
*
|
|
* When false or omitted (the default), the plugin is treated as single-tenant.
|
|
* The host then **fails closed** if `configChanged` would ever deliver a
|
|
* second, distinct company's configuration to the same worker: instead of
|
|
* silently collapsing the worker onto whichever company arrived last (a
|
|
* cross-tenant identity/secret confusion bug), the delivery is rejected with
|
|
* `PLUGIN_RPC_ERROR_CODES.CROSS_TENANT_CONFIG`. Re-delivering an unchanged
|
|
* config for a different company (idempotent replay) is still allowed.
|
|
*/
|
|
multiCompanyConfig?: boolean;
|
|
|
|
/**
|
|
* Called when the operator updates this plugin's company-scoped configuration
|
|
* at runtime, without restarting the worker.
|
|
*
|
|
* If not implemented, the host restarts the worker to apply the new config.
|
|
*
|
|
* @param newConfig - The newly resolved configuration
|
|
* @param context - Scope of the change. `context.companyId` identifies the
|
|
* company whose config changed (null for an instance/global save). A
|
|
* multi-company plugin (`multiCompanyConfig: true`) MUST key its per-company
|
|
* state on this value rather than assuming a single global config.
|
|
* @see PLUGIN_SPEC.md §13.4 — `configChanged`
|
|
*/
|
|
onConfigChanged?(
|
|
newConfig: Record<string, unknown>,
|
|
context?: PluginConfigChangeContext,
|
|
): Promise<void>;
|
|
|
|
/**
|
|
* Called when the host is about to shut down the plugin worker.
|
|
*
|
|
* The worker has at most 10 seconds (configurable via plugin config) to
|
|
* finish in-flight work and resolve this promise. After the deadline the
|
|
* host sends SIGTERM, then SIGKILL.
|
|
*
|
|
* @see PLUGIN_SPEC.md §12.5 — Graceful Shutdown Policy
|
|
*/
|
|
onShutdown?(): Promise<void>;
|
|
|
|
/** Prove plugin-owned background work is quiescent for idle sleep.
|
|
* The SDK first closes admission and checks accepted RPCs and notifications.
|
|
* Return `none` only when timers, sockets, detached operations and cleanup
|
|
* are settled and cannot start work until signal aborts. Do not cancel useful
|
|
* work to satisfy this check. Missing hooks, failures and uncertainty block
|
|
* sleep. The signal aborts on exact-owner release or bounded hold expiry.
|
|
* Plugins with autonomous work must keep returning `present` unless they
|
|
* can safely suspend and resume that work under this contract.
|
|
*/
|
|
onIdleDrain?(signal: AbortSignal): Promise<"none" | "present" | "unknown">;
|
|
|
|
/**
|
|
* Called to validate the current plugin configuration.
|
|
*
|
|
* The host calls this:
|
|
* - after the plugin starts (to surface config errors immediately)
|
|
* - after the operator saves a new config (to validate before persisting)
|
|
* - via the "Test Connection" button in the settings UI
|
|
*
|
|
* @param config - The configuration to validate
|
|
* @see PLUGIN_SPEC.md §13.3 — `validateConfig`
|
|
*/
|
|
onValidateConfig?(config: Record<string, unknown>): Promise<PluginConfigValidationResult>;
|
|
|
|
/**
|
|
* Called to handle an inbound webhook delivery.
|
|
*
|
|
* The host routes `POST /api/plugins/:pluginId/webhooks/:endpointKey` to
|
|
* this handler. The plugin is responsible for signature verification using
|
|
* a resolved secret ref.
|
|
*
|
|
* If not implemented but webhooks are declared in the manifest, the host
|
|
* returns HTTP 501 for webhook deliveries.
|
|
*
|
|
* @param input - Webhook delivery metadata and payload
|
|
* @see PLUGIN_SPEC.md §13.7 — `handleWebhook`
|
|
*/
|
|
onWebhook?(input: PluginWebhookInput): Promise<void>;
|
|
|
|
/**
|
|
* Called for manifest-declared scoped JSON API routes under
|
|
* `/api/plugins/:pluginId/api/*` after the host has enforced auth, company
|
|
* access, capabilities, and checkout policy.
|
|
*/
|
|
onApiRequest?(input: PluginApiRequestInput): Promise<PluginApiResponse>;
|
|
|
|
/**
|
|
* Called when Paperclip scans issue/comment/document content and asks this
|
|
* plugin whether any sanitized URL candidates belong to its external object
|
|
* providers. The host has already stripped URL userinfo, query strings, and
|
|
* fragments unless provider-safe identity components were explicitly hashed.
|
|
*
|
|
* Requires `external.objects.detect`.
|
|
*/
|
|
onDetectExternalObjects?(
|
|
params: DetectExternalObjectsParams,
|
|
): Promise<DetectExternalObjectsResult>;
|
|
|
|
/**
|
|
* Complete required work for the committed agent lifecycle phase.
|
|
* Requires manifest `agentLifecycle: true` and `agents.lifecycle.manage`.
|
|
* Echo operationId/version; return pending until the effect finishes.
|
|
* Calls can repeat. Fence older versions and make external effects idempotent.
|
|
*/
|
|
onAgentLifecycle?(params: AgentLifecycleRequest): Promise<AgentLifecycleResult>;
|
|
|
|
/**
|
|
* Reconcile a committed resource event. Requires manifest resourceLifecycle and events.subscribe.
|
|
* The host acknowledges successful results and replays interrupted/unfinished work.
|
|
* Calls are at least once, in order per resource. Re-read current state and use
|
|
* idempotent external operations; deletion events remain available after the row is gone.
|
|
*/
|
|
onResourceLifecycle?(event: ResourceLifecycleEvent): Promise<ResourceLifecycleResult>;
|
|
|
|
/** Propose a member from host-authorized candidates. Requires ai.connections.route. */
|
|
onRouteAiConnection?(params: AiConnectionRouterRequest): Promise<AiConnectionRouterResult>;
|
|
|
|
/**
|
|
* Called when Paperclip needs the current normalized status for one external
|
|
* object owned by a manifest-declared provider.
|
|
*
|
|
* Requires `external.objects.read`.
|
|
*/
|
|
onResolveExternalObject?(
|
|
params: ResolveExternalObjectParams,
|
|
): Promise<PluginExternalObjectResolveResult>;
|
|
|
|
/**
|
|
* Optional batch resolver used by providers that can refresh many objects
|
|
* more efficiently than individual `onResolveExternalObject` calls.
|
|
*
|
|
* Requires `external.objects.refresh`.
|
|
*/
|
|
onRefreshExternalObjects?(
|
|
params: RefreshExternalObjectsParams,
|
|
): Promise<RefreshExternalObjectsResult>;
|
|
|
|
/**
|
|
* Called to validate provider-specific configuration for a plugin-hosted
|
|
* environment driver.
|
|
*/
|
|
onEnvironmentValidateConfig?(
|
|
params: PluginEnvironmentValidateConfigParams,
|
|
): Promise<PluginEnvironmentValidationResult>;
|
|
|
|
/** Required with manifest.workspaceProvider, together with project resource lifecycle. */
|
|
onWorkspaceOperation?(params: PluginWorkspaceParams): Promise<PluginWorkspaceResult>;
|
|
|
|
/** Provide Runner execution: prepare resources, start Runner, connect via PRP, and manage task lifecycle. */
|
|
onEnvironmentTask?(params: PluginEnvironmentTaskParams): Promise<PluginEnvironmentTaskResult>;
|
|
|
|
/** Called to test reachability or readiness of a plugin-hosted environment. */
|
|
onEnvironmentProbe?(
|
|
params: PluginEnvironmentProbeParams,
|
|
): Promise<PluginEnvironmentProbeResult>;
|
|
|
|
/** Called before a run starts to acquire a provider lease. */
|
|
onEnvironmentAcquireLease?(
|
|
params: PluginEnvironmentAcquireLeaseParams,
|
|
): Promise<PluginEnvironmentLease>;
|
|
|
|
/** Called to reconnect to a previously acquired provider lease. */
|
|
onEnvironmentResumeLease?(
|
|
params: PluginEnvironmentResumeLeaseParams,
|
|
): Promise<PluginEnvironmentLease>;
|
|
|
|
/** Called when a run finishes and the provider lease can be released. */
|
|
onEnvironmentReleaseLease?(
|
|
params: PluginEnvironmentReleaseLeaseParams,
|
|
): Promise<PluginEnvironmentTerminationReceipt | void>;
|
|
|
|
/** Stop this exact allocation and retain all files, regardless of release
|
|
* policy. Throw if stop cannot be confirmed; never destroy as a fallback.
|
|
* Separate worker discovery lets the host safely defer older providers. */
|
|
onEnvironmentStopLease?(
|
|
params: PluginEnvironmentReleaseLeaseParams,
|
|
): Promise<PluginEnvironmentTerminationReceipt>;
|
|
|
|
/** Called when the host needs to force-destroy provider state. */
|
|
onEnvironmentDestroyLease?(
|
|
params: PluginEnvironmentDestroyLeaseParams,
|
|
): Promise<PluginEnvironmentTerminationReceipt | void>;
|
|
|
|
/** Read provider state only. This must not start or reconnect a sandbox. */
|
|
onEnvironmentInspectLease?(
|
|
params: PluginEnvironmentInspectLeaseParams,
|
|
): Promise<PluginEnvironmentLeaseObservation>;
|
|
|
|
/** Called to materialize the run workspace inside the provider lease. */
|
|
onEnvironmentRealizeWorkspace?(
|
|
params: PluginEnvironmentRealizeWorkspaceParams,
|
|
): Promise<PluginEnvironmentRealizeWorkspaceResult>;
|
|
|
|
/** Called to execute a command inside the provider lease. */
|
|
onEnvironmentExecute?(
|
|
params: PluginEnvironmentExecuteParams,
|
|
): Promise<PluginEnvironmentExecuteResult>;
|
|
|
|
/** Return an authenticated private WebSocket ingress for runnerd. */
|
|
onEnvironmentRunnerIngressEndpoint?(
|
|
params: PluginEnvironmentRunnerIngressEndpointParams,
|
|
): Promise<PluginEnvironmentRunnerIngressEndpoint>;
|
|
|
|
/**
|
|
* Optional, opt-in: called before execution to place host files/directories at
|
|
* target sandbox paths using a provider-native transport instead of the default
|
|
* base64-over-exec fallback. Defining this hook (together with
|
|
* `onEnvironmentSyncOut`) advertises `environmentSyncIn`; leaving it undefined
|
|
* keeps the byte-identical fallback. See `doc/plugins/SANDBOX_FILE_SYNC_HOOKS.md`.
|
|
*/
|
|
onEnvironmentSyncIn?(
|
|
params: PluginEnvironmentSyncInParams,
|
|
): Promise<PluginEnvironmentSyncResult>;
|
|
|
|
/**
|
|
* Optional, opt-in: called after execution to copy sandbox files/directories
|
|
* back to target host paths using a provider-native transport. Defining this
|
|
* hook (together with `onEnvironmentSyncIn`) advertises `environmentSyncOut`.
|
|
* See `doc/plugins/SANDBOX_FILE_SYNC_HOOKS.md`.
|
|
*/
|
|
onEnvironmentSyncOut?(
|
|
params: PluginEnvironmentSyncOutParams,
|
|
): Promise<PluginEnvironmentSyncResult>;
|
|
|
|
/** Called to start an interactive setup sandbox and return redacted connection metadata. */
|
|
onEnvironmentStartInteractiveSetup?(
|
|
params: PluginEnvironmentStartInteractiveSetupParams,
|
|
): Promise<PluginEnvironmentInteractiveSetupSession>;
|
|
|
|
/** Called to read setup status and, when authorized, a one-time connection payload. */
|
|
onEnvironmentGetInteractiveSetup?(
|
|
params: PluginEnvironmentGetInteractiveSetupParams,
|
|
): Promise<PluginEnvironmentInteractiveSetupSession>;
|
|
|
|
/** Called to capture a reusable provider template from a live setup sandbox. */
|
|
onEnvironmentCaptureTemplate?(
|
|
params: PluginEnvironmentCaptureTemplateParams,
|
|
): Promise<PluginEnvironmentCaptureTemplateResult>;
|
|
|
|
/** Called to cancel and clean up a setup sandbox without promoting a template. */
|
|
onEnvironmentCancelInteractiveSetup?(
|
|
params: PluginEnvironmentCancelInteractiveSetupParams,
|
|
): Promise<PluginEnvironmentCancelInteractiveSetupResult>;
|
|
|
|
/** Called for optional best-effort cleanup of a captured provider template. */
|
|
onEnvironmentDeleteTemplate?(
|
|
params: PluginEnvironmentDeleteTemplateParams,
|
|
): Promise<PluginEnvironmentDeleteTemplateResult>;
|
|
|
|
/**
|
|
* Called to open one live Claude `setup-token` login pseudo-terminal.
|
|
* The worker registers the terminal under the host route identifier and returns a
|
|
* worker session identifier for the output notification binding only. The worker
|
|
* streams output and the exit through `ctx.loginPty`, never as a reply.
|
|
* Defining the four `onLoginPty*` hooks advertises the four methods.
|
|
*/
|
|
onLoginPtyOpen?(
|
|
params: PluginLoginPtyOpenParams,
|
|
): Promise<PluginLoginPtyOpenResult>;
|
|
|
|
/** Called to write delayed input to an open login pseudo-terminal, keyed by the worker session identifier. */
|
|
onLoginPtyInput?(params: PluginLoginPtyInputParams): Promise<void>;
|
|
|
|
/** Called to stop an open login pseudo-terminal child, keyed by the worker session identifier. */
|
|
onLoginPtyStop?(params: PluginLoginPtyStopParams): Promise<void>;
|
|
|
|
/**
|
|
* Called to close an open login pseudo-terminal by the host route identifier. The
|
|
* worker closes the exact terminal registered under that identifier and returns a
|
|
* close acknowledgement that carries the same identifier.
|
|
*/
|
|
onLoginPtyClose?(
|
|
params: PluginLoginPtyCloseParams,
|
|
): Promise<PluginLoginPtyCloseResult>;
|
|
|
|
/**
|
|
* Called to open one persistent duplex channel. The worker registers the
|
|
* channel under the host route identifier and returns a worker session
|
|
* identifier for the data notification binding only. The worker streams data
|
|
* and the exit through worker→host notifications, never as a reply. Defining
|
|
* the four `onDuplexChannel*` hooks advertises the four methods. The host reads
|
|
* the open verb to gate the `duplexCommandStream` capability.
|
|
*
|
|
* HTTP/2 is the preferred transport. `queue_v1` is the soft-deprecated fallback.
|
|
*/
|
|
onDuplexChannelOpen?(
|
|
params: PluginDuplexChannelOpenParams,
|
|
): Promise<PluginDuplexChannelOpenResult>;
|
|
|
|
/** Called to write raw input to an open duplex channel, keyed by the worker session identifier. */
|
|
onDuplexChannelWrite?(params: PluginDuplexChannelWriteParams): Promise<void>;
|
|
|
|
/** Called to stop an open duplex channel child, keyed by the worker session identifier. */
|
|
onDuplexChannelStop?(params: PluginDuplexChannelStopParams): Promise<void>;
|
|
|
|
/**
|
|
* Called to close an open duplex channel by the host route identifier. The
|
|
* worker closes the exact channel registered under that identifier and returns
|
|
* a close acknowledgement that carries the same identifier.
|
|
*/
|
|
onDuplexChannelClose?(
|
|
params: PluginDuplexChannelCloseParams,
|
|
): Promise<PluginDuplexChannelCloseResult>;
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// PaperclipPlugin — the sealed object returned by definePlugin()
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* The sealed plugin object returned by `definePlugin()`.
|
|
*
|
|
* Plugin authors export this as the default export from their worker
|
|
* entrypoint. The host imports it and calls the lifecycle methods.
|
|
*
|
|
* @see PLUGIN_SPEC.md §14 — SDK Surface
|
|
*/
|
|
export interface PaperclipPlugin {
|
|
/** The original plugin definition passed to `definePlugin()`. */
|
|
readonly definition: PluginDefinition;
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// definePlugin — top-level factory
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Define a Paperclip plugin.
|
|
*
|
|
* Call this function in your worker entrypoint and export the result as the
|
|
* default export. The host will import the module and call lifecycle methods
|
|
* on the returned object.
|
|
*
|
|
* @param definition - Plugin lifecycle handlers
|
|
* @returns A sealed `PaperclipPlugin` object for the host to consume
|
|
*
|
|
* @example
|
|
* ```ts
|
|
* import { definePlugin } from "@paperclipai/plugin-sdk";
|
|
*
|
|
* export default definePlugin({
|
|
* async setup(ctx) {
|
|
* ctx.logger.info("Plugin started");
|
|
* ctx.events.on("issue.created", async (event) => {
|
|
* // handle event
|
|
* });
|
|
* },
|
|
*
|
|
* async onHealth() {
|
|
* return { status: "ok" };
|
|
* },
|
|
* });
|
|
* ```
|
|
*
|
|
* @see PLUGIN_SPEC.md §14.1 — Example SDK Shape
|
|
*/
|
|
export function definePlugin(definition: PluginDefinition): PaperclipPlugin {
|
|
return Object.freeze({ definition });
|
|
}
|