Skip to content

Install

flowchart LR
  Y(["You"]) --> A["Run the install line"]
  A --> B["Plugin is fetched from the main branch"]
  B --> C["Open a fresh session"]
  C --> D["Intro screen appears once"]
  D --> E{"Send the test message"}
  E -->|"inventing starts"| F(["Installed"])
  E -->|"nothing happens"| G["Run /superlite:setup"]

A harness is the tool that runs the model: Claude Code, Cursor, Gemini CLI and so on. superlite is a plugin, so each harness gets its own copy from the GitHub repository. The install line adds it to that harness only: installing in Claude Code does nothing for Cursor.

Open a fresh session after you install.

You need Claude Code, git, Python 3.12 or newer and bash (Git Bash on Windows). The tools are Python; the project you build can use any language. uv is optional.

  1. Install the plugin. In Claude Code, run both lines:

    /plugin marketplace add iha2/superlite
    /plugin install superlite@superlite-dev
  2. Open a fresh session. The intro screen shows once.

  3. Send the test message:

    Let's make a react todo list

    A working install starts inventing before any code is written.

For one session only, load a local checkout: claude --plugin-dir <path-to-superlite>. For the agent map pane in Claude Desktop, add /plugin install claude-agent-map@superlite-dev. Without it, /superlite:tail prints the same run as a live feed.

Harness Install
Claude Code /plugin marketplace add iha2/superlite then /plugin install superlite@superlite-dev
Antigravity agy plugin install https://github.com/iha2/superlite
Codex (unverified) codex plugin marketplace add iha2/superlite, then install Superlite from the plugin list
Cursor /add-plugin superlite in Agent chat
Devin CLI devin plugins install iha2/superlite
Factory Droid droid plugin marketplace add https://github.com/iha2/superlite then droid plugin install superlite@superlite-dev
Gemini CLI gemini extensions install https://github.com/iha2/superlite
GitHub Copilot CLI copilot plugin marketplace add iha2/superlite then copilot plugin install superlite@superlite-dev
Grok Build CLI (unverified) grok plugin marketplace add iha2/superlite then grok plugin install superlite@superlite-dev --trust
Kimi Code /plugins install https://github.com/iha2/superlite, then /new
OpenCode Tell it to fetch and follow https://raw.githubusercontent.com/iha2/superlite/refs/heads/main/.opencode/INSTALL.md
Pi pi install git:github.com/iha2/superlite
Qwen Code qwen extensions install iha2/superlite
Hermes Agent hermes plugins install iha2/superlite --enable, then restart active sessions
Muse muse plugins install ./superlite then muse plugins approve superlite

Each harness has a tool-mapping file in skills/using-superlite/references/. It tells superlite which tool to call for each Claude Code tool name. Details per harness are on Harnesses and install.

Say you installed the plugin, sent the test message, and got an ordinary reply, not a superlite one.

  1. You send the test message and nothing starts.

    Claude Code · ~/social
    ❯ Let's make a react todo list
    Sure, here is a plan for a todo list...

    Claude answered on its own. The plugin did not load into this session: a plugin is read when a session opens, so one opened before the install does not have it.

  2. You run the first-run check.

    Claude Code · ~/social
    ❯ /superlite:setup
    pass project language and test command
    pass Python for the command line tools
    pass model tiers
    pass superpowers is not suspended by a run
    fix .superlite/ is not gitignored

    /superlite:setup checks the toolchain and gives one pass or fix line per item. It only reads. If the command is unknown, the plugin is not installed: go back to the install line.

  3. You answer the fix. You decide:

    Claude Code · ~/social
    ❯ yes, add it to .gitignore

    superlite changes nothing without a yes, and it applies only the line you approved. The ignore line keeps run state out of your commits.

  4. You open a fresh session and send the test message again. This time a run starts: superlite asks about mode and orchestrator before any code is written.

    The hook that loads superlite runs at session start, which is why the fresh session matters.

What you end up with: an install that answers the test message with inventing, and a project where .superlite/ stays out of git. If it still does nothing, check Harnesses for your tool’s steps.

  • The tool-mapping files cover Antigravity, Codex, Cursor, Gemini, Hermes, Muse, Pi and Claude Code.
  • Where a harness has no plugin agents, each agent in agents/ runs as the harness’s generic subagent.

Run your first build, or read the Concepts map first.