Connectors
Connector Wall is the external connector control surface for Próx OS. It belongs
Position
Connector Wall is the external connector control surface for Próx OS. It belongs
under /app-connectors because it models provider context, permissions, import
readiness, sync direction, cache deletion, and source provenance.
It complements the existing connector-specific apps such as Calendar, Email,
Contacts, Files, Notes, Wallet, Game Connectors, Books Connectors, Music
Connectors, Movies Connectors, and Airtable Connectors. It is not a duplicate
/app-user/connectors route.
Current Surface
- Route:
/app-connectors/wall - Package export:
@prox-os/user-connector-apps - Source:
packages/apps/user-connector-apps/src/apps/user-connectors/connector-wall/ - Runtime kind:
os-package - Current status: mock UI with typed connector cards
Connector Wall models GitHub, Gmail, Google Calendar, Google Contacts, Cloudflare, Neon, Figma, Obsidian, Notion, NocoDB, n8n, Dify, PostHog, Web3Forms, and R2 Object Storage.
Each connector record includes status, auth mode, data objects, permissions, last sync label, category, and risk level.
Security Boundary
- No secrets in repository files.
- No real OAuth in the UI-only milestone.
- No provider API calls from the app package.
- Connector status is mock unless backed by a real integration.
- Future connector implementations must go through app contracts, permissions, audit logs, and explicit user confirmation for writes.
Future Contract
Production connectors should use provider-specific adapters, token vault storage, scoped sync jobs, webhook ingestion, MCP resources and tools where appropriate, and Activity events for auditability.
AI surfaces should receive scoped summaries or tool outputs, not uncontrolled raw provider data.