Extract adapter registry across CLI, server, and UI
Refactor monolithic heartbeat service, AgentConfigForm, and CLI heartbeat-run into a proper adapter registry pattern. Each adapter type (process, claude-local, codex-local, http) gets its own module with server-side execution logic, CLI invocation, and UI config form. Significantly reduces file sizes and enables adding new adapters without touching core code. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
11
server/src/adapters/index.ts
Normal file
11
server/src/adapters/index.ts
Normal file
@@ -0,0 +1,11 @@
|
||||
export { getServerAdapter, listAdapterModels } from "./registry.js";
|
||||
export type {
|
||||
ServerAdapterModule,
|
||||
AdapterExecutionContext,
|
||||
AdapterExecutionResult,
|
||||
AdapterInvocationMeta,
|
||||
UsageSummary,
|
||||
AgentRecord,
|
||||
AgentRuntimeStateRecord,
|
||||
} from "./types.js";
|
||||
export { runningProcesses } from "./utils.js";
|
||||
Reference in New Issue
Block a user