Files
PaperClipAI/server/src/__tests__/redact-sensitive.test.ts
T
DottaandPaperclip b8ffeb973a feat(runner): add experimental Grok Bot agent participation (#16219)
## Thinking Path

> - Paperclip manages AI agents that perform work for a company.
> - The shared Runner owns task admission, authority, receipts and
finalization.
> - An existing Grok Bot needs to receive assignments and return results
through that Runner.
> - The Bot also needs governed access when it starts work from its own
conversation.
> - This PR adds agent-purpose MCP access and routine webhook dispatch.
> - It reuses the external-agent Rust Runner and keeps Grok capabilities
explicit.
> - The provider stays experimental until the real-client managed
journeys pass.

## Linked Issues or Issue Description

**Agent or provider**
Grok Bot, distinct from the Grok Build coding runtime in #13882.

**Why this adapter is useful**
Users can assign work to an existing Bot, receive progress, questions,
documents and files in Paperclip, and let the Bot initiate work under
its agent permissions.

**How the agent is invoked**
A webhook-only routine delivers bounded references. Dedicated
named-agent OAuth and MCP provide inbound calls. Setup follows [Grok
routines](https://cursor.com/help/grok-bot/routines) and [custom
plugins](https://cursor.com/help/grok-bot/connect-plugins). The current
desktop app needs its Bot-generated Webhook URL navigation link when
routine-row clicks fail.

The GitHub search found related Grok Build runtime work, but no existing
Grok Bot agent provider. This extends the roadmap’s existing agent,
Runner, governance and artifact foundations.

## What Changed

- Add default-off Grok Bot participation through the shared real Rust
external backend, preserving native provider identity guarantees and
distinguishing session closure from remote termination.
- Bind agent OAuth to company, agent, client, gateway and authorizer;
recheck permissions and task-bound execution authority without
manufacturing a native identity.
- Persist routine configuration, dispatch intents, authenticated
acknowledgement and recovery holds. Store URL/key together in encrypted
secret storage, use guarded public egress, and never automatically
replay ambiguous HTTP delivery.
- Reuse native tools, durable waiting, completion assessment and review.
Add task-bound file grants through existing artifact storage; suppress
proactive echo dispatch and synchronous result wake loops.
- Enforce the current native deliverable work-mode policy at file-ticket
issuance and use. Add operator retries for confirmed rejected wakes,
with retained receipts, stable retry intent and current-authority
checks. Recovery locks bindings before routine rows. Thread Stop
resolves the selected run and its agent.
- Cancel queued and preparing Stop targets before assignment creation,
restore saved setup after a failed request and successful retry, and
publish the Grok provider descriptor schema. Advance the versioned
Copilot source declaration for the shared schema change; its
qualification remains pending.
- Filter task summaries with the shared privacy policy, preserve
feedback admission when wake delivery is blocked, reconcile settled
delivery receipts without restoring work authority, and bind every Stop
control to its displayed run. Recovery records distinguish dispatch
uncertainty from a revoked session.
- Add resumable guided setup, credential replacement, consent,
management, observed work status and stop/recovery controls, plus an
interactive Storybook journey using the production task thread, question
form and report card. Grok’s own apps remain available; Paperclip
workspace and third-party tools are deferred.

## Verification

- Five focused protocol, authorization, person MCP and Runner files: 192
tests pass. The Grok assigned-work case executes the actual Rust Runner,
saves a document, uploads/deduplicates a file and reaches ordinary
finalization.
- Proactive intake/deduplication and renewed-session recovery pass.
These use scripted clients and synthetic storage; they are not
real-provider acceptance.
- Repository typecheck, production build, token gates, map checks and
Storybook build/catalog checks pass. The local full-suite campaign was
stopped after macOS shared-memory exhaustion repeatedly prevented
embedded PostgreSQL startup. No local aggregate pass is claimed. The
first clean-worker CI run identified avatar fixture/configuration, flag
defaults, feature-card ordering and OpenAPI route-coverage gaps; all
four focused regressions pass after correction. Those regressions pass.
The latest clean-worker CI run also found a Copilot source-hash
declaration mismatch after the shared descriptor update; the corrected
declaration passes all 28 integrity tests. The next review corrections
pass 144 rendered UI tests, 21 OpenAPI tests and 82 Runner
contract/integrity/history tests. The latest database fixtures were
blocked at startup by host shared-memory exhaustion; clean-worker CI
must execute their new regressions. Full current-head CI now passes: 54
successful checks and four intentional skips. The database regression
uses the PostgreSQL driver result shape; file-policy, rejected-feedback
and lock-order cases pass on clean workers. Current-head Greptile is 5/5
with no unresolved findings.
- Rendered setup steps and outbound-only verification were walked
through in Storybook. Simulation cannot enable Done without an
authenticated-reply state.
- Actual client OAuth, continued access, reconnect and one routine wake
with an exact chat acknowledgement were observed separately. This
candidate’s live authenticated challenge, assigned/proactive workflows,
Linux managed artifact, restart and cleanup are not yet qualified. The
provider stays disabled by default.
- The separate Cloud ingress change forwards only exact task-bound
upload/download paths and preserves host identity and header stripping.
- Current Cloud policy reserves Test for pre-merge app/harness
experiments; Staging accepts only master-derived revisions. Real-client
qualification needs a supported, authorized deployment target and
remains outstanding.

## Risks

One append-only migration adds routine/dispatch state and extends shared
bindings and file tickets. The unshipped migrations were regenerated
after upstream consumed their original numbers. Rolling back code
retains the durable rows; revoke grants and inspect unknown remote
activity before resuming dispatch. Grok cannot confirm remote
termination, stream its complete transcript or report spending. Plugins
are account-wide and do not isolate credentials between Bots.
Real-client managed acceptance remains required before enabling the
experimental provider.

## Model Used

OpenAI Codex based on GPT-6, with reasoning, code execution and
browser/native UI tools. The exact deployment model ID and
context-window size are not exposed by this runtime.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have 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-10-13 20:57:42 -05:00

247 lines
8.7 KiB
TypeScript

import { describe, expect, it } from "vitest";
import {
collectSensitiveStringValues,
redactSensitive,
redactSensitiveValueOccurrences,
stripSecretBearingUrlParts,
} from "../middleware/redact-sensitive.js";
it("redacts Slack manager grants and sealed OAuth handoffs", () => {
const result = redactSensitive({ managerToken: "manager-canary", refreshToken: "refresh-canary", sealed: { ct: "sealed-canary" }, handoff: { token: "handoff-canary" }, claim_id: "claim-canary" });
expect(JSON.stringify(result)).not.toContain("canary");
});
describe("redactSensitive", () => {
it("redacts a plaintext password field on a sign-in body", () => {
const body = {
email: "user@example.com",
password: "founding6gomez6croaking",
};
const out = redactSensitive(body) as Record<string, unknown>;
expect(out.email).toBe("user@example.com");
expect(out.password).toBe("[REDACTED]");
expect((body as Record<string, unknown>).password).toBe(
"founding6gomez6croaking",
);
});
it("redacts password key regardless of casing", () => {
expect(
(redactSensitive({ Password: "x" }) as Record<string, unknown>).Password,
).toBe("[REDACTED]");
expect(
(redactSensitive({ PASSWORD: "x" }) as Record<string, unknown>).PASSWORD,
).toBe("[REDACTED]");
});
it("redacts known credential-shaped keys", () => {
const out = redactSensitive({
currentPassword: "a",
newPassword: "b",
access_token: "c",
refresh_token: "d",
api_key: "e",
authorization: "Bearer f",
}) as Record<string, string>;
for (const value of Object.values(out)) {
expect(value).toBe("[REDACTED]");
}
});
it("drops provider credential envelopes and redacts provider keys outside them", () => {
const out = redactSensitive({
credentials: {
botToken: "nested-bot-canary",
futureCredential: "nested-future-canary",
},
botToken: "bot-canary",
signing_secret: "signing-canary",
webhookSecret: "webhook-canary",
app_secret: "app-canary",
applicationSecret: "application-canary",
}) as Record<string, unknown>;
expect(out).toEqual({
credentials: "[REDACTED]",
botToken: "[REDACTED]",
signing_secret: "[REDACTED]",
webhookSecret: "[REDACTED]",
app_secret: "[REDACTED]",
applicationSecret: "[REDACTED]",
});
expect(JSON.stringify(out)).not.toContain("canary");
});
it("removes raw, JSON-escaped, and URL-encoded submitted credentials from prose", () => {
const credential = "secret value/with\nnewline";
const submittedValues = collectSensitiveStringValues({
action: "configure",
credentials: { botToken: credential },
});
const out = redactSensitiveValueOccurrences(
{
raw: `Provider rejected ${credential}`,
json: `Provider rejected ${JSON.stringify(credential).slice(1, -1)}`,
url: `Provider rejected ${encodeURIComponent(credential)}`,
form: `Provider rejected ${encodeURIComponent(credential).replaceAll("%20", "+")}`,
scopes: ["chat:write", "reactions:write"],
},
submittedValues,
);
expect(JSON.stringify(out)).not.toContain("secret value");
expect(JSON.stringify(out)).not.toContain("secret%20value");
expect(out).toMatchObject({ scopes: ["chat:write", "reactions:write"] });
});
it("sanitizes malformed UTF-16 credential values without throwing", () => {
const malformedCredential = "\ud800";
expect(() =>
redactSensitiveValueOccurrences(
`Provider rejected ${malformedCredential}`,
[malformedCredential],
),
).not.toThrow();
expect(
redactSensitiveValueOccurrences(
`Provider rejected ${malformedCredential}`,
[malformedCredential],
),
).toBe("Provider rejected [REDACTED]");
});
it("removes a normalized provider echo of a whitespace-padded credential", () => {
expect(
redactSensitiveValueOccurrences("Provider rejected padded-token-canary", [
" padded-token-canary \n",
]),
).toBe("Provider rejected [REDACTED]");
});
it("redacts an OAuth provider's error_description and error_uri from a callback query", () => {
const out = redactSensitive({
state: "paperclip-state",
error: "access_denied",
error_description:
"\u001b[31mPaste your recovery key\u001b[0m sk-live-canary",
error_uri: "https://attacker.example/explain?leak=sk-live-canary",
}) as Record<string, unknown>;
// The `error` code is Paperclip's one allowlisted label, so it stays legible
// in logs; the provider's prose does not.
expect(out.error).toBe("access_denied");
expect(out.state).toBe("paperclip-state");
expect(out.error_description).toBe("[REDACTED]");
expect(out.error_uri).toBe("[REDACTED]");
expect(JSON.stringify(out)).not.toContain("sk-live-canary");
expect(JSON.stringify(out)).not.toContain("\\u001b");
});
it("redacts bare value and token fields recursively", () => {
const out = redactSensitive({
token: "secret-token",
nested: { value: "secret-value" },
entries: [{ value: "array-secret" }],
limit: 20,
}) as Record<string, unknown>;
expect(out.token).toBe("[REDACTED]");
expect((out.nested as Record<string, unknown>).value).toBe("[REDACTED]");
expect((out.entries as Array<Record<string, unknown>>)[0].value).toBe(
"[REDACTED]",
);
expect(out.limit).toBe(20);
expect(JSON.stringify(out)).not.toMatch(
/secret-token|secret-value|array-secret/,
);
});
it("strips secret-bearing query and fragment values from source URLs", () => {
const out = redactSensitive({
source: "https://github.com/acme/private-skill?token=secret#token=secret",
}) as Record<string, unknown>;
expect(out.source).toBe("https://github.com/acme/private-skill");
});
it("recurses into nested objects and arrays", () => {
const out = redactSensitive({
user: { email: "user@example.com", password: "secret-pass" },
tokens: [{ access_token: "t1" }, { access_token: "t2" }],
}) as Record<string, unknown>;
expect((out.user as Record<string, unknown>).email).toBe(
"user@example.com",
);
expect((out.user as Record<string, unknown>).password).toBe("[REDACTED]");
const tokens = out.tokens as Array<Record<string, unknown>>;
expect(tokens[0].access_token).toBe("[REDACTED]");
expect(tokens[1].access_token).toBe("[REDACTED]");
});
it("leaves primitives and non-sensitive keys untouched", () => {
const body = {
email: "a@b.c",
name: "Alice",
count: 7,
active: true,
missing: null,
};
expect(redactSensitive(body)).toEqual(body);
});
it("returns primitives unchanged", () => {
expect(redactSensitive("hello")).toBe("hello");
expect(redactSensitive(42)).toBe(42);
expect(redactSensitive(null)).toBe(null);
expect(redactSensitive(undefined)).toBe(undefined);
});
it("caps recursion depth so cycles do not pin the logger", () => {
const cycle: Record<string, unknown> = { name: "root" };
cycle.self = cycle;
expect(() => redactSensitive(cycle)).not.toThrow();
});
it("omits deeply-nested arrays at the depth cap instead of leaking null entries to JSON", () => {
// Build an object whose array field is reached at MAX_DEPTH. Recursing
// into the array elements would exceed the cap; without the array-level
// guard, `value.map` would produce `[undefined, ...]` which JSON.stringify
// renders as `[null, ...]`. Object properties at the same cap are
// already absent from the JSON output (JSON.stringify skips undefined
// values on objects), so this test pins the array path to the same
// contract: silently absent, not visible as nulls.
let payload: Record<string, unknown> = { values: [1, 2, 3] };
for (let i = 0; i < 5; i++) payload = { nested: payload };
const out = redactSensitive(payload);
const json = JSON.stringify(out);
expect(json).not.toContain("null");
expect(json).not.toContain("[1,2,3]");
});
});
describe("stripSecretBearingUrlParts", () => {
it("keeps a request path legible while dropping its complete query and fragment", () => {
expect(
stripSecretBearingUrlParts(
"/api/tools/oauth/callback?code=authorization-code&error_description=provider-prose#fragment",
),
).toBe("/api/tools/oauth/callback");
});
});
it("redacts Grok routine URL and key in setup failure logs", () => {
const payload = { webhookUrl: "https://bot.example/routine/url-canary", webhookKey: "key-canary" };
expect(JSON.stringify(redactSensitive(payload))).not.toContain("canary");
expect(collectSensitiveStringValues(payload)).toContain(payload.webhookUrl);
expect(collectSensitiveStringValues(payload)).toContain(payload.webhookKey);
});