Capx
Install Casa
Getting started

Quickstart

Install Casa, open your first session, and approve an operating map in under five minutes. Nothing becomes the plan of record until you confirm it.

Prerequisites

  • Claude Code for the reference experience, or any supported harness (see Install in any harness)
  • Node 20 or later for the deterministic engine
  • A project folder: empty for a new company, or the repository your company already lives in
Note: No account, no waitlist

Casa is MIT licensed and installs from the public repository. Interactive use runs on your existing harness subscription; Casa never resells or hosts model inference.

  1. 1

    Add the marketplace

    Point Claude Code at the public Casa repository. The URL is centralized so it can move with the official organization without breaking installs.

    Add the Casa marketplaceclaude code
    /plugin marketplace add https://github.com/Capx-AI/casa# ✓ Marketplace added: capx-casa
  2. 2

    Install the plugin

    This loads Casa's skills, agents, hooks, playbooks, and the local deterministic engine into your environment.

    Install Casaclaude code
    /plugin install capx-casa# ✓ capx-casa installed# 174 playbooks · 14 operators · review panels · engine
  3. 3

    Start the company

    Run the start command inside your project. An empty folder begins a short interview, typically six to nine exchanges. An existing project gets scanned read-only first, and Casa asks only for the context the repository cannot supply.

    First sessionclaude code
    /casa-start# Reading the project … done (read-only)# Business type: b2b-saas · Stage: pre-launch# 42 applicable playbooks · 11 ready now# Draft operating map prepared for review
  4. 4

    Approve the map

    Casa presents the company profile, the binding constraint, and the first operating plan. Correct anything it inferred wrong; nothing is written as the plan of record until you approve.

    Tip: Draft shown midway

    For a new idea, Casa shows a draft plan midway through the interview so you can correct direction early instead of at the end.

  5. 5

    Work the loop

    From here, every session opens on what is true, what changed, what is blocked, and the next move. The commands you will use most:

    CommandWhat it does
    /casa-startSet up or re-onboard the company in this project
    /casa-mapShow the personalized build map: levels, tracks, and status
    /casa-nextThe single next best action, with the reasoning for it
    /casa-priorityA ranked briefing of where the company is and what to focus on
    /casa-reviewRun a critic panel over an artifact, a plan, or a decision
    /casa-loopsReview recurring obligations and what is due
    /casa-boardThe operating board: department lanes under the binding constraint
    /casa-approvalsPending approvals, and the per-department autonomy dials

    Casa ships 26 commands in total. /casa-help lists them.

    CASA 01SESSION OPENING STUDYLOCAL TERMINAL / CURRENT STATE
    CAPX CASASESSION OPEN
    STATE SOURCEcompany-brain/
    MODEFounder present
    WRITE PATHLocal files
    === Capx Casa ===READING CURRENT STATE
    North star
    retained active teams
    Do or die
    onboarding loses intent after setup.
    Next
    First-value path (Product)
    Waiting on you
    nothing
    Loops due
    weekly customer signal
    ›/casa
    How a session opens: north star, the do-or-die, the next move, and what is waiting on you.

What Casa writes

After your confirmation, Casa creates a company-brain/ directory beside your product code. It scans existing files read-only and never rewrites them. See Company brain for the full layout.

Next steps

Core conceptsThe vocabulary the whole system uses.
Install in any harnessThe same three steps in Codex, Grok Build, OpenClaw, Hermes, or with no harness at all.
Governance and gatesWhat runs automatically and what always stops.
PreviousOverviewNext Core concepts