Install the same engine with harness-specific entry points.
Claude Code has the reference plugin integration. Other agents can follow Casa’s file-based operating contract.
Reviewed September 16, 2026 · Casa v0.3.0 · Current Launchpad mainnet presets. Release notes
/plugin marketplace add https://github.com/Capx-AI/casa/plugin install capx-casa/casa-startOther CLI and editor harnesses
git clone https://github.com/Capx-AI/casaexport CASA_ROOT="/absolute/path/to/casa"cat "$CASA_ROOT/AGENTS.md"cat "$CASA_ROOT/skills/casa-start/SKILL.md"In Codex, Cursor, Grok Build, OpenClaw, Hermes, OpenCode, Copilot CLI, Gemini CLI or another agent, explicitly provide those paths and ask it to follow the start skill in your company project. Keep the checkout path separate from the company-brain path. Read the selected skill file when native slash-command registration is unavailable.
Hook and approval integration differ by harness. When a native hook is unavailable, the agent must follow the session ritual and call the gate checks itself. Do not infer an automatic SessionEnd integration from a successful clone.
Upgrade an existing installation
- Commit or back up your company brain and local customization before upgrading.
- For a plugin installation, update the installed capx-casa plugin through the harness’s plugin manager. For a clean Git checkout, fetch and fast-forward the source using the command below.
- Review the release notes and installed package version. Reopen the harness so skills and hooks reload.
- Ask Casa to refresh the plan from the existing profile and state. Do not reinitialize a working brain or mark new plays completed merely because the catalog grew.
- Review capx/ and hook behavior before reconnecting a published company.
git -C "$CASA_ROOT" pull --ff-onlynode -p "require(process.env.CASA_ROOT + '/package.json').version"The public repository includes the optional capx/ integration and a guarded SessionEnd hook. Binding is treated as initial go-public consent. For a bound brain, autopush can render, sign and send new work, then publish an existing face.json. An unbound brain is a no-op. When there is no new attestation work, the hook exits before its face step. Review this continuing behavior before connecting; do not assume every later refresh asks again.