Preparing the route, source-backed state, and recovery controls.
WorkspaceEvidenceRecovery
CRUX for upstream deal teams
Get CRUX working in your AI app.
Add upstream deal analysis to Codex or Claude Code. Choose your app, ask it to handle setup, then try a fictional deal.
CRUX Decision 0.7.0 · Local plugin · Hosted tools are optional
Which app do you use?
Choose your app to see the next step. No private GitHub access is needed.
Access and cost: the ZIP download needs no CRUX sign-in. Your AI app’s account, plan, usage charges, and organization policies still apply. Optional hosted CRUX tools require separate access; ask about access and pricing.
Try a deal without uploading any files.
After confirming installation, paste this fictional example into a new conversation. No confidential documents or hosted-tool connection are needed.
Read or select the text
What a useful sample answer should show
PDP PV-10 / asking price: $18m / $25m = 72%. Price / seller-stated annual operating cash flow: $25m / $4m = 6.25×. These are screening proxies, not investment returns or the share of total asset value attributable to PDP.
The response should explain what the missing reserve, ownership, cost, and abandonment evidence prevents it from concluding. It should identify the three most useful evidence requests. Matching the arithmetic alone does not prove the plugin was used.
Ready for your own deal?
Start a new conversation in the same app. Attach a teaser, earnings package, or reserve report using the attachment control, or give the app access to your deal folder. Then send:
The local plugin and sample work without a CRUX login or token. Hosted calculations and saved context require a separate connection and access. Review the permissions and access terms before connecting.
Your AI app handles files you give it under its own settings. Connecting hosted tools can send selected calculation inputs or source-linked facts to CRUX.
Advanced setup: ZIP download and technical instructions
For users comfortable with Python and command-line tools. Guided setup above uses the same public package. Neither route requires access to the private source repository.
Read and verify the helper using the digest in the guided setup request before running it. In Terminal, change to the folder containing the helper, then use the command for your app below. Python 3.9+ and that app’s command-line tool must be installed.
Local plugin
Claude Code
0.7.0 stable package
CRUX Decision provides 5 public skills backed by 97 upstream methods. Download and load the local package in Claude Code; host-specific task execution remains a separate check.
Authentication
The plugin itself runs locally and does not require a CRUX credential. Connect the hosted MCP separately only when the workflow needs CRUX-hosted tools or saved context.
Access profile
Local plugin files use the host workspace. Any connected CRUX credential determines only the hosted MCP authority.
Setup
Download, read, and verify the public setup helper using the guided setup request above.
Run the copied Python command in the folder containing the helper. It downloads the package and installs persistently through Claude Code’s plugin manager.
Restart Claude Code, open /plugin, and check Installed for CRUX Decision before starting a new task.
Success check
Confirm the five public CRUX Decision skills appear in the host.
Ask one first-look question and check that the relevant skill is used.
Removal, revocation, and limitation
Remove: Disable or unload crux-decision. If hosted MCP was connected separately, remove it and revoke its credential separately.
Current boundary: Claude Code package compatibility is provided through the local plugin path; this page does not claim a verified Claude model task or Cowork installation.
The user can revoke an individual key from /connect; the database row is marked revoked.
This profile can read the caller’s authorized deal, artifact, and receipt records. It is not an anonymous public key.
partner_own_context
Partner read plus own-context write
crux_partner_…
A CRUX owner mints this stateless, expiring HMAC-signed token for a named partner.
Scopes
read:engines · read:skills · write:own_context
Write boundary
write:own_context permits create, enrich, and underwrite operations only inside that token’s isolated partner tenant.
Revocation
There is no individual-token revocation list. Stop access by waiting for expiry or rotating the shared signing secret, which invalidates every token signed with it.
This is not read-only. It does not grant write:deals, cross-tenant access, lab, task, export, or admin scopes.
Other hosts, legacy routes, and portable execution details
Qualification in progress
Check each host’s connection path.
These hosted and legacy paths need their own registration or local setup.
Hosted remote server
Claude
Registration and live call proof required
The production HTTPS endpoint, OAuth consent, and a read-only CRUX MCP call are verified. Claude-host-specific add, authorize, discovery, and call evidence remains the final route receipt.
Authentication
Use OAuth/DCR for authenticated hosted use. A static bearer handoff is a fallback for local clients, not a supported hosted-connector field.
Access profile
Production OAuth has proven the read-only profile. Keep Claude-host support qualified until its own end-to-end receipt is captured.
Setup
Open Claude’s connector settings and register a custom remote MCP server.
Enter the canonical production endpoint and complete OAuth consent in Claude.
Do not paste a CRUX bearer token into chat, a URL, or an unsupported static-header field.
Success check
resources/list or tools/list proves discovery only.
Capture an authenticated tools/call receipt with the same endpoint and credential before claiming execution.
Removal, revocation, and limitation
Remove: Remove or disable the remote server in Claude, then revoke the OAuth grant or token at its issuer.
Current boundary: The CRUX OAuth and MCP service are live; this card does not yet claim a Claude-host-specific tools/call receipt.
Read or select the text
Local work and connected tools
Local skills guide the host; connected tools are optional.
The plugin adds upstream methodology to the host’s native work. A separately connected CRUX MCP offers hosted discovery and run_skill or run_skill_bundle under the caller’s access profile; downstream writes and external or binding actions are authorized separately.
Ask for the upstream outcome; the host uses relevant CRUX Decision skills and its available native tools.
If connected CRUX tools are needed, call run_skill or run_skill_bundle under the caller’s profile.
Authorize a downstream write, external send, or binding action separately when the workflow requests one.
The plugin does not contain hosted CRUX credentials or require the optional local artifact helper. When CRUX MCP is connected, run_skill and run_skill_bundle execute server-side under the caller’s profile.
Optional CRUX tools
Connect MCP when the task needs hosted CRUX execution.
The plugin adds upstream methods to host-native work. The connected CRUX MCP offers hosted methods under the caller’s access profile.
run_skill and run_skill_bundle are supplied by the connected CRUX MCP.
Without MCP, host-native analysis and artifact authoring remain available.
External sends and binding actions keep separate authorization; they do not suppress supported analysis or a working artifact.
Generated from committed product, workflow, MCP exposure, scope, and gate registries.