Advanced Browser - mod kaiu 2026

I'm not the original add-on's creator!

Advanced Browser, link to add-on on AnkiWeb.

I'm just tired of waiting for the add-on's author to respond to a good suggestion to expand the functionality of the "persitent menu for multi-selection & add fields reset function" https://github.com/AnKing-VIP/advanced-browser/pull/187 I saw a lot of issues with the map overview, and since I like to highlight certain maps in color, I couldn't do it comfortably with the standard overview.

It is recommended to use this addon with: Preview Slideshow (Shigeyuki) - mod kaiu 2026

Installation

• Disable the old add-on for now (Advanced Browser)
• Download this add-on and reboot your Anki.

The addon was tested under Qt6 on a new version of Anki, meaning it's designed for 2026, and I think it'll last at least a year until the original addon's author makes changes to reflect these ideas, or Anki is redesigned to such an extent that the addon becomes unnecessary...or stops working due to significant changes. So, don't hesitate to use it while it's still around.

What has changed in "advanced-browser-mod-kaiu-2026"

• Fixed a bug where the menu wouldn't fit many items (there were too many fields and they couldn't be accessed).

• The menu now always has three selection methods (excluding the "Use a single list for fields" setting): "- Current note fields -", ​​"- Fields (all) -", "- Fields (in models) -" — this is more convenient when there are a lot of fields and note types.

• The menu is now much more convenient, as you can select multiple items at once (author: "denny0810", still unfulfilled request "persitent menu for multi-selection & add fields reset function #187"). Select as usual with the left mouse button and complete the selection with the right mouse button. There's also an option to select the "- Fields Reset -" menu item, which will remove the main fields (not extended or system fields). This allows you to quickly reconfigure the display of the required columns.

• Added the option to display the "Tags (L1)...(L5)" columns. Tags in Anki aren't perfect, and it's unclear when they'll implement them and put them in a separate table. So the AI ​​kept insisting that this wasn't possible, but everything seems to be working fine and isn't lagging (Anki itself is lagging. Even setting "marked" takes 5-10 minutes on 150,000 notes, but a simple computer like this is ideal for testing, so you definitely won't have any issues). L1 is the level of a regular tag, without the "::" (usually a space). But sometimes you only need to see a specific tag nesting level, and Anki sorts all tags alphabetically, and this often gets in the way.

• Added the ability to display the "nid" and "cid" columns, as this is mentioned in the help file and is useful for more than just developers.

• Added the ability to display the "Card State" column. They seem to say that there is a "Card Type", but it would be good for users to see the same behavior as when choosing in the "Sidebar", and there it is not unambiguously from one, and sometimes an entry immediately refers to several "Card States".

• The "Overdue interval" and "Previous interval" columns for periods from 31 to 90 days will no longer display as months, but only as days. I think it's better to see 32 days than 1.1 months (I've seen a similar request from a user since 2020).

• The flag column will now also display the number "1 - Red" (for red), as the completion status of certain study stages was often color-coded, and sorting there was never done by color.

• Column names are now left-aligned, as is done elsewhere in other systems, since long names make it difficult to see the middle, and wide columns shift the name to the center, so you see the data but don't yet see the column name.

• The most convenient feature that was sorely missing is that the column you're in is remembered, rather than having every sorting change reset you to the beginning. It's remembered even when switching between a card and a note.

• The current row is now highlighted with frames, and the current cell with a bold frame. This is done so that you can see the row color, and the ability to display multiple colors in a single cell has been added, as this was also missing, and it's important for signaling different statuses.

• If it's the current deck, the search bar was previously blank, and you might think it was 'deck:*'. So now I type it there immediately, and even if it's deleted, the query string used to obtain the data in the table is always displayed above the table, which is very convenient.

• For the sidebar, you can now change the search bar by clicking on an item while holding Ctrl (OR operator) or Shift (AND operator). Some changes have been made to the algorithms there as well: if you accidentally added something with Shift, you can press Ctrl, and it will replace what you typed instead of adding it; But you can also delete the last item entered by pressing Ctrl+Win or Shift+Win; previously, Ctrl+Shift+Alt didn't affect negation, but now it will, since logically, it should be possible to change it.

• If you've added columns with note fields, and there can be dozens of such fields in complex decks, it's difficult to immediately find the edit field. So, to simplify focusing, you can click on such a cell in the table, and the focus will move to the edit field (you can press F2).

• The sidebar can now be hidden using the button on the quick launch toolbar or by pressing Ctrl+Alt+R (and the T next to it, pressing Ctrl+Alt+T, switches the view from the map to the note).

• By pressing F10 (or the button on the toolbar), you can open a window in which you can change the order of columns, as moving them around was terribly inconvenient with a large number of them. You can also delete some columns, re-sort, save or load the column order from a file.

• When you clicked on the sidebar and changed your query in the search bar, it wasn't saved until you pressed "Enter." This remains the case, so the drop-down list will store exactly what you want. But query changes needed to be remembered somewhere, so we introduced the change history (arrows). The history remembers the query and the current card, but the active column, sorting, and column set remain the same so you can analyze them (view with the same sorting and column set). Saving to history happens automatically if you clicked on the sidebar and if you press F9 (there you can save the positions of different cards in a single table). However, sometimes you need to go back in history, see what card was there, study it, and then move to a new card in the same table (perhaps it's the same deck) and remember this position so you can return to it later. To do this, press F5 (refresh) — this will overwrite the active card's history. Of course, you can press F9 and save a new history, but sometimes it's easier to work with three histories with different decks and change their active card rather than create new histories. When you close the ankhs and then open them another time, you'll immediately be presented with the current deck view, but you can return to the previous history and retrieve all your decks you're working with, and the current entry's position will be the one you updated by pressing F5. This is more convenient than simply saving a search query, which is currently available in the sidebar.

• Added the ability to translate the add-on into a language other than English. This time, I decided not to implement translation in the "config.json" settings file itself; I was simply tired of Google messing up the formatting for translation, and other AIs aren't perfect. I also didn't implement a complex Fluent-like translation system like Anki, since I needed a file that users could upload to Google and still have something survive. :) And the flt file itself isn't easy to read when a line like card-templates-enter-new-card-position-1 = Enter new card position (1...{ $val }): is incomplete. So I came up with my own solution (a bicycle), which is flexible and separates the variable (block) name from the text itself. This means the translator focuses only on its own lines, which never begin with === or !!! It looks like a regular text file with line translations, easy to understand for any human, much less an AI. Example:

` !!! === $ $ ; setting, block separator, variable start and end, comment start marker

=== q_Card_State

Card State

=== q_nid

nid (Note ID)

=== q_The_field_not_belong_note_type ; in the translation, be sure to check for the presence of two parameters: %s

The field '%s' does not belong to the note type '%s'. `

In the add-on settings, find the description of how to find the "en.lng" file. Create a copy of this file for your language in the same directory and translate this file into your language. (You can send me this file, and I'll add it and update the addon within a week.) You can see the source code here: https://github.com/AndreyKaiu/anki_addon_localization

Added since version 3.9.2b, date: 2026-01-25

The "$:text" search type is now supported. This will find all words, even if each character is followed by an diacritic (a mark that changes the sound) or if there are tags between letters (bold, etc.) – it will find everything.

The search is not case-sensitive.

To perform this search within a regular expression ("re:"), you must write it as a call to the $(text) function.

How it works: instead of $:abc, the search will be "re:a[\u0300-\u036F]*(<[^>]*>)*"b[\u0300-\u036F]*(<[^>]*>)*c"

Added since version 3.9.5b, date: 2026-02-27

Fixed font display in the column list window in dark mode.

A button for displaying card information, a dedicated hotkey (Shift+F1), and an option to always display the window on top of its original window have been added. The add-on settings now include the "Card Info Dialog Always On Top" setting, which is set to "true" by default. You can set it to "false" if significant errors are detected in your program. For now, I find it much more convenient. The card information window doesn't disappear when I switch between modes, and it can now be reduced to 100 pixels (reduce the font size as usual: hold down the "Ctrl" key and scroll the mouse wheel). However, if you don't like viewing card information in a separate window, you might want to try the "Browser Card Info Bar" add-on.

Added since version 3.9.6b, date: 2026-03-05

The "Previous Duration" field has been corrected. Since there were "Previous Duration" and "Previous Interval" fields, I've added "Last Duration" and "Last Interval" fields. The "Last Interval" field is not exactly the same as the "Interval" field and will show a more accurate value for "Learn," which is stored in the card statistics.

The "Step" field has been added. This field shows how many successful learning steps you've completed. If you can view "Reviews" from the card statistics, it will only be equal to the "Step" field if you've never clicked "Again." A "Step" of 7 typically indicates strong memorization, especially if the last interval was more than 14 days apart.

Added since version 3.9.8b, date: 2026-06-07

A bug that caused a long time to select more than 20 records has been fixed. It was accidentally left behind in version 3.9.5b during testing. Now, selecting 1,000 cards doesn't take as long, about a couple of seconds, but selecting 16,000 cards takes a long time, requiring about 10 seconds. If possible, avoid selecting such a large number of cards; instead, limit your search to a single deck or a query that reduces the number of cards to 1,000.

A button has been added for selecting and then viewing selected cards (notes). After selecting, you can go back and forth through the history. If only one note is selected, the button will function as a regular view button (the one activated by Ctrl+Shift+P, while this one will be activated by Shift+F2). This button is used for convenience when using the small-group memory method: selecting 3, 5, 7 (the optimal number—I recommend it), 10, 15, or 20 cards and viewing them 2-3 times in order as is, and then recalling them 2-3 more times with random card selection enabled (using the "Preview Slideshow" add-on ). If you want to be sure to view all cards, close the viewing window and reopen it. Then, the first time, it selects exactly all N cards in N selections. Once you're confident you've memorized these 7-10 words, move on to other words (word group 2). If a word feels particularly difficult, you can mark it with a red flag for later, separately. Once you've reviewed 5 groups of 7-10 words in this manner, quickly review all the cards again, starting with group 1. This way, you'll complete one review, then another review before bed, then the next morning. It's quite possible to learn 35-50 cards in a day. But not every day! One day for new words, another for reviewing the previous day's new words, and then review all the other cards. In a month, it's possible to learn 525-750 sentences (new words within sentences) using your own card sorting system or your own specific order of studying the cards. But in this case, you alone will be responsible for monitoring the intervals of studying the cards and assessing their difficulty (for example, using three different colored flags).

Added since version 4.0.0b, date: 2026-06-23

The current row number in the table (and percentage of the total) will now be shown in the window title.

The switcher between cards and notes has been returned to its original state to fit all the buttons into a compact view (users sometimes need a very compact view)

Added since version 4.0.2b, date: 2026-10-29

Originally, this add-on used the labels "Card" instead of "Card Type" and "Note" instead of "Note Type." I have restored the full names so that they match the column headers used in Anki by default. In the card info properties, the label will now appear as "Card State." I also fixed a bug present in the original version of the add-on: sorting by the "Card Type" column did not work correctly when the note type was "Cloze."

HELP AND SUPPORT

Please do not use reviews for bug reports or support requests.
And be sure to like, as your support is always needed. Thank you. I don't get notified of your reviews, and properly troubleshooting an issue through them is nearly impossible. Instead, please either use the issue tracker (preferred), add-on support forums, or just message me at andreykaiu@gmail.com. Constructive feedback and suggestions are always welcome!

VERSIONS

• 4.0.2b, date: 2026-10-29. "Card" => "Card Type"; "Note" => "Note Type". Fixed an issue with the "Card Type" field when using a "Cloze" note type.

• 4.0.1b, date: 2026-06-26. The button to view selected cards will now select cards or notes, depending on what view you currently have in your table.

• 4.0.0b, date: 2026-06-23. The current row number in the table (and percentage of the total) will now be shown in the window title.

• 3.9.9b, date: 2026-06-09. Added "Show note counts" option. Show the number of notes (cards and any elements) in the left sidebar.

• 3.9.8b, date: 2026-06-07. Fixed a slow card selection issue. Added a button to view selected cards.

• 3.9.7b, date: 2026-05-13. Fixed a bug in displaying button names in newer versions of QT.

• 3.9.7b, date: 2026-03-12. Fixed an error in the position of columns that occurred when the user manually changed their position.

• 3.9.6b, date: 2026-03-05. The "Previous Duration" field has been corrected. Added fields: "Last Duration", "Last Interval", "Step".

• 3.9.5b, date: 2026-02-27. Fixed font display in the column list window in dark mode. Added a button to display card information, a dedicated hotkey, and an option to always show the window on top.

• 3.9.4b, date: 2026-02-16. Added the ability to create a deck from the context menu of the deck item

• 3.9.3b, date: 2026-02-04. Since the "F5" hotkey was used to record audio, and the "F8" hotkey was used to select text color, the hotkeys have changed in this version: F5 ⭢ Shift+F9; F8 ⭢ F10

• 3.9.2b, date: 2026-01-25. The "$:text" search type is now supported. This will find all words, even if each character is followed by a diacritical mark (a sign that changes the sound) or if there are tags (bold, etc.) between the letters—it will find everything. The search is not case-sensitive. To perform this search within a regular expression ("re:"), you must write it as a call to the $(text) function.

• 3.9.1b, date: 2026-01-21.

SPECIAL THANKS

• Thanks for the development help: chatgpt, deepseek, GitHub.copilot - they help a lot (and sometimes they make mistakes), and without them I definitely couldn't have done it, since I don't program in Python and I'm certainly not an Anki developer.

=========================

See my other addons and decks here: https://ankiweb.net/shared/by-author/1188253433

=========================