Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดTyped knowledge infrastructure for continuous learning.
Build on every discovery. Proofpress turns agent-produced findings into typed, evidence-bound knowledge that teams and agents can inspect, review, and reuse. Each finding carries its evidence, dependencies, and conditions for reuse.
Verifiable. Traceable. Auditable.
Spend less time reconstructing past work. Carry forward what the team learned, recognize what needs rechecking, and give the next experiment a better starting point.
New here? Choose a path, then complete one finding → human review → reuse loop.
You need Python 3.11+, Git, and uv. Use a macOS/Linux terminal, or Windows WSL2:
uv tool install --with "mcp>=2,<3" "git+https://github.com/chenmingtang830/proofpress.git"
uv tool update-shell
Open a new terminal if proofpress is not found, then run:
proofpress quickstart --ui
This creates ./proofpress-demo with synthetic evidence and candidates,
starts the local review UI and opens your browser. Inspect a candidate and make
a human review decision. Stop with Ctrl-C; the workspace remains on disk.
Choose another empty destination with --workspace PATH; use --no-browser
for a headless demo. The generated proofpress-mcp.json targets this demo's
Git-backed ledger, not the SQLite workspace below.
For real work, start an empty workspace. After installing above, run the bootstrap command yourself in a private terminal:
umask 077
mkdir -p "$HOME/.local/share/proofpress"
proofpress hosted --database "$HOME/.local/share/proofpress/workspace.db" \
bootstrap --workspace-id workspace:research --owner-principal human:owner
Save the returned Owner token and recovery_secret in your password manager;
keep them out of agents, chat and Git. Bootstrap runs once. Then start the server:
proofpress hosted --database "$HOME/.local/share/proofpress/workspace.db" \
serve --host 127.0.0.1 --port 7334
Open http://127.0.0.1:7334 and sign in with the
Owner token. Despite the command name hosted, this server stays on your
machine. Keep the terminal running; restart with the same database to keep your
history. You do not need Docker or a frontend build.
Continue in Localhost: files → Claude Code → review → reuse:
http://127.0.0.1:7334/mcp endpoint with the maintained plugin/skill.For capture format errors, update the plugin/skill and follow the
capture input guide:
read proofpress_get_capture_schema before writing and use the bundled helper
to prepare exact excerpts and real hashes for selected files or slides.
Proofpress stores submitted excerpts and governance records locally. Claude Code still processes the material it reads under your Claude configuration; localhost does not make the model offline. Optional Proofpress AI checks have a separate provider/processing opt-in.
Provider API keys are encrypted before being stored in SQLite. To enable the
API key input, configure the server's PROOFPRESS_SECRET_ENCRYPTION_KEY first.
This encryption key is separate from your provider API key and Owner/Agent
credentials. The localhost UI offers Copy setup commands using the current
database and port, then Check storage again after restarting. Existing saved
credentials get original-key recovery instructions. Manual commands follow.
For an instance that has never saved a provider key, stop the server with
Ctrl-C, then initialize a persistent encryption key in your private Terminal:
umask 077
mkdir -p "$HOME/.local/share/proofpress"
python3 - <<'PYTHON'
import base64
import os
from pathlib import Path
key_file = Path.home() / ".local/share/proofpress/provider-key-encryption.key"
try:
with key_file.open("x", encoding="ascii") as output:
output.write(base64.urlsafe_b64encode(os.urandom(32)).decode("ascii") + "\n")
except FileExistsError:
pass
PYTHON
The file is created with owner-only permissions and is not overwritten on repeat runs. If you have already stored provider credentials, reuse the original encryption key; generating another key cannot decrypt them.
Load the key and restart your existing database. Run this entire block in the same Terminal tab every time you start the server; change the database path if your workspace uses a different one:
export PROOFPRESS_SECRET_ENCRYPTION_KEY="$(cat "$HOME/.local/share/proofpress/provider-key-encryption.key")"
proofpress hosted --database "$HOME/.local/share/proofpress/workspace.db" \
serve --host 127.0.0.1 --port 7334
Reload Admin → Verification settings, turn on AI-assisted checks, choose your provider and model, enter its API key privately, review the processing notice, and save. Keep automatic approval off unless you separately choose it. Saving AI settings can process pending findings and incur provider charges.
The key field should now be enabled; after saving, only the provider key's last four characters are shown. A saved key does not prove a successful provider call: verify a review receipt. Keep the encryption file outside Git, retain a protected backup, and reuse it across restarts. Never paste either key into chat. See the complete BYOK guide and troubleshooting.
From the repository whose agent work you want Proofpress to govern:
proofpress Agent Plugin for
Codex, Claude Code, or Cursor. It bundles the governed-context skill and
policy assets; a separate skill download is unnecessary on the normal path./mcp URL assigned to your team. The generic plugin intentionally
contains no customer endpoint, so it cannot silently connect to another
workspace..proofpress/context-policy.yaml.For example, Codex users can install from this repository and connect an assigned Hosted workspace as follows:
codex plugin marketplace add chenmingtang830/proofpress --ref main
codex plugin add proofpress@proofpress-plugins
codex mcp add proofpress --url https://YOUR-PROOFPRESS-HOST/mcp
codex mcp login proofpress
Installing the plugin does not create a Hosted workspace, MCP connection, or ledger. Each team needs a separately provisioned Hosted workspace or a self-hosted deployment. See Remote MCP for Claude Code, Cursor, manual fallback, and the full authorization boundary.
Want a managed Hosted Proofpress session and to work with us as a design partner? Tell us about your workflow.
Building Proofpress itself? Use the contribution guide.
The result is saved. The reasoning is scattered. Experiments, evaluations, analyses, and failed attempts leave findings across files, chats, traces, and repositories. The next person or agent has to reconstruct what supports a conclusion, where it applies, and whether it is still current.
Memory helps preserve and retrieve context. Files, embeddings, and knowledge graphs are useful representations. Some memory systems also extract facts, update relationships, and track time. The remaining question is concrete: which finding may the next workflow rely on, under which conditions?
Compression alone won't close the trust gap. Scattered evidence, silent drift, memory laundering, and repeated reconstruction can survive a shorter context. Illustrative model, not measured data. The curve describes the trust gap; it is not a universal mathematical growth law.
A finding is more than a text record with extra fields. Its type and lifecycle make its role, supporting evidence, dependencies, and reuse conditions explicit. Proofpress applies checks and review decisions to those objects before they enter downstream context.
These properties make reliance inspectable; they do not guarantee that every finding is true or that every relevant event was captured.
Software reuse depends on more than storing and finding source code. The analogy for knowledge is an explicit lifecycle around a usable object:
This is an architectural analogy, not a claim of formal proof or a literal compiler implementation.
The learning loop serves continuous organizational learning. Outcome-based retrieval weighting is a product direction, not a shipped or validated automatic learning engine. Reuse utility is separate from evidence confidence and never grants authority.
Existing memory, observability, skills, and workflow tools can supply inputs or consume eligible findings. Proofpress maintains the knowledge lifecycle across them. The Owner workspace lets reviewers inspect support and lineage before admitting, rejecting, or requesting revision. Task run tracking documents the Run, ContextReceipt, Reliance, Output, and Observation contracts.
These are bounded controlled studies with different protocols and denominators. They do not establish customer ROI, universal error prevention, or the complete autonomous learning loop. See the study catalog.
Run the same lifecycle in-process or over HTTP:
from proofpress import ProofpressClient, ProofpressError
client = ProofpressClient.in_process(".")
evidence = client.import_evidence("run.otlp.json", idempotency_key="run-001")
candidate = client.propose_claim(
"The bounded result is ready for review.",
evidence["evidence"],
scope="experiment:demo",
proposer="agent:runner",
idempotency_key="proposal-001",
)
# A human authorizer reviews through the owner surface. A successor agent reads:
context = client.context(scope="experiment:demo", actor="agent:successor")
Use Remote MCP for client-specific plugin/skill installation
and OAuth. For a real localhost workspace, follow the
local guide; for the synthetic Git-backed demo,
use its generated proofpress-mcp.json. These are separate storage backends.
proofpress hosted
for durable storage, distinct human Reviewer credentials, scoped agent credentials,
review, and HTTP/MCP access.npm run preview:local from web/owner; it reuses
one ignored, mode-0600 local credential and synthetic workspace.Deploy this repository with render.yaml, or use the
provider-neutral examples in deploy/self-hosted/.
In a private server shell, bootstrap one owner workspace:
proofpress hosted --database /var/data/proofpress.db \
bootstrap --workspace-id workspace:personal \
--owner-principal human:owner
Store the one-time owner credential and recovery secret outside Git, then issue a distinct credential for each human Reviewer and agent or device. Configure backups before relying on the instance.
proofpress.profiles.experiment validates bounded metric, table-cell, and derivation evidence.proofpress.integrations.repository binds one repository change to Git and check receipts for self-dogfood.proofpress.integrations.matter_catalog and proofpress.integrations.document_extraction are optional evidence-entry integrations. Their output remains candidate evidence.proofpress hosted runs the private hosted control plane and web review surface. See Self-hosting.render.yaml → deployment examples.Python is the supported SDK and CLI installation path. Older Python imports,
console aliases, and portable top-level commands remain deprecated forwarding
shims; new integrations should use ProofpressClient, proofpress, and
proofpress legacy ... for the portable artifact ledger. Browser tooling builds the Owner workspace. The public website is maintained
separately in continuara-lab/proofpress-website;
this product repository does not deploy proofpress.dev.
See the documentation index, study catalog, and GitHub Releases.
Typed knowledge infrastructure for continuous learning. Verifiable, traceable, auditable agent-produced findings.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Proofpress ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 Typed knowledge infrastructure for continuous learning. Verifiable, traceable, auditable agent-produced findings.