2026-02-18 13:53:03 -06:00
|
|
|
import type { UIAdapterModule } from "./types";
|
Add ACPX local adapter runtime (#4893)
## Thinking Path
> - Paperclip orchestrates AI-agent companies through a control plane
that can start, supervise, and recover agent runs.
> - Local adapters are the bridge between Paperclip issues and concrete
agent runtimes such as Claude, Codex, and other ACP-compatible tools.
> - The roadmap calls out broader “bring your own agent” and claw-style
agent support, and ACPX gives Paperclip one path to normalize multiple
ACP agents behind a single adapter.
> - The branch needed to become one reviewable PR against current
`paperclipai/paperclip:master`, without carrying stale base conflicts or
generated lockfile churn.
> - This pull request adds an experimental built-in `acpx_local`
adapter, integrates it through the server/CLI/UI adapter surfaces, and
adds regression coverage for runtime execution, skill sync, stream
parsing, diagnostics, and log redaction.
> - The benefit is that Paperclip can run Claude/Codex/custom ACP agents
through ACPX while keeping operator configuration, skills, logging, and
transcript rendering inside the existing adapter model.
## What Changed
- Added `@paperclipai/adapter-acpx-local` with server execution, config
schema, ACPX session handling, CLI formatting, UI config helpers, and
stdout parsing.
- Registered `acpx_local` across CLI, server, shared constants, UI
adapter metadata, adapter capabilities, and agent creation/editing
surfaces.
- Added ACPX runtime execution support with persistent sessions,
local-agent JWT environment handling, skill snapshots, runtime skill
materialization, and isolation/security regressions.
- Added ACPX adapter diagnostics and marked the adapter experimental in
the UI.
- Added command/env secret redaction for resolved command metadata in
adapter-utils, server event storage, and the Agent Detail invocation UI.
- Added Storybook coverage for ACPX config, transcript rendering, and
skill states, plus PR screenshots under `docs/pr-screenshots/pap-2944/`.
- Rebased the branch onto current `public-gh/master`; `pnpm-lock.yaml`
is intentionally not included and there are no migration/schema changes.
## Verification
- `pnpm exec vitest run
packages/adapters/acpx-local/src/server/execute.test.ts
packages/adapters/acpx-local/src/server/test.test.ts
packages/adapters/acpx-local/src/cli/format-event.test.ts
packages/adapters/acpx-local/src/ui/parse-stdout.test.ts
packages/adapter-utils/src/server-utils.test.ts
server/src/__tests__/redaction.test.ts
server/src/__tests__/acpx-local-execute.test.ts
server/src/__tests__/acpx-local-skill-sync.test.ts
server/src/__tests__/acpx-local-adapter-environment.test.ts
server/src/__tests__/adapter-routes.test.ts
server/src/__tests__/agent-skills-routes.test.ts
ui/src/adapters/metadata.test.ts` — 12 files, 87 tests passed.
- `pnpm --filter @paperclipai/adapter-acpx-local typecheck` — passed.
- `pnpm --filter @paperclipai/server typecheck` — passed.
- `pnpm --filter @paperclipai/ui typecheck` — passed.
- Confirmed PR diff does not include `pnpm-lock.yaml`, database schema
files, or migrations.
Screenshots:



## Risks
- Medium risk: this introduces a new built-in adapter package and
touches runtime execution, adapter registration, agent config, skills,
and transcript rendering.
- ACPX and ACP agent behavior can vary by installed tool versions; the
adapter is marked experimental to set operator expectations.
- `pnpm-lock.yaml` is excluded per repository PR policy, so dependency
lock refresh must be handled by the repo’s automation or maintainers.
- No database migration risk: no schema or migration files changed.
> 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 coding agent based on GPT-5, with repository tool use,
shell execution, git operations, and local verification. Exact hosted
context window was not exposed in this environment.
## 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-04-30 19:57:05 -05:00
|
|
|
import { acpxLocalUIAdapter } from "./acpx-local";
|
2026-02-18 13:53:03 -06:00
|
|
|
import { claudeLocalUIAdapter } from "./claude-local";
|
|
|
|
|
import { codexLocalUIAdapter } from "./codex-local";
|
Add cursor_cloud adapter for Cursor SDK + Cloud Agents API v1 (#5664)
## Thinking Path
> - Paperclip orchestrates AI agents for zero-human companies
> - There are many adapter types, one per agent-runtime product (Claude,
Codex, OpenCode, Cursor local CLI, etc.)
> - Cursor shipped a public TypeScript SDK on 2026-04-29 that exposes
Cursor's full hosted-agent platform (cloud VMs, harness, MCP, skills,
hooks)
> - Paperclip had no first-class adapter for this — agents that wanted
to use Cursor's managed cloud runtime had to fall back to the local CLI
adapter, which loses the cloud session, streaming, and durable run model
> - This PR adds a new `cursor_cloud` adapter built directly on
`@cursor/sdk`, with Paperclip's heartbeat mapped to Cursor's
durable-agent + per-run model
> - The benefit is that any Paperclip agent can now drive a Cursor cloud
agent across heartbeats with native session reuse, streaming, and
cancellation, while Paperclip remains the source of truth for issue/task
state
## What Changed
- New built-in adapter package `packages/adapters/cursor-cloud` (15
files, ~1.7k LOC) backed by `@cursor/sdk` ^1.0.12
- `src/server/execute.ts` — SDK-first lifecycle: `Agent.create` /
`Agent.resume` / `Agent.getRun` / `agent.send` / `run.stream` /
`run.wait`, with session reuse keyed on the (runtime env type, env name,
repo set) tuple
- `src/server/session.ts` — codec for `cursorAgentId` + `latestRunId` +
repo metadata, persisted in `runtime.sessionParams`
- `src/server/test.ts` — environment probe via `Cursor.me()` and
optional model validation via `Cursor.models.list()`
- `src/ui/parse-stdout.ts` + `src/cli/format-event.ts` — normalize
Cursor SDK message types (`status`, `thinking`, `assistant`, `user`,
`tool_call`, `tool_result`, `result`) into Paperclip transcript events
for the UI and CLI
- Registrations: `packages/shared/src/constants.ts`,
`packages/adapter-utils/src/session-compaction.ts`,
`server/src/adapters/{registry,builtin-adapter-types}.ts`,
`ui/src/adapters/{registry,adapter-display-registry}.ts` +
`ui/src/adapters/cursor-cloud/index.ts`, `cli/src/adapters/registry.ts`,
plus workspace deps in `cli`/`server`/`ui` `package.json`
- `ui/src/components/AgentConfigForm.tsx` — hide local-Cursor
`mode`/thinking-effort field for `cursor_cloud` (different config
surface)
- 11 vitest tests covering execute paths (fresh create, matching-resume,
active-run reattach, non-finished result), session codec round-trip,
transcript parsing, and config building
## Verification
Reviewer steps:
```bash
pnpm install
pnpm --filter @paperclipai/adapter-cursor-cloud typecheck # → clean
pnpm vitest run packages/adapters/cursor-cloud # → 11/11 passing
```
End-to-end check against a real Cursor cloud agent (requires
`CURSOR_API_KEY` and Cursor GitHub-app install on the target repo):
1. Create a `cursor_cloud` agent in Paperclip with `repoUrl` set to the
test repo, `repoStartingRef: main`, and `env.CURSOR_API_KEY` set
2. Trigger a heartbeat → adapter calls `Agent.create({ cloud: { env: {
type: "cloud" }, repos: [...] } })`, streams events, terminates on
`finished`
3. Trigger a second heartbeat → adapter calls `Agent.resume` or
`agent.send` follow-up depending on prior-run state, reusing
`cursorAgentId`
4. The Paperclip UI/CLI transcript reflects Cursor `status` / `thinking`
/ `assistant` events as they stream
5. Cancellation from Paperclip maps to `run.cancel()` or Cloud API v1
`cancelRun` for cross-heartbeat cancellation
A direct-SDK smoke run against a real repo (devinfoley/my_test_project @
main) confirmed: `Cursor.me()` ok → `Agent.create` → `agent.send` →
`run.stream()` (30 events) → terminal status `finished` in ~11s.
## Risks
- **New adapter, additive only.** No existing adapter or registry is
replaced; current `cursor` local-CLI adapter is untouched. Default
behavior of any existing agent is unchanged.
- **External dependency on `@cursor/sdk`.** Cursor's SDK is v1.0.x and
may evolve. Mocked unit tests cover the public surface used here; if the
SDK breaks compatibility we update the adapter independently.
- **Cost/budget.** `cursor_cloud` runs on Cursor's billed cloud VMs;
operators must understand they are spending money outside Paperclip's
budget controls when they enable this adapter. Same shape as other
API-billed adapters.
- **No webhook support in V1.** The SDK already provides
stream/wait/cancel/reattach, so V1 does not require a public callback
URL. If a future use case needs out-of-band wakes, we add a Cloud API v1
webhook bridge as a separate change. This is called out in the issue
plan document.
- **Lockfile.** Per repo policy, `pnpm-lock.yaml` is intentionally not
in this PR — CI's lockfile workflow will update it on merge given the
manifest changes.
## Model Used
- Provider: Anthropic Claude (via Claude Code / Paperclip `claude_local`
adapter)
- Model: `claude-opus-4-7` (Claude Opus 4.7), knowledge cutoff January
2026
- Mode: standard tool-use with extended reasoning
- Context: ~200k token window
- Capabilities used: code generation, multi-file edits, shell/test
execution, GitHub PR workflow
## 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 (11/11 in
`packages/adapters/cursor-cloud`)
- [x] I have added or updated tests where applicable (4 new test files,
11 cases)
- [ ] If this change affects the UI, I have included before/after
screenshots (the only UI change is hiding the local-Cursor mode field on
the `cursor_cloud` adapter — happy to attach a screenshot if the
reviewer wants one)
- [x] I have updated relevant documentation to reflect my changes (issue
plan document supersedes the pre-SDK design; tracked in PAPA-203)
- [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-10 17:21:04 -07:00
|
|
|
import { cursorCloudUIAdapter } from "./cursor-cloud";
|
2026-03-05 06:31:22 -06:00
|
|
|
import { cursorLocalUIAdapter } from "./cursor";
|
2026-03-08 16:43:34 +05:30
|
|
|
import { geminiLocalUIAdapter } from "./gemini-local";
|
Add built-in grok_local adapter (#6087)
## Thinking Path
> - Paperclip orchestrates AI agents for zero-human companies, so
adapter quality directly affects what runtimes the control plane can
supervise.
> - Local CLI adapters are one of the core execution surfaces because
they turn real coding tools into Paperclip-managed employees with
heartbeats, transcripts, and reviewability.
> - Grok Build was installed on the Paperclip host, but Paperclip had no
built-in `grok_local` adapter, so the runtime could not be configured
through the normal server/UI/CLI adapter path.
> - That gap needed to be closed with the same built-in registry,
environment diagnostics, transcript parsing, and skill/instructions
behavior that the other local adapters already rely on.
> - After the initial adapter landed, a real follow-up run showed that
Grok streaming text was being rendered one fragment per line, which made
transcripts harder to read even though the runtime itself was working.
> - This pull request adds the built-in `grok_local` adapter end-to-end
and then fixes the transcript parser so streamed Grok output is
coalesced into readable assistant/thinking blocks.
> - The benefit is that Grok Build becomes a first-class Paperclip
runtime with a usable operator experience instead of a partially wired
runtime with noisy transcript output.
## What Changed
- Added a new built-in `@paperclipai/adapter-grok-local` package with
server, UI, and CLI entrypoints.
- Implemented Grok execution, session handling, environment diagnostics,
config building, skill syncing, and parser coverage inside the new
adapter package.
- Registered `grok_local` across the built-in adapter inventories and
capability/display metadata in server, UI, CLI, and shared constants.
- Added adapter route coverage for the new built-in type.
- Fixed Grok transcript readability by emitting streamed `text` and
`thought` fragments as deltas so the shared transcript builder coalesces
them into readable message blocks.
- Added regression tests for the Grok parser and transcript coalescing
behavior.
## Verification
- `pnpm vitest run
packages/adapters/grok-local/src/ui/parse-stdout.test.ts
ui/src/adapters/transcript.test.ts`
- `pnpm --filter @paperclipai/adapter-grok-local build`
- Manual runtime verification on the Paperclip host during
implementation and follow-up review:
- confirmed the Grok CLI was installed and authenticated
- confirmed the worktree dev server could be restarted cleanly and
health-checked after the parser follow-up
- No screenshots attached. This change is primarily adapter plumbing
plus transcript formatting behavior; reviewers can verify via the
Grok-backed run surfaces directly.
## Risks
- This adds a new built-in adapter, so any missed registration surface
could create inconsistencies between server, UI, and CLI behavior.
- The adapter depends on Grok Build's current event/output shape; if
upstream Grok streaming JSON changes, transcript parsing or session
extraction may need follow-up updates.
- The transcript readability fix intentionally changes how Grok
fragments are grouped, so any downstream code that implicitly expected
one entry per fragment would behave differently.
> 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 via Paperclip `codex_local` agent runtime.
- GPT-5-class coding model with tool use, shell execution, file editing,
and repo inspection enabled.
- Exact backend model ID/context window were not surfaced to the agent
in this Paperclip session.
## 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
- [ ] 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
2026-05-16 09:51:09 -07:00
|
|
|
import { grokLocalUIAdapter } from "./grok-local";
|
2026-03-04 16:48:54 -06:00
|
|
|
import { openCodeLocalUIAdapter } from "./opencode-local";
|
2026-03-06 18:29:38 -08:00
|
|
|
import { piLocalUIAdapter } from "./pi-local";
|
2026-03-07 08:59:29 -06:00
|
|
|
import { openClawGatewayUIAdapter } from "./openclaw-gateway";
|
2026-03-31 21:38:37 +01:00
|
|
|
import { hermesLocalUIAdapter } from "./hermes-local";
|
2026-02-18 13:53:03 -06:00
|
|
|
import { processUIAdapter } from "./process";
|
|
|
|
|
import { httpUIAdapter } from "./http";
|
[codex] Sandbox dynamic adapter UI parsers (#4225)
## Thinking Path
> - Paperclip is a control plane for AI-agent companies.
> - External adapters can provide UI parser code that the board loads
dynamically for run transcript rendering.
> - Running adapter-provided parser code directly in the board page
gives that parser access to same-origin browser state.
> - This PR narrows that surface by evaluating dynamically loaded
external adapter UI parser code in a dedicated browser Web Worker with a
constrained postMessage protocol.
> - The worker here is a frontend isolation boundary for adapter UI
parser JavaScript; it is not Paperclip's server plugin-worker system and
it is not a server-side job runner.
## What Changed
- Runs dynamically loaded external adapter UI parsers inside a dedicated
Web Worker instead of importing/evaluating them directly in the board
page.
- Adds a narrow postMessage protocol for parser initialization and line
parsing.
- Caches completed async parse results and notifies the adapter registry
so transcript recomputation can synchronously drain the final parsed
line.
- Disables common worker network, persistence, child worker, Blob/object
URL, and WebRTC escape APIs inside the parser worker bootstrap.
- Handles worker error messages after initialization and drains pending
callbacks on worker termination or mid-session worker error.
- Adds focused regression coverage for the parser worker lockdown and
unused protocol removal.
## Verification
- `pnpm exec vitest run --config ui/vitest.config.ts
ui/src/adapters/sandboxed-parser-worker.test.ts`
- `pnpm exec tsc --noEmit --target es2021 --moduleResolution bundler
--module esnext --jsx react-jsx --lib dom,es2021 --skipLibCheck
ui/src/adapters/dynamic-loader.ts
ui/src/adapters/sandboxed-parser-worker.ts
ui/src/adapters/sandboxed-parser-worker.test.ts`
- `pnpm --filter @paperclipai/ui typecheck` was attempted; it reached
existing unrelated failures in HeartbeatRun test/storybook fixtures and
missing Storybook type resolution, with no adapter-module errors
surfaced.
- PR #4225 checks on current head `34c9da00`: `policy`, `e2e`, `verify`,
`security/snyk`, and `Greptile Review` are all `SUCCESS`.
- Greptile Review on current head `34c9da00` reached 5/5.
## Risks
- Medium risk: parser execution is now asynchronous through a worker
while the existing parser interface is synchronous, so transcript
updates should be watched with external adapters.
- Some adapter parser bundles may rely on direct ESM `export` syntax or
browser APIs that are no longer available inside the worker lockdown.
- The worker lockdown is a hardening layer around external parser code,
not a complete browser security sandbox for arbitrary untrusted
applications.
> 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 runtime, shell/git tool use
enabled. Exact hosted model build and context window are not exposed in
this Paperclip heartbeat environment.
## 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
2026-04-21 13:42:44 -05:00
|
|
|
import { loadDynamicParser, invalidateDynamicParser, setDynamicParserResultNotifier } from "./dynamic-loader";
|
2026-04-01 13:58:02 +01:00
|
|
|
import { SchemaConfigFields, buildSchemaAdapterConfig } from "./schema-config-fields";
|
2026-02-18 13:53:03 -06:00
|
|
|
|
2026-03-31 20:21:13 +01:00
|
|
|
const uiAdapters: UIAdapterModule[] = [];
|
|
|
|
|
const adaptersByType = new Map<string, UIAdapterModule>();
|
|
|
|
|
|
2026-04-04 12:40:39 +01:00
|
|
|
// Types registered at module load time — allowed to be overridden by
|
|
|
|
|
// external adapters that ship their own ui-parser.js via the server.
|
|
|
|
|
const builtinTypes = new Set<string>();
|
|
|
|
|
|
|
|
|
|
// Original builtin adapters stored for restoration when external overrides
|
|
|
|
|
// are deactivated or removed.
|
|
|
|
|
const builtinAdaptersByType = new Map<string, UIAdapterModule>();
|
|
|
|
|
|
|
|
|
|
// Tracks which builtin types currently have an active external override.
|
|
|
|
|
const activeExternalOverrides = new Set<string>();
|
|
|
|
|
|
|
|
|
|
// Generation counter to discard stale dynamic parser loads. When an override
|
|
|
|
|
// is deactivated while a load is in-flight, the generation is bumped and the
|
|
|
|
|
// stale result is discarded in its .then() handler.
|
|
|
|
|
const overrideGeneration = new Map<string, number>();
|
|
|
|
|
|
2026-04-01 21:56:19 +01:00
|
|
|
// Subscriber list — components can register to be notified when adapters change
|
|
|
|
|
// (e.g., when a dynamic parser replaces a placeholder).
|
|
|
|
|
const adapterChangeListeners = new Set<() => void>();
|
|
|
|
|
|
|
|
|
|
/** Subscribe to adapter registry changes. Returns unsubscribe function. */
|
|
|
|
|
export function onAdapterChange(fn: () => void): () => void {
|
|
|
|
|
adapterChangeListeners.add(fn);
|
|
|
|
|
return () => adapterChangeListeners.delete(fn);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
function notifyAdapterChange(): void {
|
|
|
|
|
for (const fn of adapterChangeListeners) fn();
|
|
|
|
|
}
|
|
|
|
|
|
[codex] Sandbox dynamic adapter UI parsers (#4225)
## Thinking Path
> - Paperclip is a control plane for AI-agent companies.
> - External adapters can provide UI parser code that the board loads
dynamically for run transcript rendering.
> - Running adapter-provided parser code directly in the board page
gives that parser access to same-origin browser state.
> - This PR narrows that surface by evaluating dynamically loaded
external adapter UI parser code in a dedicated browser Web Worker with a
constrained postMessage protocol.
> - The worker here is a frontend isolation boundary for adapter UI
parser JavaScript; it is not Paperclip's server plugin-worker system and
it is not a server-side job runner.
## What Changed
- Runs dynamically loaded external adapter UI parsers inside a dedicated
Web Worker instead of importing/evaluating them directly in the board
page.
- Adds a narrow postMessage protocol for parser initialization and line
parsing.
- Caches completed async parse results and notifies the adapter registry
so transcript recomputation can synchronously drain the final parsed
line.
- Disables common worker network, persistence, child worker, Blob/object
URL, and WebRTC escape APIs inside the parser worker bootstrap.
- Handles worker error messages after initialization and drains pending
callbacks on worker termination or mid-session worker error.
- Adds focused regression coverage for the parser worker lockdown and
unused protocol removal.
## Verification
- `pnpm exec vitest run --config ui/vitest.config.ts
ui/src/adapters/sandboxed-parser-worker.test.ts`
- `pnpm exec tsc --noEmit --target es2021 --moduleResolution bundler
--module esnext --jsx react-jsx --lib dom,es2021 --skipLibCheck
ui/src/adapters/dynamic-loader.ts
ui/src/adapters/sandboxed-parser-worker.ts
ui/src/adapters/sandboxed-parser-worker.test.ts`
- `pnpm --filter @paperclipai/ui typecheck` was attempted; it reached
existing unrelated failures in HeartbeatRun test/storybook fixtures and
missing Storybook type resolution, with no adapter-module errors
surfaced.
- PR #4225 checks on current head `34c9da00`: `policy`, `e2e`, `verify`,
`security/snyk`, and `Greptile Review` are all `SUCCESS`.
- Greptile Review on current head `34c9da00` reached 5/5.
## Risks
- Medium risk: parser execution is now asynchronous through a worker
while the existing parser interface is synchronous, so transcript
updates should be watched with external adapters.
- Some adapter parser bundles may rely on direct ESM `export` syntax or
browser APIs that are no longer available inside the worker lockdown.
- The worker lockdown is a hardening layer around external parser code,
not a complete browser security sandbox for arbitrary untrusted
applications.
> 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 runtime, shell/git tool use
enabled. Exact hosted model build and context window are not exposed in
this Paperclip heartbeat environment.
## 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
2026-04-21 13:42:44 -05:00
|
|
|
setDynamicParserResultNotifier(notifyAdapterChange);
|
|
|
|
|
|
2026-03-31 20:21:13 +01:00
|
|
|
function registerBuiltInUIAdapters() {
|
|
|
|
|
for (const adapter of [
|
Add ACPX local adapter runtime (#4893)
## Thinking Path
> - Paperclip orchestrates AI-agent companies through a control plane
that can start, supervise, and recover agent runs.
> - Local adapters are the bridge between Paperclip issues and concrete
agent runtimes such as Claude, Codex, and other ACP-compatible tools.
> - The roadmap calls out broader “bring your own agent” and claw-style
agent support, and ACPX gives Paperclip one path to normalize multiple
ACP agents behind a single adapter.
> - The branch needed to become one reviewable PR against current
`paperclipai/paperclip:master`, without carrying stale base conflicts or
generated lockfile churn.
> - This pull request adds an experimental built-in `acpx_local`
adapter, integrates it through the server/CLI/UI adapter surfaces, and
adds regression coverage for runtime execution, skill sync, stream
parsing, diagnostics, and log redaction.
> - The benefit is that Paperclip can run Claude/Codex/custom ACP agents
through ACPX while keeping operator configuration, skills, logging, and
transcript rendering inside the existing adapter model.
## What Changed
- Added `@paperclipai/adapter-acpx-local` with server execution, config
schema, ACPX session handling, CLI formatting, UI config helpers, and
stdout parsing.
- Registered `acpx_local` across CLI, server, shared constants, UI
adapter metadata, adapter capabilities, and agent creation/editing
surfaces.
- Added ACPX runtime execution support with persistent sessions,
local-agent JWT environment handling, skill snapshots, runtime skill
materialization, and isolation/security regressions.
- Added ACPX adapter diagnostics and marked the adapter experimental in
the UI.
- Added command/env secret redaction for resolved command metadata in
adapter-utils, server event storage, and the Agent Detail invocation UI.
- Added Storybook coverage for ACPX config, transcript rendering, and
skill states, plus PR screenshots under `docs/pr-screenshots/pap-2944/`.
- Rebased the branch onto current `public-gh/master`; `pnpm-lock.yaml`
is intentionally not included and there are no migration/schema changes.
## Verification
- `pnpm exec vitest run
packages/adapters/acpx-local/src/server/execute.test.ts
packages/adapters/acpx-local/src/server/test.test.ts
packages/adapters/acpx-local/src/cli/format-event.test.ts
packages/adapters/acpx-local/src/ui/parse-stdout.test.ts
packages/adapter-utils/src/server-utils.test.ts
server/src/__tests__/redaction.test.ts
server/src/__tests__/acpx-local-execute.test.ts
server/src/__tests__/acpx-local-skill-sync.test.ts
server/src/__tests__/acpx-local-adapter-environment.test.ts
server/src/__tests__/adapter-routes.test.ts
server/src/__tests__/agent-skills-routes.test.ts
ui/src/adapters/metadata.test.ts` — 12 files, 87 tests passed.
- `pnpm --filter @paperclipai/adapter-acpx-local typecheck` — passed.
- `pnpm --filter @paperclipai/server typecheck` — passed.
- `pnpm --filter @paperclipai/ui typecheck` — passed.
- Confirmed PR diff does not include `pnpm-lock.yaml`, database schema
files, or migrations.
Screenshots:



## Risks
- Medium risk: this introduces a new built-in adapter package and
touches runtime execution, adapter registration, agent config, skills,
and transcript rendering.
- ACPX and ACP agent behavior can vary by installed tool versions; the
adapter is marked experimental to set operator expectations.
- `pnpm-lock.yaml` is excluded per repository PR policy, so dependency
lock refresh must be handled by the repo’s automation or maintainers.
- No database migration risk: no schema or migration files changed.
> 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 coding agent based on GPT-5, with repository tool use,
shell execution, git operations, and local verification. Exact hosted
context window was not exposed in this environment.
## 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-04-30 19:57:05 -05:00
|
|
|
acpxLocalUIAdapter,
|
2026-03-31 20:21:13 +01:00
|
|
|
claudeLocalUIAdapter,
|
|
|
|
|
codexLocalUIAdapter,
|
Add cursor_cloud adapter for Cursor SDK + Cloud Agents API v1 (#5664)
## Thinking Path
> - Paperclip orchestrates AI agents for zero-human companies
> - There are many adapter types, one per agent-runtime product (Claude,
Codex, OpenCode, Cursor local CLI, etc.)
> - Cursor shipped a public TypeScript SDK on 2026-04-29 that exposes
Cursor's full hosted-agent platform (cloud VMs, harness, MCP, skills,
hooks)
> - Paperclip had no first-class adapter for this — agents that wanted
to use Cursor's managed cloud runtime had to fall back to the local CLI
adapter, which loses the cloud session, streaming, and durable run model
> - This PR adds a new `cursor_cloud` adapter built directly on
`@cursor/sdk`, with Paperclip's heartbeat mapped to Cursor's
durable-agent + per-run model
> - The benefit is that any Paperclip agent can now drive a Cursor cloud
agent across heartbeats with native session reuse, streaming, and
cancellation, while Paperclip remains the source of truth for issue/task
state
## What Changed
- New built-in adapter package `packages/adapters/cursor-cloud` (15
files, ~1.7k LOC) backed by `@cursor/sdk` ^1.0.12
- `src/server/execute.ts` — SDK-first lifecycle: `Agent.create` /
`Agent.resume` / `Agent.getRun` / `agent.send` / `run.stream` /
`run.wait`, with session reuse keyed on the (runtime env type, env name,
repo set) tuple
- `src/server/session.ts` — codec for `cursorAgentId` + `latestRunId` +
repo metadata, persisted in `runtime.sessionParams`
- `src/server/test.ts` — environment probe via `Cursor.me()` and
optional model validation via `Cursor.models.list()`
- `src/ui/parse-stdout.ts` + `src/cli/format-event.ts` — normalize
Cursor SDK message types (`status`, `thinking`, `assistant`, `user`,
`tool_call`, `tool_result`, `result`) into Paperclip transcript events
for the UI and CLI
- Registrations: `packages/shared/src/constants.ts`,
`packages/adapter-utils/src/session-compaction.ts`,
`server/src/adapters/{registry,builtin-adapter-types}.ts`,
`ui/src/adapters/{registry,adapter-display-registry}.ts` +
`ui/src/adapters/cursor-cloud/index.ts`, `cli/src/adapters/registry.ts`,
plus workspace deps in `cli`/`server`/`ui` `package.json`
- `ui/src/components/AgentConfigForm.tsx` — hide local-Cursor
`mode`/thinking-effort field for `cursor_cloud` (different config
surface)
- 11 vitest tests covering execute paths (fresh create, matching-resume,
active-run reattach, non-finished result), session codec round-trip,
transcript parsing, and config building
## Verification
Reviewer steps:
```bash
pnpm install
pnpm --filter @paperclipai/adapter-cursor-cloud typecheck # → clean
pnpm vitest run packages/adapters/cursor-cloud # → 11/11 passing
```
End-to-end check against a real Cursor cloud agent (requires
`CURSOR_API_KEY` and Cursor GitHub-app install on the target repo):
1. Create a `cursor_cloud` agent in Paperclip with `repoUrl` set to the
test repo, `repoStartingRef: main`, and `env.CURSOR_API_KEY` set
2. Trigger a heartbeat → adapter calls `Agent.create({ cloud: { env: {
type: "cloud" }, repos: [...] } })`, streams events, terminates on
`finished`
3. Trigger a second heartbeat → adapter calls `Agent.resume` or
`agent.send` follow-up depending on prior-run state, reusing
`cursorAgentId`
4. The Paperclip UI/CLI transcript reflects Cursor `status` / `thinking`
/ `assistant` events as they stream
5. Cancellation from Paperclip maps to `run.cancel()` or Cloud API v1
`cancelRun` for cross-heartbeat cancellation
A direct-SDK smoke run against a real repo (devinfoley/my_test_project @
main) confirmed: `Cursor.me()` ok → `Agent.create` → `agent.send` →
`run.stream()` (30 events) → terminal status `finished` in ~11s.
## Risks
- **New adapter, additive only.** No existing adapter or registry is
replaced; current `cursor` local-CLI adapter is untouched. Default
behavior of any existing agent is unchanged.
- **External dependency on `@cursor/sdk`.** Cursor's SDK is v1.0.x and
may evolve. Mocked unit tests cover the public surface used here; if the
SDK breaks compatibility we update the adapter independently.
- **Cost/budget.** `cursor_cloud` runs on Cursor's billed cloud VMs;
operators must understand they are spending money outside Paperclip's
budget controls when they enable this adapter. Same shape as other
API-billed adapters.
- **No webhook support in V1.** The SDK already provides
stream/wait/cancel/reattach, so V1 does not require a public callback
URL. If a future use case needs out-of-band wakes, we add a Cloud API v1
webhook bridge as a separate change. This is called out in the issue
plan document.
- **Lockfile.** Per repo policy, `pnpm-lock.yaml` is intentionally not
in this PR — CI's lockfile workflow will update it on merge given the
manifest changes.
## Model Used
- Provider: Anthropic Claude (via Claude Code / Paperclip `claude_local`
adapter)
- Model: `claude-opus-4-7` (Claude Opus 4.7), knowledge cutoff January
2026
- Mode: standard tool-use with extended reasoning
- Context: ~200k token window
- Capabilities used: code generation, multi-file edits, shell/test
execution, GitHub PR workflow
## 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 (11/11 in
`packages/adapters/cursor-cloud`)
- [x] I have added or updated tests where applicable (4 new test files,
11 cases)
- [ ] If this change affects the UI, I have included before/after
screenshots (the only UI change is hiding the local-Cursor mode field on
the `cursor_cloud` adapter — happy to attach a screenshot if the
reviewer wants one)
- [x] I have updated relevant documentation to reflect my changes (issue
plan document supersedes the pre-SDK design; tracked in PAPA-203)
- [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-10 17:21:04 -07:00
|
|
|
cursorCloudUIAdapter,
|
2026-03-31 20:21:13 +01:00
|
|
|
geminiLocalUIAdapter,
|
Add built-in grok_local adapter (#6087)
## Thinking Path
> - Paperclip orchestrates AI agents for zero-human companies, so
adapter quality directly affects what runtimes the control plane can
supervise.
> - Local CLI adapters are one of the core execution surfaces because
they turn real coding tools into Paperclip-managed employees with
heartbeats, transcripts, and reviewability.
> - Grok Build was installed on the Paperclip host, but Paperclip had no
built-in `grok_local` adapter, so the runtime could not be configured
through the normal server/UI/CLI adapter path.
> - That gap needed to be closed with the same built-in registry,
environment diagnostics, transcript parsing, and skill/instructions
behavior that the other local adapters already rely on.
> - After the initial adapter landed, a real follow-up run showed that
Grok streaming text was being rendered one fragment per line, which made
transcripts harder to read even though the runtime itself was working.
> - This pull request adds the built-in `grok_local` adapter end-to-end
and then fixes the transcript parser so streamed Grok output is
coalesced into readable assistant/thinking blocks.
> - The benefit is that Grok Build becomes a first-class Paperclip
runtime with a usable operator experience instead of a partially wired
runtime with noisy transcript output.
## What Changed
- Added a new built-in `@paperclipai/adapter-grok-local` package with
server, UI, and CLI entrypoints.
- Implemented Grok execution, session handling, environment diagnostics,
config building, skill syncing, and parser coverage inside the new
adapter package.
- Registered `grok_local` across the built-in adapter inventories and
capability/display metadata in server, UI, CLI, and shared constants.
- Added adapter route coverage for the new built-in type.
- Fixed Grok transcript readability by emitting streamed `text` and
`thought` fragments as deltas so the shared transcript builder coalesces
them into readable message blocks.
- Added regression tests for the Grok parser and transcript coalescing
behavior.
## Verification
- `pnpm vitest run
packages/adapters/grok-local/src/ui/parse-stdout.test.ts
ui/src/adapters/transcript.test.ts`
- `pnpm --filter @paperclipai/adapter-grok-local build`
- Manual runtime verification on the Paperclip host during
implementation and follow-up review:
- confirmed the Grok CLI was installed and authenticated
- confirmed the worktree dev server could be restarted cleanly and
health-checked after the parser follow-up
- No screenshots attached. This change is primarily adapter plumbing
plus transcript formatting behavior; reviewers can verify via the
Grok-backed run surfaces directly.
## Risks
- This adds a new built-in adapter, so any missed registration surface
could create inconsistencies between server, UI, and CLI behavior.
- The adapter depends on Grok Build's current event/output shape; if
upstream Grok streaming JSON changes, transcript parsing or session
extraction may need follow-up updates.
- The transcript readability fix intentionally changes how Grok
fragments are grouped, so any downstream code that implicitly expected
one entry per fragment would behave differently.
> 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 via Paperclip `codex_local` agent runtime.
- GPT-5-class coding model with tool use, shell execution, file editing,
and repo inspection enabled.
- Exact backend model ID/context window were not surfaced to the agent
in this Paperclip session.
## 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
- [ ] 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
2026-05-16 09:51:09 -07:00
|
|
|
grokLocalUIAdapter,
|
2026-03-31 21:38:37 +01:00
|
|
|
hermesLocalUIAdapter,
|
2026-03-31 20:21:13 +01:00
|
|
|
openCodeLocalUIAdapter,
|
|
|
|
|
piLocalUIAdapter,
|
|
|
|
|
cursorLocalUIAdapter,
|
|
|
|
|
openClawGatewayUIAdapter,
|
|
|
|
|
processUIAdapter,
|
|
|
|
|
httpUIAdapter,
|
|
|
|
|
]) {
|
2026-04-04 12:40:39 +01:00
|
|
|
builtinTypes.add(adapter.type);
|
|
|
|
|
builtinAdaptersByType.set(adapter.type, adapter);
|
2026-03-31 20:21:13 +01:00
|
|
|
registerUIAdapter(adapter);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
export function registerUIAdapter(adapter: UIAdapterModule): void {
|
|
|
|
|
const existingIndex = uiAdapters.findIndex((entry) => entry.type === adapter.type);
|
|
|
|
|
if (existingIndex >= 0) {
|
|
|
|
|
uiAdapters.splice(existingIndex, 1, adapter);
|
|
|
|
|
} else {
|
|
|
|
|
uiAdapters.push(adapter);
|
|
|
|
|
}
|
|
|
|
|
adaptersByType.set(adapter.type, adapter);
|
2026-04-01 21:56:19 +01:00
|
|
|
notifyAdapterChange();
|
2026-03-31 20:21:13 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
export function unregisterUIAdapter(type: string): void {
|
|
|
|
|
if (type === processUIAdapter.type || type === httpUIAdapter.type) return;
|
|
|
|
|
const existingIndex = uiAdapters.findIndex((entry) => entry.type === type);
|
|
|
|
|
if (existingIndex >= 0) {
|
|
|
|
|
uiAdapters.splice(existingIndex, 1);
|
|
|
|
|
}
|
|
|
|
|
adaptersByType.delete(type);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
export function findUIAdapter(type: string): UIAdapterModule | null {
|
|
|
|
|
return adaptersByType.get(type) ?? null;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
registerBuiltInUIAdapters();
|
2026-02-18 13:53:03 -06:00
|
|
|
|
|
|
|
|
export function getUIAdapter(type: string): UIAdapterModule {
|
2026-03-31 20:21:13 +01:00
|
|
|
const builtIn = adaptersByType.get(type);
|
|
|
|
|
|
|
|
|
|
if (!builtIn) {
|
|
|
|
|
let loadStarted = false;
|
|
|
|
|
return {
|
|
|
|
|
type,
|
|
|
|
|
label: type,
|
|
|
|
|
parseStdoutLine: (line: string, ts: string) => {
|
|
|
|
|
if (!loadStarted) {
|
|
|
|
|
loadStarted = true;
|
2026-04-04 14:04:33 -05:00
|
|
|
loadDynamicParser(type).then((parserModule) => {
|
|
|
|
|
if (parserModule) {
|
2026-03-31 20:21:13 +01:00
|
|
|
registerUIAdapter({
|
|
|
|
|
type,
|
|
|
|
|
label: type,
|
2026-04-04 14:04:33 -05:00
|
|
|
parseStdoutLine: parserModule.parseStdoutLine,
|
|
|
|
|
createStdoutParser: parserModule.createStdoutParser,
|
2026-04-01 13:58:02 +01:00
|
|
|
ConfigFields: SchemaConfigFields,
|
|
|
|
|
buildAdapterConfig: buildSchemaAdapterConfig,
|
2026-03-31 20:21:13 +01:00
|
|
|
});
|
|
|
|
|
}
|
|
|
|
|
});
|
|
|
|
|
}
|
|
|
|
|
return processUIAdapter.parseStdoutLine(line, ts);
|
|
|
|
|
},
|
2026-04-01 13:58:02 +01:00
|
|
|
ConfigFields: SchemaConfigFields,
|
|
|
|
|
buildAdapterConfig: buildSchemaAdapterConfig,
|
2026-03-31 20:21:13 +01:00
|
|
|
};
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return builtIn;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
2026-04-04 12:40:39 +01:00
|
|
|
* Keep the UI adapter registry in sync with the server's adapter list.
|
|
|
|
|
*
|
|
|
|
|
* Two concerns:
|
|
|
|
|
*
|
|
|
|
|
* 1. **Builtin overrides** — when an external adapter ships a ui-parser.js for a
|
|
|
|
|
* builtin type, the external parser takes priority. When the external is
|
|
|
|
|
* disabled or removed the original builtin parser is restored transparently.
|
|
|
|
|
* A generation counter guards against stale loads that resolve after the
|
|
|
|
|
* override has been torn down.
|
2026-03-31 20:21:13 +01:00
|
|
|
*
|
2026-04-04 12:40:39 +01:00
|
|
|
* 2. **Non-builtin externals** — register a bridge adapter that lazily loads the
|
|
|
|
|
* dynamic parser on first stdout line, falling back to the generic process
|
|
|
|
|
* adapter. Once the parser resolves the bridge is replaced.
|
2026-03-31 20:21:13 +01:00
|
|
|
*/
|
|
|
|
|
export function syncExternalAdapters(
|
2026-04-04 12:40:39 +01:00
|
|
|
serverAdapters: {
|
|
|
|
|
type: string;
|
|
|
|
|
label: string;
|
|
|
|
|
disabled?: boolean;
|
|
|
|
|
/** When true, the external override for a builtin type is client-side paused. */
|
|
|
|
|
overrideDisabled?: boolean;
|
|
|
|
|
}[],
|
2026-03-31 20:21:13 +01:00
|
|
|
): void {
|
2026-04-04 12:40:39 +01:00
|
|
|
const enabledExternalTypes = new Set(
|
|
|
|
|
serverAdapters.filter((a) => !a.disabled && !a.overrideDisabled).map((a) => a.type),
|
|
|
|
|
);
|
|
|
|
|
const allExternalTypes = new Set(
|
|
|
|
|
serverAdapters.map((a) => a.type),
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
// ── Builtin override lifecycle ──────────────────────────────────────────
|
|
|
|
|
|
|
|
|
|
for (const builtinType of builtinTypes) {
|
|
|
|
|
const originalBuiltin = builtinAdaptersByType.get(builtinType);
|
|
|
|
|
if (!originalBuiltin) continue;
|
|
|
|
|
|
|
|
|
|
const hasExternal = allExternalTypes.has(builtinType);
|
|
|
|
|
const externalEnabled = enabledExternalTypes.has(builtinType);
|
|
|
|
|
const wasOverridden = activeExternalOverrides.has(builtinType);
|
|
|
|
|
|
|
|
|
|
if (hasExternal && externalEnabled && !wasOverridden) {
|
|
|
|
|
// Activate: external just became active → replace builtin with bridge.
|
|
|
|
|
activeExternalOverrides.add(builtinType);
|
|
|
|
|
|
|
|
|
|
const gen = (overrideGeneration.get(builtinType) ?? 0) + 1;
|
|
|
|
|
overrideGeneration.set(builtinType, gen);
|
|
|
|
|
|
|
|
|
|
let loadStarted = false;
|
|
|
|
|
const fallbackParser = originalBuiltin.parseStdoutLine;
|
|
|
|
|
const externalEntry = serverAdapters.find((a) => a.type === builtinType);
|
|
|
|
|
const label = externalEntry?.label ?? builtinType;
|
|
|
|
|
|
|
|
|
|
registerUIAdapter({
|
|
|
|
|
type: builtinType,
|
|
|
|
|
label,
|
|
|
|
|
parseStdoutLine: (line: string, ts: string) => {
|
|
|
|
|
if (!loadStarted) {
|
|
|
|
|
loadStarted = true;
|
2026-04-04 14:04:33 -05:00
|
|
|
loadDynamicParser(builtinType).then((parserModule) => {
|
2026-04-04 12:40:39 +01:00
|
|
|
// Discard if the override was torn down while the load was in-flight.
|
2026-04-04 14:04:33 -05:00
|
|
|
if (parserModule && overrideGeneration.get(builtinType) === gen) {
|
2026-04-04 12:40:39 +01:00
|
|
|
registerUIAdapter({
|
|
|
|
|
type: builtinType,
|
|
|
|
|
label,
|
2026-04-04 14:04:33 -05:00
|
|
|
parseStdoutLine: parserModule.parseStdoutLine,
|
|
|
|
|
createStdoutParser: parserModule.createStdoutParser,
|
2026-04-04 12:40:39 +01:00
|
|
|
ConfigFields: originalBuiltin.ConfigFields,
|
|
|
|
|
buildAdapterConfig: originalBuiltin.buildAdapterConfig,
|
|
|
|
|
});
|
|
|
|
|
}
|
|
|
|
|
});
|
|
|
|
|
}
|
|
|
|
|
return fallbackParser(line, ts);
|
|
|
|
|
},
|
|
|
|
|
ConfigFields: originalBuiltin.ConfigFields,
|
|
|
|
|
buildAdapterConfig: originalBuiltin.buildAdapterConfig,
|
|
|
|
|
});
|
|
|
|
|
} else if ((!hasExternal || !externalEnabled) && wasOverridden) {
|
|
|
|
|
// Deactivate: external disabled or removed → restore builtin.
|
|
|
|
|
activeExternalOverrides.delete(builtinType);
|
|
|
|
|
overrideGeneration.delete(builtinType);
|
|
|
|
|
invalidateDynamicParser(builtinType);
|
|
|
|
|
registerUIAdapter(originalBuiltin);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// ── Non-builtin externals ───────────────────────────────────────────────
|
|
|
|
|
|
2026-03-31 20:21:13 +01:00
|
|
|
for (const { type, label } of serverAdapters) {
|
2026-04-04 12:40:39 +01:00
|
|
|
if (builtinTypes.has(type)) continue; // handled above
|
|
|
|
|
|
|
|
|
|
const existing = adaptersByType.get(type);
|
|
|
|
|
|
|
|
|
|
// If this type already has an externally-loaded dynamic parser, skip —
|
|
|
|
|
// it was loaded from disk on a previous sync. Only re-trigger loading
|
|
|
|
|
// when the server returns a new external adapter that hasn't been loaded yet.
|
|
|
|
|
if (existing && existing !== processUIAdapter) continue;
|
2026-03-31 20:21:13 +01:00
|
|
|
|
|
|
|
|
let loadStarted = false;
|
2026-04-04 12:40:39 +01:00
|
|
|
// Use the existing built-in parser as fallback (if any) so we don't
|
|
|
|
|
// regress to the generic process parser while the dynamic one loads.
|
|
|
|
|
const fallbackParser = existing?.parseStdoutLine ?? processUIAdapter.parseStdoutLine;
|
|
|
|
|
|
2026-03-31 20:21:13 +01:00
|
|
|
registerUIAdapter({
|
|
|
|
|
type,
|
|
|
|
|
label,
|
|
|
|
|
parseStdoutLine: (line: string, ts: string) => {
|
|
|
|
|
if (!loadStarted) {
|
|
|
|
|
loadStarted = true;
|
2026-04-04 14:04:33 -05:00
|
|
|
loadDynamicParser(type).then((parserModule) => {
|
|
|
|
|
if (parserModule) {
|
2026-03-31 20:21:13 +01:00
|
|
|
registerUIAdapter({
|
|
|
|
|
type,
|
|
|
|
|
label,
|
2026-04-04 14:04:33 -05:00
|
|
|
parseStdoutLine: parserModule.parseStdoutLine,
|
|
|
|
|
createStdoutParser: parserModule.createStdoutParser,
|
2026-04-04 12:40:39 +01:00
|
|
|
ConfigFields: existing?.ConfigFields ?? SchemaConfigFields,
|
|
|
|
|
buildAdapterConfig: existing?.buildAdapterConfig ?? buildSchemaAdapterConfig,
|
2026-03-31 20:21:13 +01:00
|
|
|
});
|
|
|
|
|
}
|
|
|
|
|
});
|
|
|
|
|
}
|
2026-04-04 12:40:39 +01:00
|
|
|
return fallbackParser(line, ts);
|
2026-03-31 20:21:13 +01:00
|
|
|
},
|
2026-04-04 12:40:39 +01:00
|
|
|
ConfigFields: existing?.ConfigFields ?? SchemaConfigFields,
|
|
|
|
|
buildAdapterConfig: existing?.buildAdapterConfig ?? buildSchemaAdapterConfig,
|
2026-03-31 20:21:13 +01:00
|
|
|
});
|
|
|
|
|
}
|
2026-02-18 13:53:03 -06:00
|
|
|
}
|
2026-03-16 12:17:28 -05:00
|
|
|
|
|
|
|
|
export function listUIAdapters(): UIAdapterModule[] {
|
|
|
|
|
return [...uiAdapters];
|
|
|
|
|
}
|