mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-25 17:45:53 +01:00
## Thinking Path > - Paperclip manages AI agents and their work. > - Connections give agents governed access to external tools. > - Agents need durable memory across tasks and execution environments. > - Mem0, Zep, Supermemory, Cognee, and Honcho provide hosted memory tools. > - This pull request adds their setup flows behind an experimental toggle. > - It also delivers assigned MCP tools through the native remote Codex runner. > - Operators can connect a provider once and use the same governed tools locally or in Daytona. ## Linked Issues or Issue Description **Problem or motivation** The Apps catalog lacks a complete set of memory providers. Remote native Codex agents also need access to assigned managed MCP tools without receiving provider credentials. **Proposed solution** Add five memory connectors behind the disabled-by-default Experimental memory connectors setting. Use the existing connection setup and permissions UI. Default their tools to Allowed. Preserve company boundaries, operator permission changes, provider scopes, and audit attribution. **Alternatives considered** Direct provider credentials in each sandbox would duplicate setup and bypass the managed gateway. The remote runner instead uses its existing protocol channel to call the gateway on the server. **Roadmap alignment** This maintainer-requested experiment supports the Memory / Knowledge and Connected Apps roadmap areas. It adds provider connections without introducing a separate memory UI. Related connector authoring documentation is tracked in #13692; no duplicate memory-provider implementation was found. ## What Changed - Add provider definitions, official branding, and the experimental setting for all five providers. - Use OAuth for Zep and Supermemory, API credentials for Mem0 and Honcho, and a bundled Cloud API bridge for Cognee with no runtime downloads or subprocesses. - Default memory tools to Allowed and classify destructive actions explicitly. - Fix personal remote credential resolution and propagate provider tool errors. - Relay assigned managed MCP tools to remote native Codex through the runner protocol. Recheck current authority for each call and rotate stale tool contracts. - Add 21 Storybook states and complete OAuth walkthrough fixtures. - Document provider research, sanitized tool inventory, and live local and Daytona proof. ## Verification - Passed workspace typecheck: `pnpm -r typecheck`. - Passed production build: `pnpm build`. - Full local `pnpm test:run`: 13,273 passed, with failures from process/readiness timeouts under parallel load. Reran all 16 affected suites with one worker: 456 passed, leaving two macOS `/var` versus `/private/var` path assertions. Both passed with `TMPDIR=/private/tmp`. No test failures remain unverified. Latest-head remote CI passes all 54 checks (two optional Storybook jobs skipped). Greptile is 5/5 with no unresolved findings. - Latest Cognee gateway regression: 71 passed, including public deployment without a runtime host and immediate recovery after a provider error. Bundled bridge tests: 25 passed. - Browser setup and real agent tasks exercised all five providers. Mem0, Cognee, Zep, and Honcho have successful store/retrieve proof. - Supermemory now has scoped read/write consent. Local storage and real Daytona write, document read, and semantic recall passed; indexing completion was verified before claiming success. - All five providers were exercised through a real Daytona sandbox and its native runner MCP relay. Provider credentials remained on the server. The final bundled Cognee bridge also passed a fresh Daytona store/recall run. All disposable sandboxes were removed and verified absent after testing. - Storybook is rebuilt and contains the experimental toggle, catalog, setup, permissions, and error states. The Zep and Supermemory access steps advance correctly. ## Risks - Provider OAuth scopes and plan limits remain independent of Paperclip tool permissions. An Allowed tool can still be rejected by the provider. - Providers can queue memory indexing; save acceptance does not prove that semantic recall is ready. - Remote tool contracts must stay synchronized with current connection authority. Regression tests cover revocation and stale contracts. - This change has no database migration. Existing connections remain usable when the experimental catalog toggle is disabled. ## Model Used OpenAI Codex, GPT-6 Astra (`gpt-6-astra`), with reasoning, repository edits, code execution, and browser automation. The exact context window size is not exposed in this session. Live acceptance agents used `gpt-5.6-sol`. ## 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>
72 lines
2.4 KiB
JSON
72 lines
2.4 KiB
JSON
{
|
|
"schemaVersion": 1,
|
|
"slug": "cognee",
|
|
"name": "Cognee",
|
|
"description": "Build and recall shared graph memory from documents and conversations.",
|
|
"categories": [
|
|
"ai"
|
|
],
|
|
"branding": {
|
|
"logoUrl": "/brands/apps/cognee.png"
|
|
},
|
|
"urlPatterns": [
|
|
"https://*.aws.cognee.ai/*"
|
|
],
|
|
"docsUrl": "https://docs.cognee.ai/cognee-cloud/connections/cloud-mcp",
|
|
"setupPrerequisite": {
|
|
"title": "Cognee Cloud and a local runtime",
|
|
"description": "Use your Cognee Cloud tenant API URL and key. Paperclip's runtime host needs uv installed to run the official Cognee MCP client. Public deployments require a trusted MCP runtime host.",
|
|
"actionLabel": "Open Cognee API keys",
|
|
"actionUrl": "https://platform.cognee.ai/api-keys"
|
|
},
|
|
"methods": [
|
|
{
|
|
"key": "cloud-local",
|
|
"transport": "local_stdio",
|
|
"auth": "api_key",
|
|
"ownershipModes": [
|
|
"customer"
|
|
],
|
|
"whenToUse": "Connect your Cloud tenant through the official Cognee MCP client.",
|
|
"defaults": {
|
|
"templateKey": "paperclip.cognee-cloud"
|
|
},
|
|
"guidanceMd": "Copy the API Base URL and create an API key on Cognee's API Keys page. Use a Cloud workspace with an active subscription. Paperclip uses its bundled Cloud client; no extra runtime installation is required.",
|
|
"riskTier": "S3",
|
|
"label": "Connect Cognee Cloud",
|
|
"credentialFields": [
|
|
{
|
|
"key": "COGNEE_BASE_URL",
|
|
"label": "API Base URL",
|
|
"type": "text",
|
|
"required": true,
|
|
"secret": false,
|
|
"placeholder": "https://your-tenant.aws.cognee.ai",
|
|
"validation": {
|
|
"pattern": "^https://[a-zA-Z0-9-]+\\.aws\\.cognee\\.ai/?$",
|
|
"maxLength": 255
|
|
},
|
|
"helperMd": "Copy API Base URL from Cognee's API Keys page."
|
|
},
|
|
{
|
|
"key": "COGNEE_API_KEY",
|
|
"label": "Cognee API key",
|
|
"type": "password",
|
|
"required": true,
|
|
"placeholder": "Paste your Cognee API key",
|
|
"secret": true,
|
|
"helperMd": "Create a key in Cognee → API Keys. The key is shown once."
|
|
}
|
|
],
|
|
"keyPlacement": {
|
|
"location": "env",
|
|
"name": "COGNEE_API_KEY"
|
|
},
|
|
"consoleLinks": {
|
|
"keys": "https://platform.cognee.ai/api-keys",
|
|
"docs": "https://docs.cognee.ai/cognee-cloud/connections/cloud-mcp"
|
|
}
|
|
}
|
|
]
|
|
}
|