2026-03-17 09:24:28 -05:00
|
|
|
import type { Db } from "@paperclipai/db";
|
|
|
|
|
import { companies, instanceSettings } from "@paperclipai/db";
|
|
|
|
|
import {
|
2026-04-02 09:11:49 -05:00
|
|
|
DEFAULT_FEEDBACK_DATA_SHARING_PREFERENCE,
|
2026-04-07 09:54:39 +02:00
|
|
|
DEFAULT_BACKUP_RETENTION,
|
2026-03-20 08:00:39 -05:00
|
|
|
instanceGeneralSettingsSchema,
|
|
|
|
|
type InstanceGeneralSettings,
|
2026-03-17 09:24:28 -05:00
|
|
|
instanceExperimentalSettingsSchema,
|
|
|
|
|
type InstanceExperimentalSettings,
|
2026-03-20 08:00:39 -05:00
|
|
|
type PatchInstanceGeneralSettings,
|
2026-03-17 09:24:28 -05:00
|
|
|
type InstanceSettings,
|
|
|
|
|
type PatchInstanceExperimentalSettings,
|
|
|
|
|
} from "@paperclipai/shared";
|
|
|
|
|
import { eq } from "drizzle-orm";
|
|
|
|
|
|
|
|
|
|
const DEFAULT_SINGLETON_KEY = "default";
|
|
|
|
|
|
2026-03-20 08:00:39 -05:00
|
|
|
function normalizeGeneralSettings(raw: unknown): InstanceGeneralSettings {
|
|
|
|
|
const parsed = instanceGeneralSettingsSchema.safeParse(raw ?? {});
|
|
|
|
|
if (parsed.success) {
|
|
|
|
|
return {
|
|
|
|
|
censorUsernameInLogs: parsed.data.censorUsernameInLogs ?? false,
|
2026-04-02 11:45:15 -05:00
|
|
|
keyboardShortcuts: parsed.data.keyboardShortcuts ?? false,
|
2026-04-02 09:11:49 -05:00
|
|
|
feedbackDataSharingPreference:
|
|
|
|
|
parsed.data.feedbackDataSharingPreference ?? DEFAULT_FEEDBACK_DATA_SHARING_PREFERENCE,
|
2026-04-07 09:54:39 +02:00
|
|
|
backupRetention: parsed.data.backupRetention ?? DEFAULT_BACKUP_RETENTION,
|
2026-03-20 08:00:39 -05:00
|
|
|
};
|
|
|
|
|
}
|
|
|
|
|
return {
|
|
|
|
|
censorUsernameInLogs: false,
|
2026-04-02 11:45:15 -05:00
|
|
|
keyboardShortcuts: false,
|
2026-04-02 09:11:49 -05:00
|
|
|
feedbackDataSharingPreference: DEFAULT_FEEDBACK_DATA_SHARING_PREFERENCE,
|
2026-04-07 09:54:39 +02:00
|
|
|
backupRetention: DEFAULT_BACKUP_RETENTION,
|
2026-03-20 08:00:39 -05:00
|
|
|
};
|
|
|
|
|
}
|
|
|
|
|
|
2026-03-17 09:24:28 -05:00
|
|
|
function normalizeExperimentalSettings(raw: unknown): InstanceExperimentalSettings {
|
|
|
|
|
const parsed = instanceExperimentalSettingsSchema.safeParse(raw ?? {});
|
|
|
|
|
if (parsed.success) {
|
|
|
|
|
return {
|
Add SSH environment support (#4358)
## Thinking Path
> - Paperclip orchestrates AI agents for zero-human companies
> - The environments subsystem already models execution environments,
but before this branch there was no end-to-end SSH-backed runtime path
for agents to actually run work against a remote box
> - That meant agents could be configured around environment concepts
without a reliable way to execute adapter sessions remotely, sync
workspace state, and preserve run context across supported adapters
> - We also need environment selection to participate in normal
Paperclip control-plane behavior: agent defaults, project/issue
selection, route validation, and environment probing
> - Because this capability is still experimental, the UI surface should
be easy to hide and easy to remove later without undoing the underlying
implementation
> - This pull request adds SSH environment execution support across the
runtime, adapters, routes, schema, and tests, then puts the visible
environment-management UI behind an experimental flag
> - The benefit is that we can validate real SSH-backed agent execution
now while keeping the user-facing controls safely gated until the
feature is ready to come out of experimentation
## What Changed
- Added SSH-backed execution target support in the shared adapter
runtime, including remote workspace preparation, skill/runtime asset
sync, remote session handling, and workspace restore behavior after
runs.
- Added SSH execution coverage for supported local adapters, plus remote
execution tests across Claude, Codex, Cursor, Gemini, OpenCode, and Pi.
- Added environment selection and environment-management backend support
needed for SSH execution, including route/service work, validation,
probing, and agent default environment persistence.
- Added CLI support for SSH environment lab verification and updated
related docs/tests.
- Added the `enableEnvironments` experimental flag and gated the
environment UI behind it on company settings, agent configuration, and
project configuration surfaces.
## Verification
- `pnpm exec vitest run
packages/adapters/claude-local/src/server/execute.remote.test.ts
packages/adapters/cursor-local/src/server/execute.remote.test.ts
packages/adapters/gemini-local/src/server/execute.remote.test.ts
packages/adapters/opencode-local/src/server/execute.remote.test.ts
packages/adapters/pi-local/src/server/execute.remote.test.ts`
- `pnpm exec vitest run server/src/__tests__/environment-routes.test.ts`
- `pnpm exec vitest run
server/src/__tests__/instance-settings-routes.test.ts`
- `pnpm exec vitest run ui/src/lib/new-agent-hire-payload.test.ts
ui/src/lib/new-agent-runtime-config.test.ts`
- `pnpm -r typecheck`
- `pnpm build`
- Manual verification on a branch-local dev server:
- enabled the experimental flag
- created an SSH environment
- created a Linux Claude agent using that environment
- confirmed a run executed on the Linux box and synced workspace changes
back
## Risks
- Medium: this touches runtime execution flow across multiple adapters,
so regressions would likely show up in remote session setup, workspace
sync, or environment selection precedence.
- The UI flag reduces exposure, but the underlying runtime and route
changes are still substantial and rely on migration correctness.
- The change set is broad across adapters, control-plane services,
migrations, and UI gating, so review should pay close attention to
environment-selection precedence and remote workspace lifecycle
behavior.
## Model Used
- OpenAI Codex via Paperclip's local Codex adapter, GPT-5-class coding
model with tool use and code execution in the local repo workspace. The
local adapter does not surface a more specific public model version
string in this branch 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
- [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
2026-04-23 19:15:22 -07:00
|
|
|
enableEnvironments: parsed.data.enableEnvironments ?? false,
|
2026-03-17 09:24:28 -05:00
|
|
|
enableIsolatedWorkspaces: parsed.data.enableIsolatedWorkspaces ?? false,
|
2026-03-20 08:43:47 -05:00
|
|
|
autoRestartDevServerWhenIdle: parsed.data.autoRestartDevServerWhenIdle ?? false,
|
2026-03-17 09:24:28 -05:00
|
|
|
};
|
|
|
|
|
}
|
|
|
|
|
return {
|
Add SSH environment support (#4358)
## Thinking Path
> - Paperclip orchestrates AI agents for zero-human companies
> - The environments subsystem already models execution environments,
but before this branch there was no end-to-end SSH-backed runtime path
for agents to actually run work against a remote box
> - That meant agents could be configured around environment concepts
without a reliable way to execute adapter sessions remotely, sync
workspace state, and preserve run context across supported adapters
> - We also need environment selection to participate in normal
Paperclip control-plane behavior: agent defaults, project/issue
selection, route validation, and environment probing
> - Because this capability is still experimental, the UI surface should
be easy to hide and easy to remove later without undoing the underlying
implementation
> - This pull request adds SSH environment execution support across the
runtime, adapters, routes, schema, and tests, then puts the visible
environment-management UI behind an experimental flag
> - The benefit is that we can validate real SSH-backed agent execution
now while keeping the user-facing controls safely gated until the
feature is ready to come out of experimentation
## What Changed
- Added SSH-backed execution target support in the shared adapter
runtime, including remote workspace preparation, skill/runtime asset
sync, remote session handling, and workspace restore behavior after
runs.
- Added SSH execution coverage for supported local adapters, plus remote
execution tests across Claude, Codex, Cursor, Gemini, OpenCode, and Pi.
- Added environment selection and environment-management backend support
needed for SSH execution, including route/service work, validation,
probing, and agent default environment persistence.
- Added CLI support for SSH environment lab verification and updated
related docs/tests.
- Added the `enableEnvironments` experimental flag and gated the
environment UI behind it on company settings, agent configuration, and
project configuration surfaces.
## Verification
- `pnpm exec vitest run
packages/adapters/claude-local/src/server/execute.remote.test.ts
packages/adapters/cursor-local/src/server/execute.remote.test.ts
packages/adapters/gemini-local/src/server/execute.remote.test.ts
packages/adapters/opencode-local/src/server/execute.remote.test.ts
packages/adapters/pi-local/src/server/execute.remote.test.ts`
- `pnpm exec vitest run server/src/__tests__/environment-routes.test.ts`
- `pnpm exec vitest run
server/src/__tests__/instance-settings-routes.test.ts`
- `pnpm exec vitest run ui/src/lib/new-agent-hire-payload.test.ts
ui/src/lib/new-agent-runtime-config.test.ts`
- `pnpm -r typecheck`
- `pnpm build`
- Manual verification on a branch-local dev server:
- enabled the experimental flag
- created an SSH environment
- created a Linux Claude agent using that environment
- confirmed a run executed on the Linux box and synced workspace changes
back
## Risks
- Medium: this touches runtime execution flow across multiple adapters,
so regressions would likely show up in remote session setup, workspace
sync, or environment selection precedence.
- The UI flag reduces exposure, but the underlying runtime and route
changes are still substantial and rely on migration correctness.
- The change set is broad across adapters, control-plane services,
migrations, and UI gating, so review should pay close attention to
environment-selection precedence and remote workspace lifecycle
behavior.
## Model Used
- OpenAI Codex via Paperclip's local Codex adapter, GPT-5-class coding
model with tool use and code execution in the local repo workspace. The
local adapter does not surface a more specific public model version
string in this branch 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
- [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
2026-04-23 19:15:22 -07:00
|
|
|
enableEnvironments: false,
|
2026-03-17 09:24:28 -05:00
|
|
|
enableIsolatedWorkspaces: false,
|
2026-03-20 08:43:47 -05:00
|
|
|
autoRestartDevServerWhenIdle: false,
|
2026-03-17 09:24:28 -05:00
|
|
|
};
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
function toInstanceSettings(row: typeof instanceSettings.$inferSelect): InstanceSettings {
|
|
|
|
|
return {
|
|
|
|
|
id: row.id,
|
2026-03-20 08:00:39 -05:00
|
|
|
general: normalizeGeneralSettings(row.general),
|
2026-03-17 09:24:28 -05:00
|
|
|
experimental: normalizeExperimentalSettings(row.experimental),
|
|
|
|
|
createdAt: row.createdAt,
|
|
|
|
|
updatedAt: row.updatedAt,
|
|
|
|
|
};
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
export function instanceSettingsService(db: Db) {
|
|
|
|
|
async function getOrCreateRow() {
|
|
|
|
|
const existing = await db
|
|
|
|
|
.select()
|
|
|
|
|
.from(instanceSettings)
|
|
|
|
|
.where(eq(instanceSettings.singletonKey, DEFAULT_SINGLETON_KEY))
|
|
|
|
|
.then((rows) => rows[0] ?? null);
|
|
|
|
|
if (existing) return existing;
|
|
|
|
|
|
|
|
|
|
const now = new Date();
|
|
|
|
|
const [created] = await db
|
|
|
|
|
.insert(instanceSettings)
|
|
|
|
|
.values({
|
|
|
|
|
singletonKey: DEFAULT_SINGLETON_KEY,
|
2026-03-20 08:00:39 -05:00
|
|
|
general: {},
|
2026-03-17 09:24:28 -05:00
|
|
|
experimental: {},
|
|
|
|
|
createdAt: now,
|
|
|
|
|
updatedAt: now,
|
|
|
|
|
})
|
|
|
|
|
.onConflictDoUpdate({
|
|
|
|
|
target: [instanceSettings.singletonKey],
|
|
|
|
|
set: {
|
|
|
|
|
updatedAt: now,
|
|
|
|
|
},
|
|
|
|
|
})
|
|
|
|
|
.returning();
|
|
|
|
|
|
[codex] Improve agent runtime recovery and governance (#4086)
## Thinking Path
> - Paperclip orchestrates AI agents for zero-human companies.
> - The heartbeat runtime, agent import path, and agent configuration
defaults determine whether work is dispatched safely and predictably.
> - Several accumulated fixes all touched agent execution recovery, wake
routing, import behavior, and runtime concurrency defaults.
> - Those changes need to land together so the heartbeat service and
agent creation defaults stay internally consistent.
> - This pull request groups the runtime/governance changes from the
split branch into one standalone branch.
> - The benefit is safer recovery for stranded runs, bounded high-volume
reads, imported-agent approval correctness, skill-template support, and
a clearer default concurrency policy.
## What Changed
- Fixed stranded continuation recovery so successful automatic retries
are requeued instead of incorrectly blocking the issue.
- Bounded high-volume issue/log reads across issue, heartbeat, agent,
project, and workspace paths.
- Fixed imported-agent approval and instruction-path permission
handling.
- Quarantined seeded worktree execution state during worktree
provisioning.
- Queued approval follow-up wakes and hardened SQL_ASCII heartbeat
output handling.
- Added reusable agent instruction templates for hiring flows.
- Set the default max concurrent agent runs to five and updated related
UI/tests/docs.
## Verification
- `pnpm install --frozen-lockfile`
- `pnpm exec vitest run server/src/__tests__/company-portability.test.ts
server/src/__tests__/heartbeat-process-recovery.test.ts
server/src/__tests__/heartbeat-comment-wake-batching.test.ts
server/src/__tests__/heartbeat-list.test.ts
server/src/__tests__/issues-service.test.ts
server/src/__tests__/agent-permissions-routes.test.ts
packages/adapter-utils/src/server-utils.test.ts
ui/src/lib/new-agent-runtime-config.test.ts`
- Split integration check: merged this branch first, followed by the
other [PAP-1614](/PAP/issues/PAP-1614) branches, with no merge
conflicts.
- Confirmed this branch does not include `pnpm-lock.yaml`.
## Risks
- Medium risk: touches heartbeat recovery, queueing, and issue list
bounds in central runtime paths.
- Imported-agent and concurrency default behavior changes may affect
existing automation that assumes one-at-a-time default runs.
- No database migrations are included.
> 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.4 tool-enabled coding model, agentic
code-editing/runtime with local shell and GitHub CLI access; exact
context window and reasoning mode are not exposed by the Paperclip
harness.
## 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-20 06:19:48 -05:00
|
|
|
if (created) return created;
|
|
|
|
|
|
|
|
|
|
const raced = await db
|
|
|
|
|
.select()
|
|
|
|
|
.from(instanceSettings)
|
|
|
|
|
.where(eq(instanceSettings.singletonKey, DEFAULT_SINGLETON_KEY))
|
|
|
|
|
.then((rows) => rows[0] ?? null);
|
|
|
|
|
if (raced) return raced;
|
|
|
|
|
|
|
|
|
|
throw new Error("Failed to initialize instance settings row");
|
2026-03-17 09:24:28 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return {
|
|
|
|
|
get: async (): Promise<InstanceSettings> => toInstanceSettings(await getOrCreateRow()),
|
|
|
|
|
|
2026-03-20 08:00:39 -05:00
|
|
|
getGeneral: async (): Promise<InstanceGeneralSettings> => {
|
|
|
|
|
const row = await getOrCreateRow();
|
|
|
|
|
return normalizeGeneralSettings(row.general);
|
|
|
|
|
},
|
|
|
|
|
|
2026-03-17 09:24:28 -05:00
|
|
|
getExperimental: async (): Promise<InstanceExperimentalSettings> => {
|
|
|
|
|
const row = await getOrCreateRow();
|
|
|
|
|
return normalizeExperimentalSettings(row.experimental);
|
|
|
|
|
},
|
|
|
|
|
|
2026-03-20 08:00:39 -05:00
|
|
|
updateGeneral: async (patch: PatchInstanceGeneralSettings): Promise<InstanceSettings> => {
|
|
|
|
|
const current = await getOrCreateRow();
|
|
|
|
|
const nextGeneral = normalizeGeneralSettings({
|
|
|
|
|
...normalizeGeneralSettings(current.general),
|
|
|
|
|
...patch,
|
|
|
|
|
});
|
|
|
|
|
const now = new Date();
|
|
|
|
|
const [updated] = await db
|
|
|
|
|
.update(instanceSettings)
|
|
|
|
|
.set({
|
|
|
|
|
general: { ...nextGeneral },
|
|
|
|
|
updatedAt: now,
|
|
|
|
|
})
|
|
|
|
|
.where(eq(instanceSettings.id, current.id))
|
|
|
|
|
.returning();
|
|
|
|
|
return toInstanceSettings(updated ?? current);
|
|
|
|
|
},
|
|
|
|
|
|
2026-03-17 09:24:28 -05:00
|
|
|
updateExperimental: async (patch: PatchInstanceExperimentalSettings): Promise<InstanceSettings> => {
|
|
|
|
|
const current = await getOrCreateRow();
|
|
|
|
|
const nextExperimental = normalizeExperimentalSettings({
|
|
|
|
|
...normalizeExperimentalSettings(current.experimental),
|
|
|
|
|
...patch,
|
|
|
|
|
});
|
|
|
|
|
const now = new Date();
|
|
|
|
|
const [updated] = await db
|
|
|
|
|
.update(instanceSettings)
|
|
|
|
|
.set({
|
|
|
|
|
experimental: { ...nextExperimental },
|
|
|
|
|
updatedAt: now,
|
|
|
|
|
})
|
|
|
|
|
.where(eq(instanceSettings.id, current.id))
|
|
|
|
|
.returning();
|
|
|
|
|
return toInstanceSettings(updated ?? current);
|
|
|
|
|
},
|
|
|
|
|
|
|
|
|
|
listCompanyIds: async (): Promise<string[]> =>
|
|
|
|
|
db
|
|
|
|
|
.select({ id: companies.id })
|
|
|
|
|
.from(companies)
|
|
|
|
|
.then((rows) => rows.map((row) => row.id)),
|
|
|
|
|
};
|
|
|
|
|
}
|