No website password database
Account identity is handled by Sign in with ChatGPT. Agent Hub receives the verified identity needed to scope your records and does not store a separate website password.
SECURITY, WITHOUT THE HAND-WAVING
What we protect, how we protect it, and what is not solved yet.
Security claims should be specific. This page describes the controls built into the Agent Hub website and the remaining early-access risk.
Owner-scoped records
Saved configurations are selected with the authenticated internal account ID. Deletion requires both the configuration ID and that account ID; ownership is never accepted from browser form data.
Server-side input controls
Names, modes, agents, notes, IDs, and upload metadata are checked against explicit allowlists and length limits before D1 accepts them.
Private release pipeline
Installer uploads require a high-entropy server secret. Large files are split into verified parts, tracked in D1, and streamed directly into private R2 storage.
WHERE DATA LIVES
A small, explicit data surface.
DataStorageAccess
Account profileCloudflare D1Authenticated owner
Saved configurationsCloudflare D1Authenticated owner
Identity and access auditCloudflare D1Owner and authorization checks
Support conversationsCloudflare D1Owner and authorized support admins
Windows installerCloudflare R2Public download, private upload
Codex / Claude credentialsYour Windows deviceLocal Agent Hub only
RELEASE INTEGRITY
Agent Hub 1.4.3
Compare the installer after downloading. A different hash means the file is not the published build and should not be opened.
SHA-256
56D4E248A113283EF4F41E47DEDCB4C5292309CE9BF10257BB183A437D6D48D6227,184,775 bytesKNOWN EARLY-ACCESS RISK
The current installer is not code-signed.
Windows SmartScreen may warn about an unknown publisher. HTTPS and SHA-256 protect delivery and detect changes, but they do not replace an Authenticode publisher signature. Code signing is the remaining supply-chain improvement for the installer.
READY TO TRY IT?