Run a Jolli workflow locally — your own agent executes the workflow's recipe (no Jolli LLM budget) and its file writes land in a git-backed Jolli Space via a branch and pull request that space-cli opens on this machine. Use when the user wants to run a Jolli workflow locally.
Sign in to Jolli from Cursor so the repository can bind to a Jolli Space and share memories. Use when the user asks to log in, authenticate Jolli, connect an account, or fix missing Jolli credentials.
Sign out of Jolli from Cursor by clearing the stored Jolli auth token and Jolli API key while preserving other provider credentials. Use when the user asks to log out, disconnect Jolli, or remove Jolli account credentials.
Publish the current branch's Jolli memories to a Jolli Space. Use when the user asks to push, publish, share, or sync memories or decisions with a team.
Run a Jolli workflow remotely — the Jolli backend executes the workflow server-side; this recipe triggers the run, monitors it to completion, reports the outcome (failed / cancelled / succeeded) with its article, PR, and workflow links, and offers to open any in your browser. Use when the user wants to run a Jolli…
Search structured commit memories across all branches — decisions, topics, files. Use when the user wants to find prior decisions, related commits, or how a topic was handled before.
Diagnose Jolli Memory installation, provider, account, hooks, queue, integrations, stored memories, and Space binding for the current repository. Use for status, health checks, missing or stale memories, setup verification, or troubleshooting.
Show the chronological evolution of a Jolli Memory decision topic. Use when the user asks for a topic timeline, how a decision changed over time, or provides a Jolli topic slug.
Automatically captures and generates project memory from your development work — team-shareable and synced across devices, so you can recall and search past decisions and context across sessions and agents. Backed by the jolli CLI bundled as an MCP server.
2 3d agoA
tokens not measured
copy · 100%Apache-2.0
Set up Jolli for this project — sign in if needed, enable memory generation, and bind the repo to a Jolli Space. Use when the user wants to initialize / set up Jolli, or bind this repo to a Space.
Sign in to Jolli to share this repo's memories to a Space. Opens your browser to complete login. (Memory generation itself runs locally and needs no sign-in.).
Open the local Jolli dashboard in a browser — the machine-wide view of memories, agent sessions, token spend and knowledge across every repository Jolli tracks, plus the daily standup page. Use when the user asks for the Jolli dashboard, stats, usage, standup, or wants to browse their memories in a UI.
Push this branch's Jolli memories to a Jolli Space so teammates can see them. Use when the user wants to push, share, publish, or sync their memory / decisions to Jolli or a Space, even without naming Jolli.
Recall prior development context for the current branch — decisions, why past choices were made, and where work left off. Use when the user wants to resume work, asks why something was done, or references earlier work, even without naming Jolli.
Search past decisions and implementations across all branches. Use when the user asks how something was handled before, whether a problem was solved previously, or to find related prior commits — even without naming Jolli.