Setup Guide

The AI tooling installs as a Claude Code super plugin. Just add the marketplace and install one plugin - enactor-ai-tooling. The child plugins (enactor-workspace-assist for workspace/POS setup, enactor-code-assist for code work) are installed on demand by Claude the first time a request needs them.

Installation order matters - code-assist needs a real Enactor workspace to work against:

• Open Claude Code (Step 2).
• No workspace yet? Set one up first with enactor-workspace-assist (Step 3).
• Already have one? Skip straight to Step 4.

Prerequisites checklist

Tick these off before you start:

• Python 3.10+ (verify with python --version, or python3 --version on macOS/Linux)
• uv (install with pip install uv)
• Claude Code CLI (install with npm install -g @anthropic-ai/claude-code)

Troubleshooting: "pip not found" when installing uv

Try invoking pip through Python instead:

# Windows
python -m pip install uv

# macOS / Linux
python3 -m pip install uv

Step 1 - Add the marketplace and install the plugin

From a terminal, run:

claude plugin marketplace add "https://ai.enactor.co.uk/marketplace.json"

claude plugin install enactor-ai-tooling@enactor

Installing the super plugin installs only the parent plugin. Child plugins are downloaded and installed on demand:

• The first workspace or POS setup request installs enactor-workspace-assist.
• The first Enactor code request installs enactor-code-assist.

Claude requests your approval the first time each child plugin is installed. After installation, the plugin suite pre-approves its own plugin commands, so no additional permission prompts are shown.

Deterministic install (optional)

Prefer everything in place up front - e.g. for a training session? Pre-install the children yourself:

claude plugin install enactor-workspace-assist@enactor
claude plugin install enactor-code-assist@enactor

Keeping the tooling up to date

The enactor-ai-tooling super plugin tracks the version published in the marketplace catalog (marketplace.json). At the start of each session it checks whether a newer release is available, and after your first prompt it tells you if there is one - listing the current and latest versions and the child plugins the release updates.

Updates are never automatic. Whenever one is offered you decide whether to apply it or skip it for now; nothing changes without your consent. You can also check on demand at any time by running /update - it belongs to the super plugin, so it's available as soon as the suite is installed. It shows a full summary of what will change and asks you to confirm before applying anything.

After applying an update, restart Claude Code. The running session keeps using the old version until you do, so the changes don't take effect until you reopen it.

Prefer the raw plugin commands? Run:

claude plugin marketplace update enactor
claude plugin update enactor-ai-tooling

For anything version-specific, see the release notes.

Project-level install

Want to limit the skills, agents, and MCP configuration to a single project instead of your user profile? Add --scope project to the install command.

Step 2 - Open Claude Code from your workspace root

Navigate to your workspace root - or the empty folder where you want to create one - and start Claude Code (Windows / macOS / Linux):

claude

note

Don't have a workspace yet? Navigating here just means the folder where you want one set up - Step 3 below creates it.

Step 3 - Set up your Enactor workspace (skip if you already have one)

note

Skip straight to Step 4 below if you already have an Enactor workspace checked out.

Code-assist can only search and generate code against a real Enactor workspace, so if you're starting from an empty folder, set one up first. Inside the Claude Code session you just opened, ask Claude to set up the workspace, or run the command directly:

/setup-workspace

note

/setup-workspace belongs to the enactor-workspace-assist child. If it isn't installed yet, just describe what you need (e.g. "set up an Enactor workspace here") - Claude installs the child and continues in the same conversation.

This runs prerequisite checks (JDK, Maven, MariaDB, Artifactory, insights/SVN access), then downloads or checks out the codebase, runs the Maven build, and imports it into Eclipse. It takes 5-15 minutes depending on network and build speed, and can resume if it's interrupted. See the Workspace Assist Skills page for the full command reference and example prompts.

Once it finishes, your workspace has the standard layout code-assist's auto-detection expects:

C:\Enactor\DevelopmentWorkspace\
├── Platform\
│   └── Branches\
│       └── <BranchVersion>\        ← already checked out
│           ├── enactor-core\
│           └── ...
├── Configs\
├── EnactorHome\
└── WorkspaceProjects\

If your layout differs (e.g. a workspace set up by hand or by an older version), don't worry. You can point the tooling at the right folder later with the /set-path command.

Step 4 - Run first-time code-assist setup (once per workspace)

Inside Claude Code, run the setup skill:

/init-workspace

note

/init-workspace belongs to the enactor-code-assist child. If it isn't installed yet, just ask Claude to "set up the Enactor code tooling"; it installs the child, runs the configuration, and tells you when to reload.

This automatically:

• Creates or updates CLAUDE.md with the Enactor rules
• Writes .mcp.json with the correct local/remote paths
• Checks dependencies (Python, uv, curl)

note

This step is only required once per workspace, on fresh installs or after upgrades.

Step 5 - Restart Claude Code

Exit and reopen Claude Code from the workspace root so the rules in CLAUDE.md take effect (only needed if you ran /init-workspace in Step 4):

claude

Expected result: Claude Code shows a one-time approval prompt. Because the new .mcp.json lists servers not yet approved for this project, Claude Code's built-in UI asks you to approve them. Accept to continue.

Step 6 - Verify MCP connections

Once Claude Code opens, type:

/mcp

Expected result: enactor-local shows Connected, and enactor-remote shows Needs sign-in until you authenticate (see below).

Server	Transport	Status
enactor-local	stdio	Connected
enactor-remote	HTTP	Needs sign-in

The remote connection goes to Enactor's hosted codebase-search service over HTTPS. It provides embedding-based search of the Enactor source for the branch version(s) your licence covers. Because it is a shared, internet-reachable service, it asks you to sign in the first time it connects - see Signing in to the remote server below.

Signing in to the remote server

The remote index is a shared, internet-reachable service, so enactor-remoteneeds you to sign in - it shows Needs sign-in in /mcp until you do. To sign in:

1. Right after the restart in Step 5, Claude Code connects to enactor-remote and opens a browser window automatically.
2. Log in with the Enactor account your Enactor contact gives you.
3. Approve the sign-in. The browser confirms, and back in Claude Code enactor-remote moves to Connected.
4. Run /mcp again to confirm both servers now show Connected.

You stay signed in across sessions, so day to day you should rarely be prompted again. If the login window never appears and enactor-remote stays failed, your account may not have access yet, or the server may not be advertising where to sign in - ask your Enactor contact to check.

Troubleshooting: enactor-remote shows as failed

Two things usually cause this: you haven't signed in yet (see Signing in to the remote server above), or search is resolving to a different branch version than your workspace - for example your workspace is on 2.7 but the index is 3.0.9.

Don't edit .mcp.json by hand. It's generated, and the setup script rewrites it on the next run, so a manual change won't stick. Instead, run /set-mcp-server inside Claude Code. It shows which server you're currently resolved to, lets you switch to the branch version that matches your workspace (2.7, 3.0.9) or return to auto, then writes the change into .mcp.json for you.

Ask your Enactor contact for the current enactor-remote endpoint for each branch.

Restart Claude Code afterwards so the new index takes effect. Until you do, /mcp and health_check() keep showing the previous connection (a "pending index switch").

Troubleshooting: setup fails with an error

Go back to the prerequisites checklist, make sure every item is installed and on your PATH, then retry the steps in order.

You're done!

Quick self-check before moving on:

• Super plugin installed (claude plugin install enactor-ai-tooling@enactor succeeded)
• An Enactor workspace exists - either it already did, or /setup-workspace (enactor-workspace-assist) completed
• enactor-code-assist present (installed on demand or pre-installed, check with claude plugin list)
• /init-workspace ran and created CLAUDE.md + .mcp.json
• /mcp shows enactor-local and enactor-remote connected

Next: learn what the skills can do in Using the Skills.