mirror of
https://github.com/alkimake/paperclip.git
synced 2026-06-14 01:50:39 +09:00
## Thinking Path > - Paperclip orchestrates AI agents for zero-human companies. > - The environment/runtime layer decides where agent work executes and how the control plane reaches those runtimes. > - Today Paperclip can run locally and over SSH, but sandboxed execution needs a first-class environment model instead of one-off adapter behavior. > - We also want sandbox providers to be pluggable so the core does not hardcode every provider implementation. > - This branch adds the Sandbox environment path, the provider contract, and a deterministic fake provider plugin. > - That required synchronized changes across shared contracts, plugin SDK surfaces, server runtime orchestration, and the UI environment/workspace flows. > - The result is that sandbox execution becomes a core control-plane capability while keeping provider implementations extensible and testable. ## What Changed - Added sandbox runtime support to the environment execution path, including runtime URL discovery, sandbox execution targeting, orchestration, and heartbeat integration. - Added plugin-provider support for sandbox environments so providers can be supplied via plugins instead of hardcoded server logic. - Added the fake sandbox provider plugin with deterministic behavior suitable for local and automated testing. - Updated shared types, validators, plugin protocol definitions, and SDK helpers to carry sandbox provider and workspace-runtime contracts across package boundaries. - Updated server routes and services so companies can create sandbox environments, select them for work, and execute work through the sandbox runtime path. - Updated the UI environment and workspace surfaces to expose sandbox environment configuration and selection. - Added test coverage for sandbox runtime behavior, provider seams, environment route guards, orchestration, and the fake provider plugin. ## Verification - Ran locally before the final fixture-only scrub: - `pnpm -r typecheck` - `pnpm test:run` - `pnpm build` - Ran locally after the final scrub amend: - `pnpm vitest run server/src/__tests__/runtime-api.test.ts` - Reviewer spot checks: - create a sandbox environment backed by the fake provider plugin - run work through that environment - confirm sandbox provider execution does not inherit host secrets implicitly ## Risks - This touches shared contracts, plugin SDK plumbing, server runtime orchestration, and UI environment/workspace flows, so regressions would likely show up as cross-layer mismatches rather than isolated type errors. - Runtime URL discovery and sandbox callback selection are sensitive to host/bind configuration; if that logic is wrong, sandbox-backed callbacks may fail even when execution succeeds. - The fake provider plugin is intentionally deterministic and test-oriented; future providers may expose capability gaps that this branch does not yet cover. ## Model Used - OpenAI Codex coding agent on a GPT-5-class backend in the Paperclip/Codex harness. Exact backend model ID is not exposed in-session. Tool-assisted workflow with shell execution, file editing, git history inspection, and local test execution. ## 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 run tests locally and they pass - [x] I have added or updated tests where applicable - [ ] If this change affects the UI, I have included before/after screenshots - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [x] I will address all Greptile and reviewer comments before requesting merge
343 lines
11 KiB
TypeScript
343 lines
11 KiB
TypeScript
/**
|
|
* `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 config = await ctx.config.get();
|
|
* await ctx.http.fetch(`https://api.linear.app/...`, {
|
|
* method: "POST",
|
|
* headers: { Authorization: `Bearer ${await ctx.secrets.resolve(config.apiKeyRef as string)}` },
|
|
* 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 } from "./types.js";
|
|
import type {
|
|
PluginEnvironmentAcquireLeaseParams,
|
|
PluginEnvironmentDestroyLeaseParams,
|
|
PluginEnvironmentExecuteParams,
|
|
PluginEnvironmentExecuteResult,
|
|
PluginEnvironmentLease,
|
|
PluginEnvironmentProbeParams,
|
|
PluginEnvironmentProbeResult,
|
|
PluginEnvironmentRealizeWorkspaceParams,
|
|
PluginEnvironmentRealizeWorkspaceResult,
|
|
PluginEnvironmentReleaseLeaseParams,
|
|
PluginEnvironmentResumeLeaseParams,
|
|
PluginEnvironmentValidateConfigParams,
|
|
PluginEnvironmentValidationResult,
|
|
} 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;
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// 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>;
|
|
|
|
/**
|
|
* Called when the operator updates the plugin's instance 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
|
|
* @see PLUGIN_SPEC.md §13.4 — `configChanged`
|
|
*/
|
|
onConfigChanged?(newConfig: Record<string, unknown>): 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>;
|
|
|
|
/**
|
|
* 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 to validate provider-specific configuration for a plugin-hosted
|
|
* environment driver.
|
|
*/
|
|
onEnvironmentValidateConfig?(
|
|
params: PluginEnvironmentValidateConfigParams,
|
|
): Promise<PluginEnvironmentValidationResult>;
|
|
|
|
/** 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<void>;
|
|
|
|
/** Called when the host needs to force-destroy provider state. */
|
|
onEnvironmentDestroyLease?(
|
|
params: PluginEnvironmentDestroyLeaseParams,
|
|
): Promise<void>;
|
|
|
|
/** 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>;
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// 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 });
|
|
}
|