3c73ed26b5
## Thinking Path > - Paperclip orchestrates AI agents for zero-human companies > - The plugin system is the extension boundary for optional product capabilities > - Rich plugins need more than a worker entrypoint: they need scoped database storage, local project folders, managed agents/routines, host navigation, and reusable UI components > - The LLM Wiki work exposed those missing host surfaces while keeping plugin code outside the core control plane > - This pull request expands the core plugin host, SDK, server APIs, and UI bridge so plugins can declare and use those surfaces > - The benefit is that future plugins can integrate with Paperclip through documented, validated contracts instead of bespoke server or UI imports ## What Changed - Added plugin-managed database namespaces and migration tracking, including Drizzle schema/migration files and SQL validation for namespace isolation. - Added server support for plugin local folders, managed agents, managed routines, scoped plugin APIs, and plugin operation visibility. - Expanded shared plugin manifest/types/validators and SDK host/testing/UI exports for richer plugin surfaces. - Added reusable UI pieces for file trees, managed routines, resizable sidebars, route sidebars, and plugin bridge initialization. - Updated plugin docs and example plugins to use the expanded host and SDK surface. ## Verification - `pnpm install --frozen-lockfile` - `pnpm run preflight:workspace-links && pnpm exec vitest run packages/shared/src/validators/plugin.test.ts server/src/__tests__/plugin-database.test.ts server/src/__tests__/plugin-local-folders.test.ts server/src/__tests__/plugin-managed-agents.test.ts server/src/__tests__/plugin-managed-routines.test.ts server/src/__tests__/plugin-orchestration-apis.test.ts ui/src/api/plugins.test.ts ui/src/components/FileTree.test.tsx ui/src/components/ResizableSidebarPane.test.tsx ui/src/pages/PluginPage.test.tsx ui/src/plugins/bridge.test.ts` passed: 11 files, 67 tests. - Confirmed this PR changes 89 files and does not include `pnpm-lock.yaml` or `.github/workflows/*`. ## Risks - Medium: this expands plugin host contracts across db/shared/server/ui and includes a new core migration (`0076_useful_elektra.sql`). - The plugin database namespace validator is intentionally restrictive; plugin authors may need follow-up affordances for SQL patterns that remain blocked. - Merge this before the LLM Wiki plugin PR so the plugin can resolve the new SDK and host APIs. > 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 coding agent, tool-enabled shell/git/GitHub workflow. Context window size was 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 run tests locally and they pass - [x] I have added or updated tests where applicable - [x] 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 --------- Co-authored-by: Paperclip <noreply@paperclip.ing>
228 lines
7.5 KiB
TypeScript
228 lines
7.5 KiB
TypeScript
import type {
|
|
PluginDataResult,
|
|
PluginActionFn,
|
|
HostLocation,
|
|
HostNavigation,
|
|
PluginHostContext,
|
|
PluginStreamResult,
|
|
PluginToastFn,
|
|
} from "./types.js";
|
|
import { getSdkUiRuntimeValue } from "./runtime.js";
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// usePluginData
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Fetch data from the plugin worker's registered `getData` handler.
|
|
*
|
|
* Calls `ctx.data.register(key, handler)` in the worker and returns the
|
|
* result as reactive state. Re-fetches when `params` changes.
|
|
*
|
|
* @template T The expected shape of the returned data
|
|
* @param key - The data key matching the handler registered with `ctx.data.register()`
|
|
* @param params - Optional parameters forwarded to the handler
|
|
* @returns `PluginDataResult<T>` with `data`, `loading`, `error`, and `refresh`
|
|
*
|
|
* @example
|
|
* ```tsx
|
|
* function SyncWidget({ context }: PluginWidgetProps) {
|
|
* const { data, loading, error } = usePluginData<SyncHealth>("sync-health", {
|
|
* companyId: context.companyId,
|
|
* });
|
|
*
|
|
* if (loading) return <div>Loading…</div>;
|
|
* if (error) return <div>Error: {error.message}</div>;
|
|
* return <div>Synced Issues: {data!.syncedCount}</div>;
|
|
* }
|
|
* ```
|
|
*
|
|
* @see PLUGIN_SPEC.md §13.8 — `getData`
|
|
* @see PLUGIN_SPEC.md §19.7 — Error Propagation Through The Bridge
|
|
*/
|
|
export function usePluginData<T = unknown>(
|
|
key: string,
|
|
params?: Record<string, unknown>,
|
|
): PluginDataResult<T> {
|
|
const impl = getSdkUiRuntimeValue<
|
|
(nextKey: string, nextParams?: Record<string, unknown>) => PluginDataResult<T>
|
|
>("usePluginData");
|
|
return impl(key, params);
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// usePluginAction
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Get a callable function that invokes the plugin worker's registered
|
|
* `performAction` handler.
|
|
*
|
|
* The returned function is async and throws a `PluginBridgeError` on failure.
|
|
*
|
|
* @param key - The action key matching the handler registered with `ctx.actions.register()`
|
|
* @returns An async function that sends the action to the worker and resolves with the result
|
|
*
|
|
* @example
|
|
* ```tsx
|
|
* function ResyncButton({ context }: PluginWidgetProps) {
|
|
* const resync = usePluginAction("resync");
|
|
* const [error, setError] = useState<string | null>(null);
|
|
*
|
|
* async function handleClick() {
|
|
* try {
|
|
* await resync({ companyId: context.companyId });
|
|
* } catch (err) {
|
|
* setError((err as PluginBridgeError).message);
|
|
* }
|
|
* }
|
|
*
|
|
* return <button onClick={handleClick}>Resync Now</button>;
|
|
* }
|
|
* ```
|
|
*
|
|
* @see PLUGIN_SPEC.md §13.9 — `performAction`
|
|
* @see PLUGIN_SPEC.md §19.7 — Error Propagation Through The Bridge
|
|
*/
|
|
export function usePluginAction(key: string): PluginActionFn {
|
|
const impl = getSdkUiRuntimeValue<(nextKey: string) => PluginActionFn>("usePluginAction");
|
|
return impl(key);
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// useHostContext
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Read the current host context (active company, project, entity, user).
|
|
*
|
|
* Use this to know which context the plugin component is being rendered in
|
|
* so you can scope data requests and actions accordingly.
|
|
*
|
|
* @returns The current `PluginHostContext`
|
|
*
|
|
* @example
|
|
* ```tsx
|
|
* function IssueTab() {
|
|
* const { companyId, entityId } = useHostContext();
|
|
* const { data } = usePluginData("linear-link", { issueId: entityId });
|
|
* return <div>{data?.linearIssueUrl}</div>;
|
|
* }
|
|
* ```
|
|
*
|
|
* @see PLUGIN_SPEC.md §19 — UI Extension Model
|
|
*/
|
|
export function useHostContext(): PluginHostContext {
|
|
const impl = getSdkUiRuntimeValue<() => PluginHostContext>("useHostContext");
|
|
return impl();
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// useHostNavigation
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Navigate within the Paperclip host without forcing a full document reload.
|
|
*
|
|
* Use `linkProps()` for links so browser-native behavior still works:
|
|
* modifier-click, middle-click, copy-link, and open-in-new-tab all use the
|
|
* returned real `href`.
|
|
*
|
|
* @example
|
|
* ```tsx
|
|
* function WikiSidebarLink() {
|
|
* const hostNavigation = useHostNavigation();
|
|
* return <a {...hostNavigation.linkProps("/wiki")}>Wiki</a>;
|
|
* }
|
|
* ```
|
|
*/
|
|
export function useHostNavigation(): HostNavigation {
|
|
const impl = getSdkUiRuntimeValue<() => HostNavigation>("useHostNavigation");
|
|
return impl();
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// useHostLocation
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Observe the current host router location.
|
|
*
|
|
* Returns a snapshot of the active `pathname`, `search`, and `hash`. The
|
|
* component re-renders when any of these change (e.g. after the host router
|
|
* pushes a new entry, or after the browser back/forward gestures). Use this
|
|
* for URL-driven plugin UI such as a takeover sidebar with section-aware
|
|
* active state.
|
|
*
|
|
* @example
|
|
* ```tsx
|
|
* function WikiSection() {
|
|
* const { pathname } = useHostLocation();
|
|
* const section = pathname.split("/").filter(Boolean).at(-1) ?? "wiki";
|
|
* return <div>Active section: {section}</div>;
|
|
* }
|
|
* ```
|
|
*/
|
|
export function useHostLocation(): HostLocation {
|
|
const impl = getSdkUiRuntimeValue<() => HostLocation>("useHostLocation");
|
|
return impl();
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// usePluginStream
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Subscribe to a real-time event stream pushed from the plugin worker.
|
|
*
|
|
* Opens an SSE connection to `GET /api/plugins/:pluginId/bridge/stream/:channel`
|
|
* and accumulates events as they arrive. The worker pushes events using
|
|
* `ctx.streams.emit(channel, event)`.
|
|
*
|
|
* @template T The expected shape of each streamed event
|
|
* @param channel - The stream channel name (must match what the worker uses in `ctx.streams.emit`)
|
|
* @param options - Optional configuration for the stream
|
|
* @returns `PluginStreamResult<T>` with `events`, `lastEvent`, connection status, and `close()`
|
|
*
|
|
* @example
|
|
* ```tsx
|
|
* function ChatMessages() {
|
|
* const { events, connected, close } = usePluginStream<ChatToken>("chat-stream");
|
|
*
|
|
* return (
|
|
* <div>
|
|
* {events.map((e, i) => <span key={i}>{e.text}</span>)}
|
|
* {connected && <span className="pulse" />}
|
|
* <button onClick={close}>Stop</button>
|
|
* </div>
|
|
* );
|
|
* }
|
|
* ```
|
|
*
|
|
* @see PLUGIN_SPEC.md §19.8 — Real-Time Streaming
|
|
*/
|
|
export function usePluginStream<T = unknown>(
|
|
channel: string,
|
|
options?: { companyId?: string },
|
|
): PluginStreamResult<T> {
|
|
const impl = getSdkUiRuntimeValue<
|
|
(nextChannel: string, nextOptions?: { companyId?: string }) => PluginStreamResult<T>
|
|
>("usePluginStream");
|
|
return impl(channel, options);
|
|
}
|
|
|
|
// ---------------------------------------------------------------------------
|
|
// usePluginToast
|
|
// ---------------------------------------------------------------------------
|
|
|
|
/**
|
|
* Trigger a host toast notification from plugin UI.
|
|
*
|
|
* This lets plugin pages and widgets surface user-facing feedback through the
|
|
* same toast system as the host app without reaching into host internals.
|
|
*/
|
|
export function usePluginToast(): PluginToastFn {
|
|
const impl = getSdkUiRuntimeValue<() => PluginToastFn>("usePluginToast");
|
|
return impl();
|
|
}
|