/setup

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select setup from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv setup, /just-vibe setup and /jv:setup in Claude. See shortcut setup and context examples.

What the agent does

1. Resolve scripts/installer.mjs relative to this installed plugin. Choose doctor for a status question, setup for an install request, update for a refresh request, and uninstall only for an explicit removal request.
2. Honor the host, bundled default / --github / --local source and Claude --scope user|project|local; Claude project/local operations run with the project as the working directory; --root applies only to editor adapters. Never place tokens in commands or files.
3. For a requested preview append --dry-run and report conditional steps without claiming installed state was inspected. Preserve all native source/scope/inventory conflict checks.
4. Read back native source, scope, enabled state and version after the authorized installation; preserve unrelated plugins and report partial native failures. Explain that changed skills load in a fresh conversation. Uninstall retains marketplace registration and persistent data. Do not bypass errors with global edits or cache deletion.

Inputs

• Requested operation and target host; Claude scope when applicable.

Optional context: source, scope, dryRun.

Scope

Reads

Install/enable just-vibe through the selected host's plugin manager; no unrelated plugin, permission, hook, or integration changes.

Writes

Selected host plugin registration and its managed just-vibe payload directory. For Claude, also the owned shortcut files: the jv skills-directory plugin (skills/just-vibe-shortcuts), commands/jv.md, commands/just-vibe.md and .just-vibe/installations/claude-shortcuts.json, under ~/.claude at user scope or the project .claude folder at project or local scope. Editor adapters write only their listed project files.

Mode

Apply for an installation request; target host, bundled source, --github or --local checkout, and Claude scope. A preview request uses the existing `--dry-run` behavior.

Prerequisites

Node.js 22+. Codex and Claude targets also need the host CLI with native plugin support; editor adapters need only the project directory. Git is required only for --github. Use the bundled installer; preserve marketplace and scope checks.

Expected output

• Installation outcome with source/version, host/scope and native host state, and executable verification or the precise blocker.
• Changed files, including Claude shortcut files that appear as untracked repository files at project or local scope.

How the work is checked

• Repeated setup does not create duplicate registrations; an existing marketplace with another source stops without replacement.

When to stop or clarify

• Dry run does not inspect host state and must not imply it did. No manual global-config edits or credentials embedded in commands.

Handling missing context

Infer

Inspect selected host, native CLI support, existing source/scope and package version without changing global configuration.

Assume

Use the documented bundled source and existing host conventions unless the user selects another source.

Ask

Ask only when multiple host/scope/source choices cannot be resolved from context and would change installation; report an actual missing executable instead of requesting unrelated credentials.

Technical guidance

Evidence

Resolve host, scope, source channel, native plugin inventory and candidate bundled version.

Method

Use the supported installer lifecycle and persistent payload, reconciling existing source identity before update or removal.

Pitfall

A package-manager install alone does not register a native plugin; deleting package cache must not break the managed payload.

Check

Read back the native inventory: source, scope, enabled state and payload version match the request, and for Claude the owned shortcut files report healthy.

Situational decisions

When an existing managed source conflicts with the selected channel: Report the conflicting identity and supported switch procedure instead of overwriting arbitrary directories.

When the target is an editor adapter (Cursor, Copilot, Gemini, Zed and the other adapter hosts): Pass --root <project> and no --local or --github flag; there is no native inventory, so verify the adapter JSON (installed, conflicts, missing, outdated) and restart the host.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring