CRUX workspace
Preparing the route, source-backed state, and recovery controls.
CRUX for upstream deal teams
Choose the work you need, connect Codex or Claude, and use one natural-language prompt. CRUX routes the specialist work privately, processes the VDR and native artifacts on your workstation, and keeps the answer, model, memo, deck, sources, and open items connected.
Stable local plugin. The direct package is the current validated path; hosted tools use a separate OAuth connection.
Recommended install path
The host card gives the exact install command, first-run prompt, and success check for your client.
Compact by design
Your host routes analysis, artifact creation, and package audit separately. Each focused skill loads the smallest private capability set and keeps specialist instructions out of the public routing surface.
The 22 intent routes are routing metadata—not 22 competing public skills.
Choose the job
You do not need to choose a skill, agent, route, or engine. Start with the outcome; CRUX selects the smallest specialist path required.
Turn a CIM, teaser, earnings package, or sparse first-look file set into a supported recommendation and the few gaps that can change it.
First-look recommendation · kill gates · asset and earnings view · evidence requestsReconcile production, reserves, ownership, pricing, development, valuation, funding, and downside into one challengeable underwrite.
Buyer model · sensitivities · valuation bridge · diligence prioritiesCarry the supported case into an IC memo, workbook, deck, map, source register, and a clear review-ready status.
Memo · model · deck · map · source trail · QA summarySupported hosts
Codex and Claude package discovery are verified. The local plugin uses your workspace; hosted CRUX tools use a separate OAuth connection. Read each card’s channel note: the direct ZIP and official GitHub marketplace resolve the same reviewed 0.3.1 package.
Curated plugin
The exact 0.3.1 ZIP, three focused automatic skills, one explicit compatibility alias, ten private capability contracts, local VDR intake, and plugin-local artifact engine are validated as one package.
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.
Local plugin files use the host workspace. Any connected CRUX credential determines only the hosted MCP authority.
Remove: Disable or uninstall crux-compact-plus. If hosted MCP was connected separately, remove it and revoke its credential separately.
Current boundary: 0.3.1 is the stable local-first package. Its bounded six-family response bracket and package gates pass; fresh Claude model execution, fresh artifact rendering, a rich geometry-backed deal package, and Copilot-native packaging remain separate evidence tracks.
First run
Natural language is the interface. Missing evidence should narrow affected conclusions—not stop supported work.
Screen these upstream deal files. Lead with the recommendation, quantify the decision hinges, and give me the three evidence requests that matter most.
Expected response order: recommendation → decisive figures → contradictions and downside → open evidence → next action. Artifact requests add paths and one authoritative readiness state.
Hosted tools
Native host skills can guide the work locally. Connect the CRUX MCP when you need optional hosted tools or saved compact context. VDR binaries, native models, generated artifacts, and QA rasters stay on your workstation; MCP receives only compact source-linked facts or calculation inputs when the user chooses that path.
Production OAuth + read-only MCP call verifiedEvaluated stable release
The stable compact plugin is a separate, evaluated local-first package: three focused automatic skills route analysis, artifact creation, and audit work to ten private capabilities and a bundled artifact engine.
This is not the legacy 97-skill plugin or the hosted MCP product. 0.3.1 is the stable local-first package; the response result remains n=1 per arm and family with one grader, no fresh artifact rendering was performed for RC3, and rich deal-artifact custody per target host/model plus Copilot-native packaging remain separate evidence tracks.
Official main: 0.3.1 · f0b622ceda07caa6c25fccbab7aa67d45c4aaf37
sha256 9cddb047908805581939da47b1d7cb490235cf4942e8e989af2b8c0eef2ab04cAccess details
The default connected-user path is read-only. Partner own-context writes require a separately issued credential and never grant general deal writes.
connect_read_only
crux_sk_ro_…A signed-in user mints this database-backed key at /connect. Clerk and the application database must be available.
This profile can read the caller’s authorized deal, artifact, and receipt records. It is not an anonymous public key.
partner_own_context
crux_partner_…A CRUX owner mints this stateless, expiring HMAC-signed token for a named partner.
This is not read-only. It does not grant write:deals, cross-tenant access, lab, task, export, or admin scopes.
Qualification in progress
These paths remain visible for technical evaluation, but they are not presented as equivalent to the verified Codex and Claude package paths.
Hosted remote server
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.
Use OAuth/DCR for authenticated hosted use. A static bearer handoff is a fallback for local clients, not a supported hosted-connector field.
Production OAuth has proven the read-only profile. Keep Claude-host support qualified until its own end-to-end receipt is captured.
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.
Skill use · discover and run
A connected CRUX MCP provides skill discovery and the hosted run_skill and run_skill_bundle entry points. Those entry points return supported analysis and working artifacts; downstream writes and external or binding actions are authorized separately.
The portable bundle contains the compact skill system, bundled deterministic artifact renderer, and local validators; it does not contain hosted CRUX credentials or server-side execution. When CRUX MCP is connected, run_skill and run_skill_bundle execute server-side under the caller’s profile.
Portable skill bundle · local checks
Repository operators can run pnpm skill:export --skill <id> --target dist/agent-skills. The bundle includes local validators and a dependency manifest.
run_skill and run_skill_bundle are supplied by the connected CRUX MCP.Generated from committed product, workflow, MCP exposure, scope, and gate registries.
https://crux.sunya.ai/api/mcp