Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Meza-dev/Ghostly/llms.txt

Use this file to discover all available pages before exploring further.

ghostly update upgrades your globally installed @ghostly-io/cli package to the latest version published on npm. Because the CLI bundles every Ghostly component — the API server, the test runner, the MCP server, and the web dashboard — a single update command is all that is needed to keep your entire local environment current.

​
What it does

Running ghostly update executes the following command in your shell: 
npm install -g @ghostly-io/cli@latest
The spinner stays active until npm finishes. On success the terminal confirms the update and instructs you to restart your terminal. If npm exits with a non-zero code the error is printed and you are shown the manual fallback command.

​
Usage

ghostly update
There are no flags for this command.

​
After updating

1

Restart your terminal

npm replaces the ghostly and ghost wrapper scripts on disk. Open a new terminal session (or source your shell profile) so the shell picks up the new binary paths.
2

Verify the installed version

ghostly --version
3

Re-run the installer

Run ghostly install again to refresh the Cursor rules, skills, and MCP server configuration with any changes shipped in the new version.
ghostly install
4

Restart the engine

If ghostly up was already running, stop it (Ctrl+C) and start it again. The new version will run prisma generate and apply any schema changes automatically.
ghostly up

​
Bundled components

The @ghostly-io/cli package ships every service Ghostly needs as part of its dist/ directory. Updating the CLI updates all of them in one step:
ComponentPurpose
API serverREST API and MCP tool handlers
Test runnerPlaywright-based E2E execution engine
MCP serverCursor tool integration via Model Context Protocol
Web frontendDashboard served as static files by the API
After updating, always run ghostly install to ensure the MCP server entry in ~/.cursor/mcp.json points to the correct path in the new version and that your Cursor rules and skills are up to date.
If npm install -g fails due to permission errors, you may need to fix your global npm prefix ownership or use a Node version manager (such as nvm or fnm) that installs global packages without requiring sudo.

Build docs developers (and LLMs) love

Get started for freeTalk to us