Logseq Copilot | Blog

Logseq Copilot 2.0

Thu, 12 Nov 2026 00:00:00 GMT

Logseq Copilot 2.0 is a rebuild of the extension on WXT. It brings a sidebar for the page you are reading, a redesigned card on search result pages, Brave Search, recall rule scopes, a new look, and a stricter way of mounting the extension’s UI in the pages you visit. It also fixes a long list of clipping and search problems. This post covers what changed.

File graphs and DB graphs

Logseq Copilot works with file graphs (Logseq 0.10.x) and DB graphs (Logseq 2.x). It asks Logseq which kind of graph is open each time it searches, so there is no setting to switch. Move from one graph type to the other and the next search uses the right one.

DB graph support already existed in 1.x. What 2.0 adds is coverage and fixes. CI now runs integration tests and browser end-to-end tests against a real Logseq. The end-to-end runs use 0.10.15 for file graphs and 2.0.2 for DB graphs. Along the way we fixed DB search, URL lookup and TODO toggling. On a DB graph a task’s state is a property rather than text in the block, so the extension maps TODO, DOING, DONE and CANCELED onto Logseq’s built-in statuses.

Firefox

2.0 sets a minimum Firefox version: 127. MV3 host permissions are only granted at install time from 127 on, and the extension needs them on every site. The Firefox manifest now also declares that the extension collects no data.

The end-to-end suite runs in Firefox as well as Chromium, against both graph types. 2.0 also removes Chromium-only assumptions, including how a click on a highlight is resolved to a text position. There is no Safari build; see Installation.

When you clip a text selection, the extension also saves it as a highlight on the page. The highlights of the page you are reading are listed in your browser’s own sidebar: the side panel in Chrome and Edge, the sidebar in Firefox. The list follows the active tab and stays open when you switch tabs. Click a highlight to jump to it on the page, edit its note, or delete it.

The toolbar icon opens this sidebar. The 1.x popup is gone, because the sidebar does what it did: below the highlights it lists the notes in your graph that mention the page, and its header has a search of your graph and the Clip page and Clip selection buttons. In Firefox, click the icon again to close it.

Browsers without a sidebar of their own get the same sidebar drawn on the right side of the page. Arc has a side panel but never shows it, so the extension detects Arc and uses the sidebar on the page there until you choose otherwise. In other browsers you can switch to it under Settings, Sidebar, In-page sidebar. See Sidebar.

Highlights are stored in your browser only. They are not written to Logseq. The clipped text still goes to Logseq as before. Highlights in the browser sidebar walks through the whole workflow.

Search result pages

The card next to your search results is redesigned. It groups what it finds by page, shows the best blocks of each page, and for a block deep in an outline it adds a gray line with its parent, so you can tell where it sits. Click a page, a block or a parent line to open it in Logseq. See Search Engines.

Brave Search is a new built-in engine (#69).
The Kagi card now fits the results page (#81).
The card shows again on Startpage’s new layout and on Bing’s layout that drops unknown classes. A Bing result page that loads twice no longer searches Logseq twice.
On a file graph, the card finds more than the first 10 blocks that Logseq’s own search returns.

Clipping

A clip uses your graph’s journal date format (#77).
You can clip a selection where the extension cannot run in the page, such as the browser’s PDF viewer (#60). Use the right-click menu.
When a clip fails, you now see why, wherever you clipped from: a message on the page, an error under the sidebar buttons, or a ! on the toolbar icon where no page script runs (#48).
A failed connection names the address that was tried and the HTTP status, and says whether the token is wrong (#80).

Recall rules

Recall rules change how the extension searches your graph for pages that match a URL pattern. A rule can:

drop the URL hash or query string before searching, and ignore chosen path segments;
exclude or prefer keywords;
search only some Logseq pages, or skip others;
recall notes about more than the page itself, up to its parent paths (the scope);
cap the number of results, or put recent ones first.

A rule’s scope sets how many levels of the address it recalls: this page only, or up to three levels. The rule editor shows the broadest path a rule recalls for a test address.

Two rules ship by default. “Single-page apps” is on and ignores the URL hash. “GitHub Pull Request” is off. On pull request and issue pages it recalls notes about the same repository, not only the page itself. A rule you edited keeps your edits. Add, edit and test rules under Recall Rules in the extension options. Rules apply to the notes lookup for the current page, to the results next to your search engine, and to the count on the toolbar badge. When several rules match the same page, they are combined.

Page scopes compare exact page names, ignoring case and surrounding spaces, so excluding “Work” does not hide “Homework”. If a result’s page name cannot be determined while a scope is active, the result is dropped instead of shown.

Privacy

The extension draws some UI inside the pages you visit: search results next to your search engine, the clip button and the highlight comment popup. That UI lives in shadow roots. In packaged builds the roots are now closed, so a script on the page cannot reach into them through element.shadowRoot. Development and test builds keep them open, and a test checks that the packaged build exposes shadowRoot === null.

Related changes: the content script no longer trusts DOM events that a page script could dispatch, and uses an in-memory channel instead. Closed roots do not change what the extension can access. It still has host access to all sites, as in 1.x, and sends data only to the Logseq API server you configure.

The extension’s styles no longer leak into the pages you visit either. Before, a page that used Tailwind could lose some of its own styles to the extension (#79).

New UI

The orange theme is replaced by Logseq teal, about #206f78 in light mode and #85c8c8 in dark mode. The browser sidebar and the options pages follow your system’s dark mode, and highlights on the page use the teal on both light and dark pages. The options pages are flat, with plain lists instead of nested cards, and are capped at a centered 768 px width. The built-in recall rules now have English names and descriptions.

Smaller changes

Block text on the card and in the sidebar keeps its line breaks, and DB graph tags and page references show their names.
The options page checks the connection as you type, and shows the extension version in its sidebar.

Get it

Install from the store for your browser on the Installation page, then follow the Setup guide if this is a fresh install. The code, release notes and issue tracker are on GitHub. Questions and bug reports are welcome in Discussions.

Highlights in the browser sidebar

Fri, 23 Oct 2026 00:00:00 GMT

Logseq Copilot 2.0 keeps the highlights of the page you are reading in your browser’s own sidebar. In Chrome and Edge that is the side panel (the extension uses the sidePanel API). In Firefox it is the sidebar (sidebar_action). Browsers without a sidebar of their own, and Arc, get the same sidebar drawn on the page instead. This post follows a highlight from creation to deletion. The reference version is on the Sidebar page.

Create a highlight

A highlight is created when you clip a text selection.

Select text on a web page.
Clip it in one of three ways:
- Right-click the selection and choose Clip “…”.
- Press the clip shortcut. The default is Ctrl+Shift+U, and you can change it in your browser’s shortcut settings.
- Click the floating clip button that appears next to the selection. It is off by default. Turn on Floating Button under Clip Note in the extension’s Settings.
The text is marked on the page. Reload the page later and the saved highlights are marked again. Click a highlight on the page to open a small comment popup.

A clip with a selection does two separate things. The selected text is converted to Markdown and written to Logseq with your default template. And a highlight, with its position on the page, is saved in your browser.

There are three entry points.

Click the toolbar icon. In Firefox, click it again to close the sidebar.
Right-click the page or a selection and choose Open sidebar.
Use the Open sidebar command. It has no default key, so you bind your own.

To bind the command:

Open the shortcut settings. In Chrome that is chrome://extensions/shortcuts. In Edge it is edge://extensions/shortcuts. In Firefox, open about:addons, click the gear icon and choose Manage Extension Shortcuts.
Find Logseq Copilot and set a key for Open sidebar.

The sidebar is tied to the browser window and shows the highlights of that window’s active tab. Switch tabs, or navigate to another page, and the list updates. The sidebar stays open. In Edge the browser reloads the side panel on every tab switch, so the extension rebuilds the list from the active tab and from storage.

The header shows the name of your graph, a search box and the Clip page and Clip selection buttons. The list is newest first. Each entry shows the highlighted text (shortened to 120 characters), the note (shortened to 80), when you made it, and up to three tags.

Highlights belong to an exact URL. https://example.com/post, https://example.com/post?ref=feed and https://example.com/post#intro each have their own list.

Jump, edit, delete

Jump to it. Click an entry and the page scrolls to the highlight.
Edit the note. Hover over an entry, or tab to it, and click the pencil. Save with the button or Ctrl+Enter (Cmd+Enter on macOS). Escape drops your changes. If the comment popup for that highlight is open on the page, it shows the new note.
Delete it. Click the trash button. The highlight disappears from the list and the page. There is no confirmation and no undo.

Two notices can appear when you click an entry. “Couldn’t find this highlight on the page” means the text is no longer there, usually because the page changed. The entry stays in the list. “Reload the page to jump to highlights” means the tab has no content script, typically because it was already open when you installed or updated the extension. Reload the tab and click again.

Pages that do not have highlights

Only http and https pages can have highlights. On the new tab page, on browser pages such as chrome://extensions or about:addons, on local files and on other extensions’ pages, the sidebar says “Not available on this page”. Open a web page and the list appears.

Where the data is stored

The clipped text becomes a block in Logseq, but a note you add to a highlight stays in the browser. Uninstalling the extension deletes the stored highlights.

To see everything in one place, open the extension options and go to Highlights. That page lists the highlights from all sites, can export them as a JSON file with Export All, and can remove them all with Clear All. Export before you uninstall if you want to keep them.

Upgrading to 2.0

Fri, 23 Oct 2026 00:00:00 GMT

The update from 1.x to 2.0 installs like any other. Your settings are migrated automatically, so you do not need to export or re-enter anything. This guide lists what is migrated, what to check afterwards, and what is different.

What is migrated

The migrations run in the extension’s background script when the browser installs or updates the extension. Each one only acts when there is something to migrate, so running it again changes nothing.

Connection (host, port, token). 2.0 reads the same storage keys as 1.15.2, so these stay as they are. Very old installs may still hold a single logseqHost URL. If so, 2.0 splits it into host and port, then deletes the old key. It never overwrites a host or port you have already saved. A URL without a port gets the default port of its scheme (80 for http, 443 for https).
Clip settings. 1.x had one clip template, one location and one custom page. 2.0 has a list of templates, and the clip shortcut and the context menu use the first one. On update, your template, location and custom page are copied into the first template. This only happens if you have not edited the templates yet, meaning they are unset or still the single built-in default. The old keys stay in storage, but clipping no longer reads them. The copy runs once.
Floating clip button. The setting uses the same key as in 1.x and keeps its value.

What to check afterwards

Open the extension options and go to Settings. The connection is checked as soon as the page loads. You should see “Connected to Logseq v…”. The extension builds the API address as http://<host>:<port>, so the scheme of an old https:// URL is not kept.
Reload tabs that were already open during the update. The extension only attaches to a page when it loads, so an old tab does not run the new content script. If you click a highlight in the sidebar on such a tab, it shows “Reload the page to jump to highlights”.
Open Templates and look at the first template. It should contain your old clip template.
If you want a key for the sidebar, bind one. The Open sidebar command has no default shortcut. The clip shortcut keeps its default, Ctrl+Shift+U.

File graphs and DB graphs

There is no setting for the graph type. On each request the extension asks Logseq whether the current graph is a DB graph, and uses the matching code. The connection fields are the same for both: Host, Port and Authorization Token. File graphs are Logseq 0.10.x. DB graphs are Logseq 2.x.

The differences you can notice:

Tasks. On a file graph, toggling a task rewrites the marker in the block text, and blocks with a SCHEDULED: line are refused. On a DB graph, the task state is Logseq’s status property. TODO, DOING, DONE and CANCELED can be toggled, and other markers are refused.
URL lookup. On a file graph the lookup also tries the URL with its query string and hash. On a DB graph it searches by host and path.

Highlights are new

1.x marked the text you clipped, but only until you reloaded the page. It did not save highlights, so there is nothing to migrate. In 2.0 a highlight is saved when you clip a selection, and the list opens in the browser’s own sidebar. See Highlights in the browser sidebar.

If you tried a development build, you may remember a sidebar drawn over the page, with a floating toggle and a Ctrl/Cmd+Shift+H shortcut. They are removed. The sidebar is the browser’s own now, and the toolbar icon opens it in place of the 1.x popup. Only browsers that do not show a sidebar of their own get a sidebar drawn on the page, and it opens from the toolbar icon too. Arc has a side panel but does not show it, so the extension uses the one on the page there until you choose in Settings, Sidebar, In-page sidebar.

Permissions

The permission list is the same as in 1.15.2: storage, activeTab, contextMenus and access to all sites. 2.0 adds sidePanel on Chrome and Edge, which is what lets the side panel open. It does not trigger an install warning, so the update should not ask you to approve anything. The Firefox build declares that it collects no data.

Known limits

Safari is not supported. See Installation.
Firefox 127 or later is required. Older Firefox versions cannot install 2.0.
Highlights only work on http and https pages, and only match the exact URL they were saved on.
Highlights are stored in the browser only. They are not written to Logseq.

If something does not migrate the way this page says, open an issue on GitHub or ask in Discussions. The 2.0 announcement has the full list of changes.

Logseq Copilot | Blog

Logseq Copilot 2.0

File graphs and DB graphs

Firefox

Highlights in the browser sidebar

Search result pages

Clipping

Recall rules

Privacy

New UI

Smaller changes

Get it

Highlights in the browser sidebar

Create a highlight

Open the sidebar

The sidebar follows your tab

Jump, edit, delete

Pages that do not have highlights

Where the data is stored

Upgrading to 2.0

What is migrated

What to check afterwards

File graphs and DB graphs

Highlights are new

Permissions

Known limits