Last Updated: 9/2/2026

What’s New

Everything that has shipped, newest first. Each entry is one release day, grouped by the part of Jolli it affects. Versions are not listed in the headings: an entry usually spans the CLI, the editor extensions and the web app, which version independently.

September 1, 2026

Highlights: the Spaces and Workflows command plugins now need a current CLI.

Jolli Memory

• The Spaces and Workflows plugins need the CLI at 0.99.17 or later. Both now take the list of Jolli web addresses from the CLI itself instead of keeping their own copy, so a CLI that learns a new address teaches them the same one with no plugin release. On an older CLI the plugin is skipped rather than loaded, which means jolli space and jolli workflow stop appearing at all rather than reporting an error. If either goes missing, run npm i -g @jolli.ai/cli. How addresses are judged is unchanged. See Reference.

August 31, 2026

Highlights: CLI 0.99.17 on every channel, with the JetBrains plugin level again.

Jolli Memory

• The JetBrains plugin is up to date with the others. It had been a release behind; it now ships 0.99.17 alongside npm, the VS Code Marketplace and Open VSX, so a JetBrains setup receives everything announced for August 24 and August 28.
• The Claude Code, Cursor and Codex plugins are one release behind from today. Each bundles its own copy of Jolli, currently 0.99.16, so this release reaches them at their next plugin update rather than immediately.
• Bug fixes and performance improvements.

August 29, 2026

Highlights: the agent plugins pick up the August 28 release.

Jolli Memory

• The Claude Code, Cursor and Codex plugins now bundle CLI 0.99.16, so everything in the August 28 entry reaches them too, Hermes Agent capture included. Take the plugin update and there is nothing else to do.
• Signing out of Codex or Cursor now names Hermes among the logins that keep local memory generation working.

August 28, 2026

Highlights: Standup, Coaching, Skills and MCPs join the Dashboard in your browser, Hermes Agent becomes the eleventh captured agent, and the Team views narrow to owners and administrators.

Jolli Memory

• Hermes Agent conversations become memories. Sessions are found in Hermes’ own database, and on macOS and Linux a session-end hook records each one as it finishes. That makes fourteen sources across eleven agents. Every Hermes profile is set up, not only the default one. Turn it off with jolli configure --set hermesEnabled=false. The JetBrains plugin does not read Hermes sessions yet. See Supported AI Agents and Capture.
• Hermes can also generate your memories. It joins Claude Code, Codex, Cursor, OpenCode and Kimi Code as a local-agent option, so summaries can run through the agent you already have with no API key: jolli configure --set aiProvider=local-agent --set localAgentTool=hermes. See Getting Started with Jolli Memory.
• See where each repository syncs to. Settings now shows which Jolli Space a repository is connected to, in both the VS Code extension and the JetBrains plugin.
• A snappier dashboard on large repositories, with slow spots easier to spot so jolli doctor can point them out.
• The Decisions card is accurate again.

Jolli Memory Dashboards

• The Dashboard in your browser is now five pages, under My Dashboard and Team Dashboard. Alongside Dashboard there are Standup, Coaching, Skills and MCPs, each taking the same date range and repository picker. See The Web Dashboard.
• Standup lays out a week of committed work as day columns, with a pager to move between weeks. Only work that reached a commit and synced appears.
• Coaching reads your journeys against your own earlier line: how many in the window, plan-first share, cost and recall, with individual journeys openable as a trace. On the Team view it reports across members. Marked Beta.
• Skills and MCPs each get a full page, breaking every skill or MCP server out day by day with its runs and tokens, at more grain than the cards on the overview.
• The Team views need View Team Memory Activity, and Member no longer carries it. Owners and administrators have it. To give it to someone else, move them to a custom role that includes it. This narrows what the August 21 entry described. See Settings.

Onboarding & Settings

• The hosted assistant endpoint address is on the Settings page, with a button to copy it. It is the only address the endpoint accepts: a connection arriving on a workspace subdomain or a custom domain is turned away with a message naming the right one.
• Authorizing an AI assistant now says what it can do, not just what it can read. The consent screen and Settings → Connected apps both describe the tool permission as reading content and starting or cancelling Workflow runs that can add or change content.

August 24, 2026

Highlights: Cursor work is captured as it finishes, the local dashboard gains an MCPs page, and all three agent plugins ship the same evening.

Jolli Memory

• Cursor work is captured right away. Cursor conversations are recorded as they finish, so they appear without waiting for a commit or for the dashboard to be opened. In the Cursor plugin this arrives as a session-end hook the plugin installs itself.
• An MCPs page in the local dashboard, showing which MCP servers your agents called day by day, with the calls and tools for each. It ships in the plugins’ bundled dashboard too. See The Local Dashboard.
• A much faster local dashboard, especially on large repositories.
• Turning an agent off now applies everywhere. Switch a source off in Settings and it stops appearing across the dashboard, not just in the sidebar.
• The dashboard action takes a port, or a request for the address without opening a browser. Naming a page is no longer needed: the dashboard’s own navigation reaches every page once it is open.
• The Claude Code, Cursor and Codex plugins carry all of this, published the same evening and bundling the same 0.99.15 engine as the CLI.

August 21, 2026

Highlights: a Dashboard in your browser that reports what your agents did for you and for your team, memories that record which AI tool did the work, and a repair command for memories stranded by a rebase.

Jolli Memory

• A Dashboard when you open Jolli in your browser: the Analytics page is now Dashboard, with My and Team views. It reports your memories, decisions, skills, MCP calls, tokens and estimated spend over a range you pick, filtered to the repositories you choose. Old /analytics links land on the new page. See The Web Dashboard.
• The Team view needs a permission: View Team Memory Activity. Every built-in role has it, so the page is open by default. To close it, move people to a custom role without it.
• Your machine now sends session statistics to your organization, which is what fills that Dashboard: tokens, estimated cost, model names, tool and skill names, and session titles, for every repository Jolli is enabled in. It is on once you are signed in. Conversation text and code are never part of it. Turn it off with jolli configure --set syncSessions=false, or in the local dashboard under Settings → Sync to Jolli. What it does and does not send is spelled out in Troubleshooting and FAQ.
• See which agent did the work: memories record which AI tool each conversation, commit and skill came from, and both dashboards break your work down by agent. References and memories carry their source’s own badge.
• Two new pages in the local dashboard: Skills shows which agent used which skill, and Coaching reads your journeys for plan-first share, top skill, cost and recall, calling out your smoothest and hardest. Daily Standup is now a week at a time, and Knowledge and Graph are switched on under Settings → Advanced. See The Local Dashboard.
• jolli repair-memory reattaches a lost memory: when an amend, rebase or squash rewrites a commit, its memory can end up stuck on the old hash while the new commit shows nothing. jolli doctor now flags it and jolli repair-memory puts it back, with --status to preview first. Safe to run twice, and it backs up anything it replaces.
• Pick a model per local agent: localAgentModel now applies per tool, so Claude Code and Codex each keep their own default and choices. In the editors, Settings → AI Summary.
• Cleaner conversation history: empty conversations no longer clutter your archives, conversations that grow after import are picked back up, and Codex transcripts parse more reliably.
• SSH host aliases are recognised: a repository cloned through a ~/.ssh/config alias binds to the same identity as one cloned by its real host.
• The Claude Code, Cursor and Codex plugins are level with the CLI: each now bundles version 0.99.14, so everything above reaches the plugins too, including the session statistics that fill the Dashboard. Take the plugin update and there is nothing else to do.
• Open the local dashboard from the conversation: a new dashboard action in all three plugins - /jolli:dashboard in Claude Code, /jolli-dashboard in Cursor, $jolli:dashboard in Codex. See The Local Dashboard.
• Cursor: every skill now ships with the plugin. All twelve are available from the moment you install, including recall and search, which used to appear only after you had opted a repository in.
• Cursor: if you already had the plugin, remove the marketplace and add it again. It was renamed, and Cursor identifies a marketplace by its name, so the old entry keeps reporting that you are up to date and will never offer the update. In Customize, remove Jolli Cursor Marketplace, add jolliai/jolli-cursor-plugin again - it now appears as Jolli Cursor - then reinstall and restart Cursor. Your memories and settings are untouched, and this is a one-time step. See Jolli Memory in Your AI Agent.

Jolli Spaces

• Article search reads content, not just titles: searching from an AI agent now matches article bodies as well as titles, and every result comes back with a link you can open, a plain-text snippet of the match, and a relevance score. A search across several Spaces is ranked before it is capped, so the best matches survive.
• Approving an agent only offers workspaces where it will work: the approval screen lists the workspaces that have this kind of connection turned on, and says so plainly when none of yours do, instead of connecting and then refusing every request.

August 17, 2026

Highlights: the Jolli plugin is now available for Cursor and Codex, alongside Claude Code.

Jolli Memory

• Jolli Memory for Cursor: add jolliai/jolli-cursor-plugin as a marketplace in Cursor, then install Jolli Memory from Customize and pick a project or user scope. You get the Memory skills, the MCP tools, and a bundled runtime, so there is no CLI to install. Repositories are opted in one at a time with /jolli or /jolli-init rather than automatically, so a repository you only browsed is left alone.
• Jolli Memory for Codex: run codex plugin marketplace add jolliai/jolli-chatgpt-plugin, then codex plugin add jolli@jolli-marketplace. Review and trust the Jolli hook in /hooks before it can do anything, then start a new session; the MCP tools arrive from the session after that.
• A branch briefing on all three: Cursor and Codex now get the automatic session-start briefing that was previously Claude Code only, so your prior reasoning on a branch is in context from the first message.
• The Claude Code page is now Jolli Memory in Your AI Agent, covering all three plugins and how they differ.

August 15, 2026

Highlights: hosted agents can sign in to Jolli themselves, instead of being given an API key.

Jolli Spaces

• Connect an agent by signing in: an agent that supports connectors can now send you to Jolli in the browser to approve the connection, so there is no key to create or paste. Add https://jolli.ai/mcp and approve.
• You pick which organization the agent reaches: the approval screen asks, and checks the answer against the organizations you belong to. If you were invited to one and had not opened it yet, approving finishes setting up your account there.
• API keys still work for anything that cannot open a browser. See Use Your Memory from Any AI Agent (MCP).

August 14, 2026

Highlights: the dashboard runs in your terminal and gains Knowledge and Graph views, the wiki rebuilds when you ask, three more reference sources, and your agent can write a memory to Jolli Cloud.

Jolli Memory

• The dashboard runs in your terminal: jolli dashboard serves until you press Ctrl+C instead of leaving a server behind, so jolli dashboard --stop is gone. Run it again and it replaces the one already running. See The Local Dashboard.
• Knowledge and Graph join the dashboard: browse your wiki and view the knowledge graph in the page, next to My Dashboard, Daily Standup, and Memories. The Repositories page is gone, replaced by a picker that scopes what you are looking at.
• The wiki and graph rebuild when you ask: they no longer rebuild after every commit, so commits stay fast and nothing spends AI credits unprompted. For the old behavior: jolli configure --set wikiRebuild=auto.
• Three more places your references come from: Vercel deployments, Figma design files, and Sentry issues now appear on your memories, bringing the total to fifteen sources.
• Your dashboard finds more conversations: it now reads your agents’ session history from the last seven days, not just what was already recorded, and says in one line what it picked up.
• Pushes stop promising memories that were never yours: after a rebase the pre-push check counted commits already on the remote. It now counts only what your push adds.
• MCP tools answer for the right repository: started outside a project, the tools that need one are hidden rather than returning an empty result that reads as “no memories here”.
• jolli doctor gains --schema-log and --mark-migration: inspect your memory database’s schema history, or repair it when a migration record went missing.

Jolli Memory in VS Code

• Open your dashboard from the sidebar: a new toolbar button, also Jolli Memory: Open Dashboard in the Command Palette, runs it in a terminal so you can watch it work and stop it with Ctrl+C.
• A wiki banner: the sidebar shows how far behind your wiki and graph are and rebuilds them on one click. Dismiss it and it returns once there is something new.

Jolli Memory in JetBrains IDEs

• The FILES panel matches VS Code: discard and “leave out of this memory” moved onto each row as hover buttons, and committing lives on the Current Memory card.
• Discarding a file is reliable: renamed, copied, untracked, and conflicted files all behave now, the confirmation matches what happens, and a failure tells you instead of reporting success.

Jolli Spaces

• Your agent can write a memory to Jolli Cloud: the hosted MCP surface gains create_remote_memory, so an agent can capture a decision or a note without leaving the conversation. It writes to your organization’s default memory Space, or one you name.
• One address for the hosted MCP endpoint: connect at https://jolli.ai/mcp. A connection on a workspace subdomain or a custom domain is now turned away with a message naming the address that works, instead of failing later for no clear reason.

Jolli Memory in Claude Code

The plugin moves to 1.0.3 and its engine is level with the CLI again, so everything above is available through the plugin. Its commands and skills are unchanged. Quit Claude Code completely and reopen it so the update takes effect.

August 10, 2026

Highlights: a local dashboard for your memories, a one-way move to local database storage, Kimi Code sessions become memories, a new minimum Node version, and the Claude Code plugin catching up to the CLI.

Jolli Memory

• Node 22.13 or newer is now required: previously 22.5. The package refuses to install on an older runtime, so upgrade Node before running npm install -g @jolli.ai/cli. If an install looks like it worked but leaves you with no jolli command, this is almost always why. The VS Code extension now needs VS Code 1.101 or newer; on 1.100 and earlier the Marketplace stops offering updates, so your installed version quietly stays where it is.
• A dashboard in your browser: jolli dashboard starts a private server on your machine and opens a view of your memories, per-repo stats, and a standup summary. Nothing is uploaded. Stop it with jolli dashboard --stop. See The Local Dashboard.
• Move a repository’s memories to a local database: jolli cutover makes SQLite the source of truth for a repository. This is one way. It freezes the repository’s git branch, and jolli enable will not unfreeze it. Run jolli cutover --status first to see where a repository stands, and jolli cutover --probe afterwards to check the frozen branch for drift.
• Kimi Code conversations become memories: sessions from Kimi Code CLI are discovered automatically, with references and skill usage, and no hook to install. Jolli also registers its MCP server for Kimi Code, bringing the total to eleven hosts.
• Skills travel with the memory: pushing a memory or a branch to a Space now sends the skills the work used as separate articles, next to plans, notes, and references.
• Squash memories keep your working context: plans, notes, and references you activated during a session are archived into squash and merge memories instead of being left behind.

Jolli Memory in JetBrains IDEs

Same release as the CLI and VS Code this time, so everything above applies here too. The plugin now needs Node 22.13, up from 18.

• The tool window is redesigned: one + button for plans, notes, and snippets, hover actions on every row, and a new status overlay carrying Sign In, Sync Now, and a Disable that turns Memory off for a whole repository.
• Kimi Code, Devin, Cline, and Antigravity reach the sidebar, each with a Status row and a switch under Settings → AI Agents.
• Skills used: a new row in CONTEXT and on every memory, listing each skill with its count and first and last use.

Jolli Memory in Claude Code

The plugin moves to 1.0.2. Its commands and skills are unchanged, but the engine inside it was two releases behind and now matches the CLI, so everything above is available through the plugin.

• Nothing to install by hand: Claude Code fetches the plugin itself, and the new engine arrives with it. Quit Claude Code completely and reopen it so the update takes effect.

August 7, 2026

Highlights: connect a hosted AI agent straight to Jolli with an API key, published Sites gain robots.txt and sitemap.xml, and a new Set up page greets everyone on their first sign-in.

Jolli Memory

• Point a hosted agent at Jolli: agents that cannot run a local process can now connect over the web at /mcp using a Jolli API key as a bearer token. The endpoint works on your workspace URL, a tenant subdomain, or a verified custom domain. Your key decides which workspace it reaches, so there is nothing else to configure.
• A hosted agent can read your team’s memory: new tools let a connected agent search your organization’s memory and open a specific memory document, scoped to what the key’s creator can view. Documentation search is unchanged and still leaves memory and personal Spaces out.

Jolli Sites

• Published sites now emit robots.txt and sitemap.xml: every site gets robots.txt, and a sitemap once the site has a canonical web address. Sites behind a sign-in serve Disallow: / and no sitemap.
• /llms.txt is sharper: page links and source lines are now absolute, cross-references between articles resolve to real URLs, sections follow your navigation instead of alphabetical slugs, and each page contributes a single heading.
• Give your site a summary: a new Site Description in Site Settings renders as the opening line of /llms.txt, so an agent landing cold knows what the site is. An edited summary or a newly attached domain now shows up as a pending change, so you know a republish is due.

Onboarding & Settings

• A Set up page is the new first stop: signing in for the first time now lands on Set up Jolli for your team, with the install command for your platform, the other install targets, and a short explanation of where the data comes from and when it arrives. Whoever can invite people also gets an Invite your team card.

August 2, 2026

Highlights: the JetBrains plugin catches up, and the jolli-pr skill is retired.

Jolli Memory in JetBrains IDEs

The IntelliJ plugin moves to 0.99.10, past 0.99.9, so a JetBrains IDE now has what the CLI and VS Code picked up on July 31 below, including reference ids and the per-repository push toggle. The local agent picker from that entry arrives here too, under Settings → AI Summary → Local Agent. Update the plugin from Settings > Plugins and restart the IDE when prompted.

New to JetBrains in this update: the first-run screen offers Use a local agent CLI alongside the Anthropic-key and Jolli sign-in options, so you can get started without any key.

Also in this update:

• The jolli-pr skill has been removed: only jolli-recall and jolli-search are installed now, and upgrading removes the old skill file for you. Turning a branch’s memories into a pull-request description is still available through the get_pr_description MCP tool and the jolli pr-description command.
• Sessions started in a subdirectory are found: an AI session begun in a nested folder is attributed to the repository that contains it instead of being missed.
• Memory generation from GUI git clients such as SourceTree and IntelliJ’s own commit UI is fixed, unsaved editor buffers are staged before an AI commit, and the full branch commits list is restored.

July 31, 2026

Highlights: Memory registers itself with three more AI agents, you can turn one repository’s pushes off without turning capture off, a running Workflow can be cancelled from the button that started it, and a Space can restrict which repositories push into it.

Jolli Memory

• Three more agents are wired up for MCP: Cline, Devin, and Antigravity now get the jollimemory server registered for them, bringing the total to ten. For Cline this is the VS Code extension, once per flavor you have installed; the Cline CLI keeps no MCP config of its own.
• Agents are detected more reliably when you enable: several hosts could previously be skipped, either because detection needed a newer Node version than the editor extension runs on, or because the agent had not been used yet and so looked absent. Detection no longer depends on either. Registration still happens when you run jolli enable, so install the agent first.
• Choose the local agent that writes your memories: Codex, Cursor, OpenCode, and Kimi Code join Claude Code. If exactly one is installed and working it is picked automatically and named back to you; otherwise you choose from the ones found on your machine.
• Turn pushing off for a single repository: jolli push-control --disable stops that repo from sending memories to a Space while still recording them locally, and --enable turns it back on and sends what was held. VS Code has the same control per repository on its Settings page.
• See whether the Memory Bank is writing: jolli status and the VS Code Settings page now always show the Memory Bank’s state, naming the folder in use or saying why nothing is being written.
• Skill usage is captured: a commit now records which skills the session entered and roughly what they cost, as a table in your Memory Bank folder and live in the VS Code sidebar. Claude Code, Codex, and OpenCode report it.
• Every memory has a short reference id: memories now carry a JM- id you can quote to a teammate, shown in both editors and in the web app. Selecting it in an editor copies it.
• A repository you turned off stays off: the VS Code sidebar and AI commit messages now respect that, and a turned-off project is left alone.

Workflows

• Cancel a run from the button that started it: a Workflow card’s primary button reads Run now while the Workflow is idle and changes to Running… while a run is in flight. Choosing it then asks you to confirm, and cancelling stops the run without publishing anything. Cancelling is no longer buried in the overflow menu. Pausing a Workflow still leaves a run that is already going to finish, or to be cancelled.

Jolli Spaces

• Restrict which repositories push into a Space: Jolli Memory Spaces have a new Restrict pushes to listed repos setting, off by default. Turn it on and only the repositories already registered may push; anything else is refused and can no longer add itself. Repos already listed keep working, and turning it on never removes one.
• The auto-apply setting is hidden where it does not apply: Spaces whose repository Jolli manages already merge automatically, so the toggle no longer appears for them.

July 25, 2026

Highlights: the install script is now the quickest way to get set up.

Jolli Memory

• The install script is now the recommended way to install: one command installs the CLI, installs Node.js if you need it, and runs the guided setup. See Getting Started with Jolli Memory.

July 24, 2026

Highlights: four new AI agents captured, /llms.txt on every published Site, and workflow run-completion notifications by Inbox and email.

Jolli Memory

• More agents captured: Memory now captures twelve sources across nine agents, adding Cursor CLI (cursor-agent), Cline (the VS Code extension and the CLI), Devin, and Antigravity. All are discovered automatically, no setup.
• Ships as a Claude Code plugin: install Jolli from Claude Code’s plugin marketplace with /plugin marketplace add jolliai/jolli-claude-plugin, then /plugin install jolli@jolli-marketplace. Restart Claude Code, open a session in a git repository, and Memory sets itself up: the git hooks, Memory’s MCP tools, the /jolli:status, /jolli:init, /jolli:login, /jolli:logout, and /jolli:timeline commands, the /jolli:recall, /jolli:search, and /jolli:push skills, and a /jolli menu that lists them. No CLI install, no API key, and no sign-in needed to start generating memories. The plugin covers Jolli Memory; jolli space, jolli site, and jolli workflow still come from their own CLI plugins. See Jolli Memory in Your AI Agent.
• Simpler setup: if a local Claude Code CLI is detected, jolli enable uses it automatically (its subscription, no key, no menu).
• Smarter references: Context7 library lookups are now tracked as lightweight bookmarks, and Codex now captures Slack threads referenced in a conversation (previously Claude Code only).
• Memory in the web app: an interactive knowledge-graph viewer for your Memory spaces, and a Copy Recall Prompt button on Memory summaries.

Workflows

• Notify on completion: post a run summary to your Inbox when a run finishes, to the Space owner, the Workflow owner, and/or all Space members.
• Run summaries by email: each recipient also gets an email with the same summary and links shown in their Inbox, plus a View in inbox button that opens that exact notification. Email goes to the recipients you already picked, with no separate setting to switch on.
• Email sent on completion: the Workflow complete notification shows a preview of the email that went out, including who it was delivered to and its subject line.
• Inspect runs from the command line: for a git-backed Space cloned on your machine, the new jolli workflow plugin reports which Workflows can run locally, a Workflow’s run history, and the status of a run as it finishes. Output is JSON, so it drops into scripts and agent recipes. Install it with npm i -g @jolli.ai/cli @jolli.ai/workflow-cli.
• Duplicate or move a workflow: copy a workflow, or move it to another Space, right from the workflow card.
• Run now is now a one-click primary button on every workflow card.
• Richer run history: each run shows how many documents it created, edited, and deleted, and whether the result was applied automatically or opened as a pull request.

Jolli Sites

• Built for AI: every published Site now generates /llms.txt and /llms-full.txt at its root and advertises them in each page’s <head>, so AI clients like Claude, Cursor, and ChatGPT can ingest your docs in one shot.

Onboarding & Settings

• A friendlier first run: name-free signup, plus a ready-to-use Shared Space (seeded with a Welcome doc) created for you automatically.
• Rename your workspace anytime from the new Settings → Workspace page.
• Invite your team from a single dialog: one person or a CSV.

July 17, 2026

Highlights: generate memories with your own local AI, a guided first run of the jolli command, three more reference sources, and workflow run history you can click through.

Jolli Memory

• Write memories with your own AI: a new local-agent provider drives a locally-installed Claude Code to generate your memories using its own login, with no API key and no Jolli proxy call. Turn it on in the extension settings or with jolli configure --set aiProvider=local-agent.
• A guided front door: running jolli with no arguments now walks you through signing in, fixing a missing AI provider key, and turning recent commits into memories, all from one prompt.
• Run a workflow from your agent: the new /jolli-local-run skill runs a Jolli workflow on your own machine, with no Jolli AI credits, and lands the result in a git-backed Space through a branch and pull request. Remote runs work too.
• More reference sources: conversations that mention monday.com, Asana, or Confluence now capture those items as references.
• Your knowledge graph follows you: graphs now sync across the machines you sign in to, and can be embedded on the web.
• One menu for everything: type /jolli in Claude Code for a single menu that lists the Jolli skills (recall, search, PR, run a workflow) and the Jolli tools available in your session, then runs the one you pick.
• More ways to install: new PowerShell and Windows Command Prompt install scripts, plus one-click install buttons for VS Code, Cursor, and JetBrains.
• Clean uninstall: jolli uninstall finds and removes every Jolli install and config on your machine, and never touches your memories.

Workflows

• Run history you can click through: open History on any workflow to see past runs, jump straight to the article a run wrote or the pull request it opened, and link directly to a specific run.
• Run now with custom values: when a workflow’s prompt uses variables, Run now opens a form to set values for that run only, without changing the workflow’s saved defaults.

Jolli Spaces

• Wiki-style links: relative links between articles now open the linked article in place, and heading links jump to the right spot on the page.
• Cleaner article links: article web addresses are now readable and built from the article title instead of an internal id, so a shared link makes sense at a glance.

July 10, 2026

Highlights: memory that syncs on every push, Slack and Zoom captured as sources, the IntelliJ extension catching up to VS Code, and the Jolli Agent on the newest Claude models.

Jolli Memory

• Sync on every push: once you are signed in, git push automatically syncs the pushed commits’ memory to your Jolli Space in the background, and retries anything that did not make it on the next push. Turn it off with syncOnPush: false.
• More reference sources: Slack threads and Zoom meetings mentioned in a conversation are now captured as references.
• The IntelliJ extension catches up to VS Code: the JetBrains plugin gains token usage and estimated cost on each memory, Markdown export, read-only share links, and a card that builds memories from your existing commit history.
• More agents captured: GitHub Copilot and Copilot Chat conversations are now captured, and Codex sessions resume correctly and stay scoped to the current repo.
• Usage and cost on shared memories: pushed memory articles now show a Task usage line with total tokens and an estimated cost, now priced by the model that generated each memory rather than a flat rate.
• Global AI instructions are now opt-in: Jolli asks before adding its skill-preference block to your global instruction files, and will not add it without your go-ahead.

Jolli Spaces

• Guided Space setup: creating a Space now lets the Jolli Agent generate documentation from your connected sources or import your existing docs as-is, with a live progress view that keeps running if you step away.
• The newest Claude models: the Jolli Agent now runs on Claude Opus 4.8 and Sonnet 5 with extended thinking, for stronger document generation and analysis.
• Fewer naming collisions: creating a folder or document with a name that already exists now adds a number instead of failing.

Onboarding & Settings

• Clearer access errors: opening a shared link that belongs to an account you are not a member of now names that account and offers to sign in with a different one.

Related

• Welcome to Jolli - the three layers and where to start.
• Getting Started with Jolli Memory - install the CLI and generate your first Memory.