jolliai/jolli-cursor-plugin/jolli-status

Jolli Status

1. Call the Jolli Memory status tool.
2. Call queue_status without waiting.
3. Render a compact Markdown table containing version/enabled, hooks/runtime,

migration, provider/local agent, account credentials, bound Space, and stored memories. Omit unavailable optional fields.

1. List detected AI integrations below the table using their returned status text.
2. State whether memory generation is idle or still running.
3. Give a provider-aware verdict:

• local-agent: ready when its tool is configured; if an auth failure is

reported, use that tool's login remedy.

• jolli: requires Jolli sign-in or a Jolli API key.
• anthropic: requires an Anthropic API key.
• unset: requires a usable provider credential.

If status is unavailable, run JOLLI_INVOKED_VIA=skill:status "$HOME/.jolli/jollimemory/run-cli" status and summarize it. Do not list branch memories; route those requests to /jolli-recall or /jolli-search.

Shell prerequisite

This block requires a POSIX bash shell. On Linux/macOS the system bash works. On Windows, use Git Bash (the bash bundled with Git for Windows). Other Windows "bash" options — C:\Windows\System32\bash.exe, the WindowsApps alias, or any WSL bash — see a separate Linux home directory and will not find the Jolli entry script that lives under %USERPROFILE%.

If Git Bash is not available on Windows, STOP and tell the user: "Jolli skill needs Git Bash on Windows. Install Git for Windows from https://git-scm.com/download/win and retry."

Do NOT fall back to npm run, npx, node directly, PowerShell-native commands, WSL bash, or any workspace-local script — those bypass the security recipe and the dist resolver and will not produce valid output.

If the Jolli CLI dispatcher is missing (Cursor)

$HOME/.jolli/jollimemory/run-cli is written by this plugin's sessionStart hook, and a freshly installed plugin's hooks are not registered until Cursor has been fully restarted — a window reload or another chat is not enough (measured). So when that file does not exist, the fix is to quit Cursor completely (⌘Q) and reopen it, then start a new chat, and retry.

This REPLACES any instruction above to report Jolli as not installed, or to install @jolli.ai/cli globally or the Jolli VS Code extension. You are running inside the Jolli plugin, so Jolli IS installed, and neither of those is the fix on this host.