<div align="center">

cuecards

Your agent reads every skill you own, on every message. cue loads only the ones that project needs.

<p align="center"> <img src="https://raw.githubusercontent.com/opencue/cuecards/main/docs/assets/hero.svg" alt="cuecards — agent profile manager for Claude Code and Codex" width="820"> </p> <p align="center"> <a href="https://github.com/opencue/cuecards/stargazers"><img src="https://img.shields.io/github/stars/opencue/cuecards?style=for-the-badge&logo=github&label=%E2%AD%90%20Star%20this%20repo&color=yellow" alt="Star cuecards on GitHub"></a> </p> <p align="center"> <a href="https://www.npmjs.com/package/cue-ai"><img src="https://img.shields.io/npm/v/cue-ai?style=for-the-badge&logo=npm&logoColor=white&label=npm&color=cb3837" alt="npm version"></a> &nbsp; <a href="https://www.npmjs.com/package/cue-ai"><img src="https://img.shields.io/npm/dw/cue-ai?style=for-the-badge&label=downloads&color=2b3137" alt="npm downloads"></a> &nbsp; <a href="https://github.com/opencue/cuecards/blob/main/LICENSE"><img src="https://img.shields.io/github/license/opencue/cuecards?style=for-the-badge&label=license&color=4c1" alt="MIT license"></a> &nbsp; <img src="https://img.shields.io/badge/node-%E2%89%A520-339933?style=for-the-badge&logo=node.js&logoColor=white" alt="Node 20+"> &nbsp; <img src="https://img.shields.io/badge/telemetry-none-success?style=for-the-badge" alt="zero telemetry"> </p>

Install · How it works · Profiles · Multi-agent · FAQ · Contributing

</div>

---

Install

Already have an agent open? Paste this into Claude Code, Codex, Cursor, or whatever you use — it installs cue and sets up this project, asking before it touches anything:

Install cue (https://github.com/opencue/cuecards) on this machine and set it up
for this project.

1. Check Node >= 20 with `node --version`. If it's missing or older, stop and tell me.
2. Check whether cue is already installed: `command -v cue`. If it resolves, skip to 4.
3. Ask me before installing anything, then run: `npm install -g cue-ai`
4. Run `cue auto-detect --json`. Show me the profile suggestions it returns and what
   each one is for, and let me pick one — don't choose for me.
5. Run `cue setup --profile <the one I picked> --yes`. That pins the profile,
   installs the shim that makes `claude`/`codex` load it, and — if needed —
   appends a PATH line to my shell rc file (~/.bashrc, ~/.zshrc, or fish config)
   so the shim takes effect. It will not enable telemetry and will not install
   third-party skills. If it exits non-zero, stop and show me the output
   instead of continuing to step 6.
6. If it prints PATH guidance, show it verbatim — the shims do nothing until that
   line is added.
7. Report which profile got pinned and whether the shim is active. Mention that
   `install.sh --uninstall` undoes it.

Do not install anything without asking me first.

Rather type it yourself?

npm install -g cue-ai && cue setup

cue setup installs the claude/codex shim, scans this project, shows what the matching profile costs against loading everything, and pins it. Requires Node ≥ 20 and an existing Claude Code or Codex install — cue is a thin shim that hands off to your real agent, not a replacement for it.

package cue-ai · command cue · repo opencue/cuecards

Three things happen when you type claude afterwards:

1. The shim resolves this directory's .cue.profile.
2. cue materializes only that profile's skills, MCPs, and persona into a runtime.
3. The real Claude Code binary starts against it.

Pin a different project to a different profile:

cd ~/projects/my-shop
cue use medusa-dev      # writes .cue.profile in this directory
claude                  # launch