Expand plugin host surface (#5205)
## 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>
2026-05-05 07:42:57 -05:00
|
|
|
import { afterEach, describe, expect, it, vi } from "vitest";
|
|
|
|
|
import os from "node:os";
|
|
|
|
|
import path from "node:path";
|
|
|
|
|
import { promises as fs } from "node:fs";
|
|
|
|
|
import {
|
|
|
|
|
assertConfiguredLocalFolder,
|
|
|
|
|
assertWritableConfiguredLocalFolder,
|
|
|
|
|
inspectPluginLocalFolder,
|
|
|
|
|
listPluginLocalFolderEntries,
|
|
|
|
|
preparePluginLocalFolder,
|
|
|
|
|
readPluginLocalFolderText,
|
|
|
|
|
resolvePluginLocalFolderPath,
|
[codex] Add LLM Wiki plugin host support (#5597)
## Thinking Path
> - Paperclip orchestrates AI agents for zero-human companies.
> - The plugin system needs host contracts and runtime support before
large plugins can integrate cleanly.
> - The source branch mixed the LLM Wiki package with supporting
host/runtime work, managed plugin skills, root-level storage spaces, and
a bookmarks reference plugin.
> - [PAP-9173](/PAP/issues/PAP-9173) asked for the current branch to be
split by file boundary: plugin package separately from everything else.
> - [PAP-9188](/PAP/issues/PAP-9188) clarified that LLM Wiki may have
plugin-local spaces, but Paperclip core should not reorganize top-level
local storage into spaces.
> - Follow-up review clarified that the bookmarks example should not
ship in this PR either.
> - This pull request contains the
non-`packages/plugins/plugin-llm-wiki/` host/runtime work, keeps runtime
state under the selected Paperclip instance root, and no longer includes
the bookmarks example.
## What Changed
- Added/updated plugin host contracts, SDK types, worker RPC plumbing,
managed plugin skill support, and related server tests.
- Removed the bookmarks example plugin package and its
bundled-example/workspace references.
- Removed the root-level local spaces CLI/migration surface and restored
instance-root runtime defaults for config, db, logs, storage, secrets,
workspaces, projects, and adapter homes.
- Replaced shared root `space-paths` helpers with `home-paths` helpers
for core runtime storage.
- Tightened stranded recovery unique-conflict detection so concurrent
recovery scans reuse the raced recovery issue when Postgres errors are
wrapped.
- Kept `packages/plugins/plugin-llm-wiki/` out of this PR diff;
plugin-local spaces remain in the stacked plugin-only PR.
## Verification
- `pnpm exec vitest run cli/src/__tests__/data-dir.test.ts
cli/src/__tests__/home-paths.test.ts cli/src/__tests__/onboard.test.ts
packages/shared/src/home-paths.test.ts
packages/db/src/runtime-config.test.ts
server/src/__tests__/agent-instructions-service.test.ts
server/src/__tests__/claude-local-execute.test.ts
server/src/__tests__/codex-local-execute.test.ts`
- `pnpm exec vitest run packages/db/src/runtime-config.test.ts`
- `pnpm exec vitest run
server/src/__tests__/plugin-routes-authz.test.ts`
- `pnpm --filter @paperclipai/server typecheck`
- `pnpm exec vitest run
server/src/__tests__/heartbeat-process-recovery.test.ts -t "reuses the
raced stranded recovery issue"` skipped locally because embedded
Postgres did not initialize on this macOS temp host; the code path was
typechecked and is covered by Linux CI.
- Boundary check: no core references remain for `PAPERCLIP_SPACE_ID`,
`spaces migrate-default`, `@paperclipai/shared/space-paths`,
`registerSpacesCommands`, or the removed bookmarks example.
- Previous PR head `4f23e034` had green GitHub checks: `verify`, all
four serialized server shards, `e2e`, `Canary Dry Run`, `policy`, Snyk,
and `Greptile Review`. Current head `582f466d` is re-running checks
after the bookmarks deletion.
## Risks
- Plugin host changes touch shared runtime paths, so regressions would
most likely appear in adapter startup, plugin loading, or local dev path
defaults.
- Removing the bookmarks example also removes one demonstration of
plugin database namespaces plus local-folder persistence; remaining
plugin examples still cover bundled example discovery and plugin host
flows.
- The plugin package itself is intentionally deferred to the stacked
plugin-only PR, where LLM Wiki plugin-local spaces live.
- Existing installs that tested the transient root-level spaces CLI
should stop using it; this PR intentionally removes that unsupported
migration surface before merge.
> 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 Codex via Codex CLI, tool use and local code execution
enabled; context window 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 run tests locally and they pass, except where noted above
for host-specific embedded Postgres initialization
- [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
Stacked follow-up: PR #5592 contains only
`packages/plugins/plugin-llm-wiki/` and targets this branch.
---------
Co-authored-by: Paperclip <noreply@paperclip.ing>
2026-05-10 07:34:12 -05:00
|
|
|
deletePluginLocalFolderFile,
|
Expand plugin host surface (#5205)
## 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>
2026-05-05 07:42:57 -05:00
|
|
|
writePluginLocalFolderTextAtomic,
|
|
|
|
|
} from "../services/plugin-local-folders.js";
|
|
|
|
|
|
|
|
|
|
describe("plugin local folders", () => {
|
|
|
|
|
const tempRoots: string[] = [];
|
|
|
|
|
|
|
|
|
|
afterEach(async () => {
|
|
|
|
|
await Promise.all(tempRoots.map((root) => fs.rm(root, { recursive: true, force: true })));
|
|
|
|
|
tempRoots.length = 0;
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
async function makeRoot() {
|
|
|
|
|
const root = await fs.mkdtemp(path.join(os.tmpdir(), "paperclip-plugin-folder-"));
|
|
|
|
|
tempRoots.push(root);
|
|
|
|
|
return root;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
it("reports a healthy generic folder when required paths exist", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
await fs.mkdir(path.join(root, "sources"));
|
|
|
|
|
await fs.writeFile(path.join(root, "schema.md"), "schema", "utf8");
|
|
|
|
|
|
|
|
|
|
const status = await inspectPluginLocalFolder({
|
|
|
|
|
folderKey: "content-root",
|
|
|
|
|
storedConfig: {
|
|
|
|
|
path: root,
|
|
|
|
|
access: "readWrite",
|
|
|
|
|
requiredDirectories: ["sources"],
|
|
|
|
|
requiredFiles: ["schema.md"],
|
|
|
|
|
},
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
expect(status.healthy).toBe(true);
|
|
|
|
|
expect(status.problems).toEqual([]);
|
|
|
|
|
expect(status.requiredDirectories).toEqual(["sources"]);
|
|
|
|
|
expect(status.requiredFiles).toEqual(["schema.md"]);
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
it("reports missing required folders and files without using product-specific branches", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
|
|
|
|
|
const status = await inspectPluginLocalFolder({
|
|
|
|
|
folderKey: "content-root",
|
|
|
|
|
storedConfig: {
|
|
|
|
|
path: root,
|
|
|
|
|
requiredDirectories: ["sources"],
|
|
|
|
|
requiredFiles: ["schema.md"],
|
|
|
|
|
},
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
expect(status.healthy).toBe(false);
|
|
|
|
|
expect(status.missingDirectories).toEqual(["sources"]);
|
|
|
|
|
expect(status.missingFiles).toEqual(["schema.md"]);
|
|
|
|
|
expect(status.problems.map((item) => item.code)).toEqual(
|
|
|
|
|
expect.arrayContaining(["missing_directory", "missing_file"]),
|
|
|
|
|
);
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
it("reports all required paths as missing when the configured root does not exist", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
const missingRoot = path.join(root, "missing-root");
|
|
|
|
|
|
|
|
|
|
const status = await inspectPluginLocalFolder({
|
|
|
|
|
folderKey: "content-root",
|
|
|
|
|
storedConfig: {
|
|
|
|
|
path: missingRoot,
|
|
|
|
|
requiredDirectories: ["sources"],
|
|
|
|
|
requiredFiles: ["schema.md"],
|
|
|
|
|
},
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
expect(status.healthy).toBe(false);
|
|
|
|
|
expect(status.configured).toBe(true);
|
|
|
|
|
expect(status.readable).toBe(false);
|
|
|
|
|
expect(status.missingDirectories).toEqual(["sources"]);
|
|
|
|
|
expect(status.missingFiles).toEqual(["schema.md"]);
|
|
|
|
|
expect(status.problems.map((item) => item.code)).toContain("missing");
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
it("uses manifest declaration access and required paths over stored or caller overrides", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
await fs.mkdir(path.join(root, "manifest-dir"));
|
|
|
|
|
await fs.writeFile(path.join(root, "manifest.md"), "schema", "utf8");
|
|
|
|
|
|
|
|
|
|
const status = await inspectPluginLocalFolder({
|
|
|
|
|
folderKey: "content-root",
|
|
|
|
|
declaration: {
|
|
|
|
|
folderKey: "content-root",
|
|
|
|
|
displayName: "Content root",
|
|
|
|
|
access: "read",
|
|
|
|
|
requiredDirectories: ["manifest-dir"],
|
|
|
|
|
requiredFiles: ["manifest.md"],
|
|
|
|
|
},
|
|
|
|
|
storedConfig: {
|
|
|
|
|
path: root,
|
|
|
|
|
access: "readWrite",
|
|
|
|
|
requiredDirectories: ["stored-dir"],
|
|
|
|
|
requiredFiles: ["stored.md"],
|
|
|
|
|
},
|
|
|
|
|
overrideConfig: {
|
|
|
|
|
access: "readWrite",
|
|
|
|
|
requiredDirectories: ["override-dir"],
|
|
|
|
|
requiredFiles: ["override.md"],
|
|
|
|
|
},
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
expect(status.access).toBe("read");
|
|
|
|
|
expect(status.writable).toBe(false);
|
|
|
|
|
expect(status.requiredDirectories).toEqual(["manifest-dir"]);
|
|
|
|
|
expect(status.requiredFiles).toEqual(["manifest.md"]);
|
|
|
|
|
expect(status.healthy).toBe(true);
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
it("prepares required directories for a read-write folder without creating required files", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
|
|
|
|
|
await preparePluginLocalFolder({
|
|
|
|
|
folderKey: "content-root",
|
|
|
|
|
storedConfig: {
|
|
|
|
|
path: root,
|
|
|
|
|
access: "readWrite",
|
|
|
|
|
requiredDirectories: ["sources", "wiki/concepts"],
|
|
|
|
|
requiredFiles: ["schema.md"],
|
|
|
|
|
},
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
await expect(fs.stat(path.join(root, "sources"))).resolves.toMatchObject({});
|
|
|
|
|
await expect(fs.stat(path.join(root, "wiki/concepts"))).resolves.toMatchObject({});
|
|
|
|
|
await expect(fs.stat(path.join(root, "schema.md"))).rejects.toMatchObject({ code: "ENOENT" });
|
|
|
|
|
|
|
|
|
|
const status = await inspectPluginLocalFolder({
|
|
|
|
|
folderKey: "content-root",
|
|
|
|
|
storedConfig: {
|
|
|
|
|
path: root,
|
|
|
|
|
access: "readWrite",
|
|
|
|
|
requiredDirectories: ["sources", "wiki/concepts"],
|
|
|
|
|
requiredFiles: ["schema.md"],
|
|
|
|
|
},
|
|
|
|
|
});
|
|
|
|
|
expect(status.missingDirectories).toEqual([]);
|
|
|
|
|
expect(status.missingFiles).toEqual(["schema.md"]);
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
it("allows write access to repair folders that are only missing required paths", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
const status = await inspectPluginLocalFolder({
|
|
|
|
|
folderKey: "content-root",
|
|
|
|
|
storedConfig: {
|
|
|
|
|
path: root,
|
|
|
|
|
access: "readWrite",
|
|
|
|
|
requiredFiles: ["schema.md"],
|
|
|
|
|
},
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
expect(status.healthy).toBe(false);
|
|
|
|
|
expect(() => assertConfiguredLocalFolder(status)).toThrow("Local folder is not healthy");
|
|
|
|
|
expect(() => assertWritableConfiguredLocalFolder(status)).not.toThrow();
|
|
|
|
|
|
|
|
|
|
await writePluginLocalFolderTextAtomic(root, "schema.md", "schema");
|
|
|
|
|
const repaired = await inspectPluginLocalFolder({
|
|
|
|
|
folderKey: "content-root",
|
|
|
|
|
storedConfig: {
|
|
|
|
|
path: root,
|
|
|
|
|
access: "readWrite",
|
|
|
|
|
requiredFiles: ["schema.md"],
|
|
|
|
|
},
|
|
|
|
|
});
|
|
|
|
|
expect(repaired.healthy).toBe(true);
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
it("rejects traversal outside the configured folder", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
|
|
|
|
|
await expect(resolvePluginLocalFolderPath(root, "../outside.txt")).rejects.toMatchObject({
|
|
|
|
|
status: 403,
|
|
|
|
|
});
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
it("detects required symlinks that escape the configured folder", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
const outside = await makeRoot();
|
|
|
|
|
await fs.writeFile(path.join(outside, "secret.txt"), "nope", "utf8");
|
|
|
|
|
await fs.symlink(path.join(outside, "secret.txt"), path.join(root, "linked.txt"));
|
|
|
|
|
|
|
|
|
|
const status = await inspectPluginLocalFolder({
|
|
|
|
|
folderKey: "content-root",
|
|
|
|
|
storedConfig: {
|
|
|
|
|
path: root,
|
|
|
|
|
requiredFiles: ["linked.txt"],
|
|
|
|
|
},
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
expect(status.healthy).toBe(false);
|
|
|
|
|
expect(status.problems.some((item) => item.code === "symlink_escape")).toBe(true);
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
it("writes files atomically under the root and can read them back", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
await fs.mkdir(path.join(root, "nested"));
|
|
|
|
|
|
|
|
|
|
await writePluginLocalFolderTextAtomic(root, "nested/page.md", "hello");
|
|
|
|
|
await writePluginLocalFolderTextAtomic(root, "nested/page.md", "updated");
|
|
|
|
|
|
|
|
|
|
await expect(readPluginLocalFolderText(root, "nested/page.md")).resolves.toBe("updated");
|
|
|
|
|
const leftovers = await fs.readdir(path.join(root, "nested"));
|
|
|
|
|
expect(leftovers.filter((name) => name.includes(".paperclip-"))).toEqual([]);
|
|
|
|
|
});
|
|
|
|
|
|
[codex] Roll up May 17 branch changes (#6210)
## Thinking Path
> - Paperclip is the control plane for autonomous AI companies, so agent
work needs visible ownership, recovery, and operator controls.
> - This local branch had accumulated several related control-plane
reliability and operator-experience fixes across recovery actions,
watchdog folding, model-profile defaults, mentions, markdown editing,
plugin launchers, and small UI polish.
> - The branch needed to be converted into a PR against the current
`origin/master` without losing dirty work or including lockfile/workflow
churn.
> - The safest standalone shape is a single rollup PR because the
recovery/server/UI files overlap heavily across the local commits and
splitting would create avoidable conflicts.
> - This pull request replays the local branch onto latest
`origin/master`, preserves the uncommitted work as logical commits, and
adds a Zod 4 validator compatibility fix found during verification.
> - The benefit is that the May 17 local branch can be reviewed and
merged as one coherent, conflict-free branch under the 100-file Greptile
limit.
## What Changed
- Rebased the local May 17 branch work onto current `origin/master` in a
dedicated worktree.
- Preserved and committed previously dirty changes for recovery retry
handling, plugin/sidebar launcher polish, and `.herenow` ignores.
- Added recovery-action behavior for returning source issues to `todo`
when retrying source-scoped recovery.
- Included the existing local recovery/liveness/watchdog fold, Codex
cheap-profile, markdown/mention, duplicate-agent, and UI polish commits
from the branch.
- Normalized shared validator `z.record(...)` schemas to explicit
string-key records for Zod 4 compatibility.
- Confirmed the PR has no `pnpm-lock.yaml` or `.github/workflows/*`
changes and stays below the 100-file Greptile limit.
## Verification
- `pnpm install --frozen-lockfile --ignore-scripts`
- `npm run install` in
`node_modules/.pnpm/sqlite3@5.1.7/node_modules/sqlite3` to build the
local native sqlite3 binding after installing with scripts disabled
- `pnpm exec vitest run packages/shared/src/validators/issue.test.ts
packages/shared/src/project-mentions.test.ts
packages/adapter-utils/src/server-utils.test.ts
server/src/__tests__/heartbeat-model-profile.test.ts
server/src/__tests__/issue-recovery-actions.test.ts
server/src/__tests__/issue-agent-mutation-ownership-routes.test.ts
server/src/__tests__/heartbeat-active-run-output-watchdog.test.ts
server/src/__tests__/plugin-local-folders.test.ts
ui/src/components/IssueRecoveryActionCard.test.tsx
ui/src/components/Sidebar.test.tsx
ui/src/components/SidebarAccountMenu.test.tsx
ui/src/components/IssueProperties.test.tsx
ui/src/components/MarkdownEditor.test.tsx
ui/src/components/MarkdownBody.test.tsx
ui/src/lib/duplicate-agent-payload.test.ts
ui/src/pages/Routines.test.tsx`
- First pass: 13 files passed with 201 passing tests; 3 server files
failed before sqlite3 native binding was built.
- After rebuilding sqlite3:
`server/src/__tests__/heartbeat-model-profile.test.ts`,
`server/src/__tests__/issue-recovery-actions.test.ts`, and
`server/src/__tests__/heartbeat-active-run-output-watchdog.test.ts`
passed/loaded; embedded Postgres tests were skipped by the local host
guard.
- `pnpm --filter @paperclipai/shared typecheck`
- `pnpm --filter @paperclipai/adapter-utils typecheck`
- `pnpm --filter @paperclipai/server typecheck`
- `pnpm --filter @paperclipai/ui typecheck`
## Risks
- Medium risk: this is a broad rollup PR across recovery semantics,
server tests, shared validators, and UI surfaces.
- Some embedded Postgres tests skipped locally due the host guard, so CI
should provide the stronger database-backed signal.
- UI changes were covered by component tests, but no browser screenshot
was captured in this PR creation pass.
- This branch may overlap with existing recovery/liveness PR work; merge
this PR independently or restack/close overlapping branches rather than
merging duplicate implementations together.
> 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, tool-enabled local repository
and GitHub workflow, medium reasoning effort.
## 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
---------
Co-authored-by: Paperclip <noreply@paperclip.ing>
2026-05-17 17:15:06 -05:00
|
|
|
it("creates missing nested parent directories for atomic writes", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
|
|
|
|
|
await writePluginLocalFolderTextAtomic(root, "cases/active/smoke/README.md", "hello");
|
|
|
|
|
|
|
|
|
|
await expect(readPluginLocalFolderText(root, "cases/active/smoke/README.md")).resolves.toBe("hello");
|
|
|
|
|
});
|
|
|
|
|
|
[codex] Add LLM Wiki plugin host support (#5597)
## Thinking Path
> - Paperclip orchestrates AI agents for zero-human companies.
> - The plugin system needs host contracts and runtime support before
large plugins can integrate cleanly.
> - The source branch mixed the LLM Wiki package with supporting
host/runtime work, managed plugin skills, root-level storage spaces, and
a bookmarks reference plugin.
> - [PAP-9173](/PAP/issues/PAP-9173) asked for the current branch to be
split by file boundary: plugin package separately from everything else.
> - [PAP-9188](/PAP/issues/PAP-9188) clarified that LLM Wiki may have
plugin-local spaces, but Paperclip core should not reorganize top-level
local storage into spaces.
> - Follow-up review clarified that the bookmarks example should not
ship in this PR either.
> - This pull request contains the
non-`packages/plugins/plugin-llm-wiki/` host/runtime work, keeps runtime
state under the selected Paperclip instance root, and no longer includes
the bookmarks example.
## What Changed
- Added/updated plugin host contracts, SDK types, worker RPC plumbing,
managed plugin skill support, and related server tests.
- Removed the bookmarks example plugin package and its
bundled-example/workspace references.
- Removed the root-level local spaces CLI/migration surface and restored
instance-root runtime defaults for config, db, logs, storage, secrets,
workspaces, projects, and adapter homes.
- Replaced shared root `space-paths` helpers with `home-paths` helpers
for core runtime storage.
- Tightened stranded recovery unique-conflict detection so concurrent
recovery scans reuse the raced recovery issue when Postgres errors are
wrapped.
- Kept `packages/plugins/plugin-llm-wiki/` out of this PR diff;
plugin-local spaces remain in the stacked plugin-only PR.
## Verification
- `pnpm exec vitest run cli/src/__tests__/data-dir.test.ts
cli/src/__tests__/home-paths.test.ts cli/src/__tests__/onboard.test.ts
packages/shared/src/home-paths.test.ts
packages/db/src/runtime-config.test.ts
server/src/__tests__/agent-instructions-service.test.ts
server/src/__tests__/claude-local-execute.test.ts
server/src/__tests__/codex-local-execute.test.ts`
- `pnpm exec vitest run packages/db/src/runtime-config.test.ts`
- `pnpm exec vitest run
server/src/__tests__/plugin-routes-authz.test.ts`
- `pnpm --filter @paperclipai/server typecheck`
- `pnpm exec vitest run
server/src/__tests__/heartbeat-process-recovery.test.ts -t "reuses the
raced stranded recovery issue"` skipped locally because embedded
Postgres did not initialize on this macOS temp host; the code path was
typechecked and is covered by Linux CI.
- Boundary check: no core references remain for `PAPERCLIP_SPACE_ID`,
`spaces migrate-default`, `@paperclipai/shared/space-paths`,
`registerSpacesCommands`, or the removed bookmarks example.
- Previous PR head `4f23e034` had green GitHub checks: `verify`, all
four serialized server shards, `e2e`, `Canary Dry Run`, `policy`, Snyk,
and `Greptile Review`. Current head `582f466d` is re-running checks
after the bookmarks deletion.
## Risks
- Plugin host changes touch shared runtime paths, so regressions would
most likely appear in adapter startup, plugin loading, or local dev path
defaults.
- Removing the bookmarks example also removes one demonstration of
plugin database namespaces plus local-folder persistence; remaining
plugin examples still cover bundled example discovery and plugin host
flows.
- The plugin package itself is intentionally deferred to the stacked
plugin-only PR, where LLM Wiki plugin-local spaces live.
- Existing installs that tested the transient root-level spaces CLI
should stop using it; this PR intentionally removes that unsupported
migration surface before merge.
> 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 Codex via Codex CLI, tool use and local code execution
enabled; context window 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 run tests locally and they pass, except where noted above
for host-specific embedded Postgres initialization
- [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
Stacked follow-up: PR #5592 contains only
`packages/plugins/plugin-llm-wiki/` and targets this branch.
---------
Co-authored-by: Paperclip <noreply@paperclip.ing>
2026-05-10 07:34:12 -05:00
|
|
|
it("returns the real folder key after deleting a file", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
await fs.writeFile(path.join(root, "stale.md"), "delete me", "utf8");
|
|
|
|
|
|
|
|
|
|
const status = await deletePluginLocalFolderFile(root, "stale.md", "content-root");
|
|
|
|
|
|
|
|
|
|
expect(status.folderKey).toBe("content-root");
|
|
|
|
|
await expect(fs.stat(path.join(root, "stale.md"))).rejects.toMatchObject({ code: "ENOENT" });
|
|
|
|
|
});
|
|
|
|
|
|
Expand plugin host surface (#5205)
## 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>
2026-05-05 07:42:57 -05:00
|
|
|
it("lists nested local folder entries without following symlink escapes", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
const outside = await makeRoot();
|
|
|
|
|
await fs.mkdir(path.join(root, "wiki/concepts"), { recursive: true });
|
|
|
|
|
await fs.writeFile(path.join(root, "wiki/concepts/live.md"), "# Live\n", "utf8");
|
|
|
|
|
await fs.writeFile(path.join(outside, "secret.md"), "# Secret\n", "utf8");
|
|
|
|
|
await fs.symlink(outside, path.join(root, "wiki/outside"));
|
|
|
|
|
|
|
|
|
|
const listing = await listPluginLocalFolderEntries(root, {
|
|
|
|
|
relativePath: "wiki",
|
|
|
|
|
recursive: true,
|
|
|
|
|
maxEntries: 20,
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
expect(listing.entries.map((entry) => entry.path)).toContain("wiki/concepts/live.md");
|
|
|
|
|
expect(listing.entries.map((entry) => entry.path)).not.toContain("wiki/outside/secret.md");
|
|
|
|
|
expect(listing.truncated).toBe(false);
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
it("revalidates temp-file containment before writing atomic contents", async () => {
|
|
|
|
|
const root = await makeRoot();
|
|
|
|
|
const outside = await makeRoot();
|
|
|
|
|
const nested = path.join(root, "nested");
|
|
|
|
|
await fs.mkdir(nested);
|
|
|
|
|
const originalOpen = fs.open.bind(fs);
|
|
|
|
|
const openSpy = vi.spyOn(fs, "open");
|
|
|
|
|
openSpy.mockImplementationOnce(async (file, flags, mode) => {
|
|
|
|
|
await fs.rm(nested, { recursive: true, force: true });
|
|
|
|
|
await fs.symlink(outside, nested);
|
|
|
|
|
return originalOpen(file, flags, mode);
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
try {
|
|
|
|
|
await expect(writePluginLocalFolderTextAtomic(root, "nested/page.md", "secret")).rejects.toMatchObject({
|
|
|
|
|
status: 403,
|
|
|
|
|
});
|
|
|
|
|
await expect(fs.readFile(path.join(outside, "page.md"), "utf8")).rejects.toMatchObject({ code: "ENOENT" });
|
|
|
|
|
expect(await fs.readdir(outside)).toEqual([]);
|
|
|
|
|
} finally {
|
|
|
|
|
openSpy.mockRestore();
|
|
|
|
|
}
|
|
|
|
|
});
|
|
|
|
|
});
|