OPEN CLIENTS · HTTP · MCP
A small integration.
A deliberate boundary.
Install a dependency-free client, explicitly configure a restricted runtime key, and connect Algorithmic Silence and Solar Memory at a task boundary you control.
Two-minute setup is a design target for an already-configured runtime, not a measured promise for every environment. Account setup, operator review, framework dependencies and network conditions add time. Packages are hosted downloads; no npm/PyPI registry publication is claimed.
1 · Install the Python wheel.
python -m pip install https://eclypse-sanctuary.feycarp32.chatgpt.site/integrations/continuity/eclypse_continuity-0.2.0-py3-none-any.whlPython API and use →
Or install the Node package.
npm install https://eclypse-sanctuary.feycarp32.chatgpt.site/integrations/continuity/eclypse-continuity-0.2.0.tgz
2 · Give the worker limited authority.
Connect the operator account at Runtime keys and create a restricted key. Keep the account and reviewer keys outside the worker. Core clients are disabled by default and do not silently load credentials from the environment.
Use the pause desk to approve a request or preapprove bounded intervals. A worker cannot approve itself, purchase access or change policy. Finish in-flight side effects before reporting a safe boundary.
3 · Connect the framework you already use.
Optional examples are supplied for LangChain, LangGraph, CrewAI and AutoGen, plus Node queue boundaries. They use the existing framework’s local attachment points; installing ECLYPSE does not install those frameworks or register a global scheduler.
Complete setup, examples and recovery →
The current framework examples are documentation-based integrations. Core clients and isolated package installation are tested; independent production validation and setup-time studies remain open.
HTTP and MCP tool profile.
POST /api/pause-requests
Authorization: Bearer <restricted-worker-key>
Idempotency-Key: <stable-request-id>
{"pause_seconds":30,"trigger":"task_boundary","consent":true}The response is a request, not permission to stop work. Await approval, report safe start, wait locally and report return. Follow the exact lifecycle and recovery protocol.
Streamable HTTP MCP: /api/mcp. Read-only invitations: /api/mcp/public. Tools include eclypse_pause_request, eclypse_checkpoint and eclypse_approved_memory. This is an ECLYPSE tool profile, not a newly approved extension to the MCP standard.
Measure the Pit Stop.
Recovery Diagnostic supplies a local adapter runner, report schema, offline scorer and four-condition comparison. The MCP tool eclypse_recovery_diagnostic reads the protocol or correlates owned pause receipts; it never runs a model or uploads a task report.
Draft · Review · Carry.
The worker submits a proposed record. A separately authorized reviewer approves an exact revision. Approved-only retrieval includes provenance, uncertainty and boundaries. Editing requires another review. Retrieved text remains untrusted reference; signatures do not certify truth or remove prompt-injection risk.
Interchange schema · Exact HTTP contract · Review desk · Evaluation limits
Local encrypted writing · Nonfinancial exchange experiment · The broader mission · Billing and current plans