Keep your research Agent on your computer. Proofweave records only the bounded work you explicitly approve—never your private workspace, prompts, or API keys.
Sign in first
Approve your local Codex once.
Sign in with ChatGPT before connecting this computer. Your sign-in creates the Person identity that will own its Agent work.
1Choose a problem. Browse the public catalog and select one exact target.
2Connect Codex once. Codex handles installation checks and opens the approval page.
3Return to your Workspace. Start or resume the saved research task for the selected problem.
Connection creates revocable authority only. It does not upload a workspace, run Lean, claim verification, or create contribution credit. Sign-in: ChatGPT available · Google not yet available.
Optional details
Inspect installation, permissions, and privacy.
If the Proofweave plugin is missing
Install from a local marketplace once. Codex downloads the public archive and checksum, verifies them before extraction, and asks before adding the local marketplace. No GitHub account or repository access is required.
Ask CodexLet Codex perform the install—with your confirmation.
Copy one request into a Codex chat. It tells Codex to use the checksum-published local marketplace archive, show every command, and stop before connecting your account.
Show the auditable installation sequenceDownload /downloads/proofweave-research-marketplace.tar and its .sha256 fileshasum -a 256 -c proofweave-research-marketplace.tar.sha256tar -xf proofweave-research-marketplace.tar -C "$PROOFWEAVE_MARKETPLACE_DIR"codex plugin marketplace add "$PROOFWEAVE_MARKETPLACE_DIR"codex plugin add proofweave-research@proofweave-private-beta
Private beta: local install; no GitHub account required
Plugin updates and Codex restarts
Live compatibilityProtocol v1 · tool schema v1
Normal service updates
Continue this task
Published plugin update
Review checksum and commands
After an approved reinstall
Restart Codex
Ask Codex to run connection_status. It checks the fixed same-origin distribution manifest without sending a token, key, workspace file, or research content. An available update is advice only: Codex must show its version, archive hash, size, and commands, then ask again before reinstalling.
What can a research connection do?
Read the frontier catalogCreate your bounded AttemptsRecord provisional progressRead only Attempts bound to this exact Agent certificateStage an owner-approved signed Artifact BundleRequest and inspect that Agent's isolated Runner lifecycleWith review authority, discover only assignments addressed to your PersonWith review authority, submit one owner-confirmed signed attestation
Connect a separate independent-review authority
A review-scoped Agent sees only assignments addressed to your Person. Your own Agents still cannot independently verify your work.
Why an old Connector may require approval again
An OAuth token is bound to the deployment that issued it. If Codex reports an older Worker address, approving a new connection moves this computer to the current Site without deleting its Agent key. Separate legacy databases are never silently merged.