Files
PaperClipAI/doc/plans/chat-adapters/setup-wireframe-data-v8.mjs
T
DottaandPaperclip 889947c238 feat: add experimental native chat connectors (#13038)
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work.
> - People also ask agents for work in their existing chat tools.
> - Each external conversation needs one task and a current authorized
source.
> - Retries, Stop, and provider failures must not duplicate work or
expose private data.
> - The first chat PR establishes the opt-in provider and data
contracts.
> - This PR adds experimental channel integration and its durable
control plane.
> - Users can request work from connected channels and inspect delivery
in Paperclip.

## Linked Issues or Issue Description

Refs #13100 and #13092. This is the second of exactly two chat PRs.
Foundation #13100 is merged and changed 143 files. Runner prerequisite
#13092 is also merged. This PR changes 400 files against master, below
the 500-file review limit. It contains no wireframe images or HTML
galleries.

## What Changed

- Add native Slack, GitHub, Microsoft Teams, Telegram, and Discord chat
connections. Keep chat disabled unless the operator enables experimental
chat connectors. Preserve the production GitHub tool connection and its
normal setup path.
- Bind each provider bot identity to one immutable Paperclip agent. Bind
each admitted external conversation to one task. Paperclip owns tasks,
runs, permissions, and audit records.
- Add durable admission, per-conversation queues, questions, task
controls, progress, final replies, images, files, and delivery receipts.
Board comments remain internal unless explicitly sent to the channel.
- Check current identity, provider reach, resource access, credentials,
runtime generation, and exact source before provider effects. Keep
private responses private. Never send raw reasoning, private logs,
credentials, or tool arguments.
- Hold uncertain sends for explicit audited resolution. Make Board
Send-to-channel atomic and idempotent. Keep reconnect and setup
credentials in Paperclip secret storage.
- Preserve current native-runner authority across retries, lost
acknowledgements, and recovery. Keep immutable input and completion
contracts separate from newer user input. Receipt reconciliation cannot
launch a provider.
- Reconcile chat close/new ordering and provider-effect lock order.
Audit resource access changes in the same transaction. Submit only the
selected resource from each UI toggle so stale pages cannot undo
unrelated access changes.
- Drain Codex stdout before certifying process exit. Bound the drain
with the existing shutdown grace. Preserve observed terminal authority
without treating an undrained process as successful or reusable.
- Incorporate master `018ca5da` with its ACP Stop, mobile task layout,
runner packaging, and official lock changes. Preserve dedicated
chat-answer continuations in both directions when ordinary queued
comments are adopted after Stop.
- Fence late adapter readiness behind an earlier Stop for the same run.
Preserve verified cleanup for registered adapters. Handle single Stop,
agent pause, duplicate Stops, and failure release without creating a
false cancellation receipt.
- Incorporate master's `6dd48cad4` wake-queue extraction. Preserve exact
failed-chat retry authorization and lineage, retired question-source
suppression, and the block on generic recovery that would discard the
admitted source. Fresh deferred input retains its separate promotion
path.
- Incorporate master `2a05b5ed3` and its queue-admission extraction,
simplified transaction ports, and separate runner CI job. Preserve exact
durable receipts, actor separation, and dedicated-answer isolation
through the new module. A failed receipt insert rolls back the
accompanying deferred-wake merge.

## Verification

Current head: `afe19299d06253cb628eb398e91d1200ea9f412a`, incorporating
master `2a05b5ed3457ea33efd6895520447d1d97fe98d8`. The conflicts are
resolved. This successor fixes two test-harness boundaries exposed by
CI: per-case route-module preparation and actual durable-save completion
before intentional runner termination. Production code and all existing
test/turn deadlines are unchanged. [Exact-head Greptile
review](https://github.com/paperclipai/paperclip/pull/13038#issuecomment-5587250594)
is **5/5**, completed September 10 at 13:20:55 UTC, with no actionable
findings or open review threads. [Fresh exact-head
CI](https://github.com/paperclipai/paperclip/actions/runs/34481724341)
passes **all 24 jobs**, including Build and both required aggregates.
Normal exact-head guarded merge was attempted and rejected by the
remaining branch approval policy: CODEOWNER review is required and no
human approval is present. Normal **squash auto-merge is enabled** as of
September 10 at 13:36:26 UTC. Requested CODEOWNERS have been notified;
no approval bypass or self-approval was used. Earlier-head results below
remain historical evidence, not qualification of this successor.

- Final exact-head Linux evidence: 995/995 chat integration cases; 36/36
agent-skills routes; 35/35 runner live-session cases, including real
process kill/resume; 1948 runner Vitest cases with three existing
benchmark/platform guards; 870/870 API-authority cases; and 104 browser
cases with four existing optional skips. Rust, conformance/replay, full
repository build, typecheck, canary, all server/workspace shards, and
both required aggregates pass with normal CI concurrency. Earlier failed
attempts remain recorded below.

- Latest test-only qualification: 141/141
route/permissions/authentication cases pass in separate cold forks, with
plain server types and independent review clear. The real-runner suite
passes 35/35, with plain runner types and independent review clear. A
controlled premature-save acknowledgement fails as expected; matching
ownership/effect/process evidence, rejected saves, real turn outcome,
test abort, and pre-kill liveness are covered. No local reproduction of
the original CI scheduling failure is claimed. The preceding [CI
run](https://github.com/paperclipai/paperclip/actions/runs/34479680858)
passes 21/24 jobs, including all 995 Linux chat cases and browser
aggregate (104 passed, four existing optional skips); only Build, the
skills serialized shard, and the required verification aggregate fail.
Its exact-head Greptile review was 5/5. Both failed job logs are
retained.

- Final fixture qualification: all eight focused Discord cases and all
995 chat integration cases pass. The exact modal statement/PID is
observed before taking the real connection lock; the test then proves
its actual blocking relationship before mutation. Original SQL
execution, provider behavior, negative assertions, and 1s/15s timeouts
remain unchanged. Independent review is clear and test/production hashes
remain frozen. The preceding [CI
attempt](https://github.com/paperclipai/paperclip/actions/runs/34477184777)
passed 22 jobs, including Build/runner, typecheck, canary, all other
test shards, and browser aggregate (104 passed, four existing optional
skips); the two fixture failures and failed verification aggregate
remain recorded, not relabeled as a pass.

- Current queue-module composition: 308/308 recovery/batching/queue/Stop
tests; 995/995 full chat integration; 89/89 module tests, including real
PostgreSQL receipt-insert rollback; 24/24 workflow/module-boundary
tests; plain server and UI types. All four actual local process/ACP
browser paths pass in 1.4 minutes. Fresh databases, no skips or retries,
stable reviewed source hashes. The initial boundary failure is retained;
its no-op service wrapper was removed without changing recovery context
or weakening the check. An exploratory standalone test-directory
typecheck fails because its new upstream transformation config is not a
standalone typechecking project; standard CI/build does not invoke it,
and no configuration was weakened to suppress those diagnostics.

- The preceding head `e02a63d462ce5d47433b0aeb632bb6fd20aab1ba` passed
[all 24 CI
jobs](https://github.com/paperclipai/paperclip/actions/runs/34436462958)
and exact-head Greptile review at 5/5. Required CODEOWNER review
prevented its normal merge before master advanced again.

- Final extracted-module composition: 307/307 recovery, batching, queue
and Stop-control tests; 995/995 full chat integration; 49/49 module
tests including eight PostgreSQL adapter cases; and 19/19 issue-update
tests. Plain server types pass. All four actual local process/ACP
browser paths pass in 1.3 minutes. Fresh databases, no skips or retries
in these cohorts, frozen source hashes, and independent review clear.

- The preceding head `3e4e1c1c` passes [all PR CI
jobs](https://github.com/paperclipai/paperclip/actions/runs/34415826820),
including Build and required `ci / verify` and `ci / e2e`. Both the
original Rust failure and the previously load-sensitive lineage fixture
pass with unchanged Linux concurrency. Master advanced afterward and
required this reconciliation.
- Final master composition: 448/448 focused UI tests, 186/186 adapter
tests, 24/24 queue/control tests, and 11/11 packaging tests. Plain UI,
server, shared, and adapter types pass. Token gates and diff checks
pass. Independent server and UI reviews are clear.
- Stop-registration regression: both real-service cases fail against
exact `a95` source and pass with the fix. The full corrected
recovery/control suite passes 265/265. Duplicate-owner and failed-Stop
controls also pass. Plain server types pass. The readiness barrier
prevents provider startup without adding an acknowledgment to an already
terminal run.
- Final qualification strengthens terminal-field equality and repeats
both affected cases successfully on a fresh database. All four actual
local process/ACP browser paths pass again in 1.3 minutes, without skips
or retries. The final screenshot shows Cancelled, a paused subtree,
retained input, and no error toast.
- Two new actual-service regressions fail before the merge fix. They
prove that queued-comment adoption could consume a dedicated chat answer
or add unrelated input to that answer. The fixed four-case cohort
passes, including ordinary upstream continuation and adapter Stop
controls. Full recovery passes 257/257. All four actual local
process/ACP Stop browser flows pass in 1.4 minutes, without skips or
retries, on a fresh database.
- The unchanged runner artifact was qualified with 171/171 transport
tests, 870/870 API-authority tests, conformance 1/1, and replay 11/11.
Six controlled reader tests prove the exit/drain repair. Its local
serial Rust workspace passed 546 top-level cases plus two invoked
helpers; the later passing Linux CI supplies default-concurrency
evidence.
- Prior exact-source full chat integration passes 995/995. Settings
regressions cover concurrent stale pages, 501 destinations, pending
state, rejected updates, and explicit retry. These deterministic tests
do not prove live provider behavior.
- Retained failed attempts and their causes are in the [qualification
log](https://github.com/paperclipai/paperclip/blob/afe19299d06253cb628eb398e91d1200ea9f412a/doc/plans/chat-adapters/2026-09-08-chat-queue-and-webhook-repair.md).
The first merge adapter run timed out while macOS slept for 290 seconds.
Its unchanged repeat passed with a temporary sleep guard. No assertion,
deadline, or CI gate was weakened.

Review commands include `pnpm --filter @paperclipai/server exec vitest
run src/__tests__/heartbeat-process-recovery.test.ts
src/__tests__/issue-queued-comments-routes.test.ts` and `pnpm exec
playwright test --config tests/e2e/playwright.config.ts
tests/e2e/acp-stop-continuation.spec.ts`. Database suites require fresh
disposable databases. See the [browser
runbook](https://github.com/paperclipai/paperclip/blob/afe19299d06253cb628eb398e91d1200ea9f412a/doc/plans/chat-adapters/2026-09-04-chat-adapters-browser-e2e-runbook.md)
for provider setup and separate live acceptance steps.

## Risks

- This remains experimental. Deterministic tests and bounded live
evidence do not establish every provider feature, tenant, permission
layout, or media shape. Teams work-tenant qualification is still open.
- Failed and uncertain provider effects remain visible and can require
operator action. A transport receipt does not prove recipient
visibility.
- Native controller and runner artifacts must remain compatible.
Preserve lease ownership, terminal authority, source binding, and
quarantine during future changes.
- Access and audit rows commit together, but activity notifications
remain best-effort. This is not a new durable event outbox.
- The PR operation does not deploy a live server, replace its runner, or
change provider permissions. Remaining live qualification is documented
in the [temporary
handoff](https://github.com/paperclipai/paperclip/blob/afe19299d06253cb628eb398e91d1200ea9f412a/doc/plans/chat-adapters/2026-09-08-open-qualification-followups.md).

## Model Used

OpenAI Codex assisted with implementation, tool execution, testing, and
review. The work records `gpt-6-astra` assistance. The environment does
not report a context-window size. No private reasoning traces are
included.

## 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 searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

---------

Co-authored-by: Paperclip <noreply@paperclip.ing>
2026-09-10 10:06:45 -05:00

276 lines
10 KiB
JavaScript

import { setupFlows as v6SetupFlows } from "./setup-wireframe-data-v6.mjs";
const githubSetup = {
provider: "GitHub",
short: "GitHub",
screens: [
{
id: "16",
slug: "github-create",
title: "Create or connect a GitHub App",
subtitle:
"Bring your own dedicated GitHub App and verify it with Paperclip.",
rail: ["Agent selected", "Connect GitHub App", "Try Maya"],
active: 1,
mode: "default",
instructions: [
[
"Generate the webhook secret",
"Paperclip stores a random 32-byte secret and shows it once. Paste it with the Paperclip webhook URL into GitHub and keep SSL verification enabled.",
],
[
"Set minimum permissions and events",
"Grant Metadata: read, Issues: read and write, and Pull requests: read and write. Subscribe only to Issue comment and Pull request review comment.",
],
[
"Create and install the App",
"Choose the owning user or organization, keep user authorization off, then install the App on only the repositories where people may mention the agent.",
],
[
"Return the App credentials",
"Paste the numeric App ID and private-key PEM into Paperclip. Connect remains unavailable until GitHub has delivered a correctly signed webhook ping.",
],
],
values: [
[
"Paperclip webhook URL",
"https://paperclip.example/api/chat-webhooks/…/github",
],
["Webhook secret", "Generated by Paperclip · shown once"],
],
fields: [
["GitHub App ID", "123456"],
["Private key (PEM)", "Write-only PEM"],
],
actions: [
[
"Generate webhook secret",
"Creates and stores the webhook secret, then exposes its one-time copy value.",
],
[
"Open new GitHub App form",
"Opens GitHub App registration; GitHub remains the authority for App ownership and repository installation.",
],
[
"Connect and verify",
"Authenticates with the App ID and private key, verifies the immutable App identity, required permissions and events, installation, and signed webhook ping.",
],
],
annotations: [
"The customer-owned App path is the complete shipped setup; no managed App Manifest exchange is required.",
"Paperclip generates the webhook secret and never returns it from normal endpoint reads.",
"Grant Metadata read, Issues and Pull requests read/write, plus Issue comment and Pull request review comment events; installation lifecycle events are automatic.",
"GitHub installation scope and Paperclip repository enablement remain independent reach controls.",
],
rationale:
"Bring-your-own App credentials are sufficient to ship and preserve one provider bot identity per Paperclip agent.",
},
{
id: "46",
slug: "github-try",
title: "Try Maya in GitHub",
subtitle: "Start one task in an installed repository.",
rail: ["Agent selected", "Connect GitHub App", "Try Maya"],
active: 2,
mode: "default",
instructions: [
[
"Open an issue or pull request",
"Use one of the repositories selected in the customer-owned App installation.",
],
[
"Mention Maya",
"Add a comment that directly mentions the verified GitHub App bot.",
],
[
"Continue the task",
"Add another comment in the same issue or pull request without repeating the mention.",
],
],
actions: [
[
"Open GitHub",
"Opens an installed repository while Paperclip waits for the first signed mention and follow-up to complete setup.",
],
],
annotations: [
"The test uses the real GitHub issue or pull-request conversation boundary.",
"The first addressed setup repository becomes enabled; other discovered repositories remain disabled.",
"One external conversation maps to one Paperclip task.",
],
rationale:
"A signed provider round trip proves installation, reach, identity, and conversation continuity.",
},
],
};
// v8 also replaced the helper-first Teams draft. Keep the current generator
// from overwriting that settled customer-owned setup while it consumes the
// historical v6 data for unchanged providers.
const teamsSetup = {
provider: "Microsoft Teams",
short: "Teams",
screens: [
{
id: "19",
slug: "teams-register",
title: "Create Maya for Microsoft Teams",
subtitle: "Register a customer-owned Entra App and Azure Bot.",
rail: ["Agent selected", "Connect Teams app", "Install Maya", "Try Maya"],
active: 1,
mode: "default",
instructions: [
[
"Copy the messaging endpoint",
"Use Paperclip's public callback in the Azure Bot configuration.",
],
[
"Create the Microsoft resources",
"Create the single-tenant Entra App, client secret, Azure Bot, and customer-owned Teams app in Microsoft's portals.",
],
[
"Return the identity values",
"Paste the Application ID, Directory/Tenant ID, and client-secret value into Paperclip.",
],
],
actions: [
[
"Copy messaging endpoint",
"Copies the public callback for Azure Bot configuration.",
],
[
"Open Microsoft setup",
"Opens Microsoft's provider-owned registration surfaces.",
],
[
"Connect and verify",
"Stores the client secret write-only and verifies the tenant and application identity.",
],
],
annotations: [
"Paperclip provides the exact public messaging endpoint.",
"The operator creates the single-tenant Entra App, Azure Bot, and Teams app in Microsoft.",
"A future helper is optional and cannot gate the customer-owned path or release.",
],
rationale:
"Bring-your-own credentials are the required portable setup path.",
},
{
id: "49",
slug: "teams-install",
title: "Install Maya in Microsoft Teams",
subtitle:
"Publish or upload the customer-owned app, then add it in Teams.",
rail: ["Agent selected", "Connect Teams app", "Install Maya", "Try Maya"],
active: 2,
mode: "default",
instructions: [
[
"Open Teams Developer Portal",
"Complete the app metadata and publish it or download it for tenant-approved custom upload.",
],
[
"Install the app",
"Use Microsoft's installation flow in the intended personal, team, or group-chat scope.",
],
],
actions: [
[
"Open Teams Developer Portal",
"Opens the provider-owned app surface; tenant policy may require administrator approval.",
],
],
annotations: [
"Microsoft owns app creation, packaging, publication, approval, and installation.",
"Paperclip does not generate a complete Teams package or promise an install link.",
"Tenant approval remains in Microsoft's install experience.",
],
rationale:
"Customer-owned registration is required; Microsoft owns the app artifact and installation.",
},
{
id: "50",
slug: "teams-try",
title: "Try Maya in Microsoft Teams",
subtitle: "Start one task in a channel post.",
rail: ["Agent selected", "Connect Teams app", "Install Maya", "Try Maya"],
active: 3,
mode: "default",
instructions: [
[
"Open an installed channel",
"Start a new post rather than replying to an unrelated post.",
],
["Mention Maya", "Mention the installed bot in the new post."],
[
"Continue in replies",
"Reply once beneath that post; the post and replies are one Paperclip task.",
],
],
actions: [
[
"Open Microsoft Teams",
"Opens Teams while Paperclip waits for the authenticated mention and reply.",
],
],
annotations: [
"The body is only the Teams channel test sequence.",
"The instructions teach the channel-post-and-replies task boundary.",
"There is one action: open Teams and perform the test.",
],
rationale: "The final provider event is the verification.",
},
{
id: "48",
slug: "teams-manual",
title: "Microsoft provider setup details",
subtitle:
"Create the customer-owned bot and app, then paste the three identity values.",
rail: ["Agent selected", "Connect Teams app", "Install Maya", "Try Maya"],
active: 1,
mode: "default",
instructions: [
[
"Create the Microsoft identity",
"Create a single-tenant Entra App registration and a client secret.",
],
[
"Create the bot and Teams app",
"Create the Azure Bot, configure Paperclip's endpoint, and create the customer-owned Teams app in Developer Portal.",
],
[
"Enter the identity below",
"Return the Application ID, Directory ID, and client-secret value to Paperclip.",
],
],
actions: [
[
"Copy Paperclip endpoint",
"Copies the public messaging endpoint for the Azure Bot resource.",
],
[
"Connect and verify",
"Stores the client secret write-only and verifies Microsoft bot authentication.",
],
["Back", "Returns to the primary customer-owned credential setup."],
],
annotations: [
"The endpoint is the one Paperclip-specific value required by Microsoft.",
"Every instruction is a provider portal operation.",
"The three identity fields are the minimum credentials Paperclip needs.",
"Connect does not generate a Teams package or install link.",
],
rationale:
"This is reference detail for the required customer-owned path; a future helper remains optional.",
},
],
};
export const setupFlows = v6SetupFlows.map((flow) =>
flow.provider === "GitHub"
? githubSetup
: flow.provider === "Microsoft Teams"
? teamsSetup
: flow,
);